Skip to Content

Odoo 20: keep the AI for a few users and protect your credits

November 18, 2026 by
Odoo 20: keep the AI for a few users and protect your credits

You move to Odoo 20 and, the next day, everybody clicks the little “AI” logo: to rephrase an email, summarise a PDF, generate a product image. Each click spends Odoo AI credits, and the question comes quickly: “how do I keep the AI for a few people?”. I looked for the answer in the Odoo 20 code. There is none. Here is what the standard does, what it does not do, and the free module I wrote to fill the gap.

1. In Odoo 20, AI is everywhere and it is paid in credits

Odoo 20 removed the OpenAI key you could enter in Odoo 19: all the built-in AI now goes through the Odoo AI service, billed in IAP credits. And it is installed by default on an Enterprise database as soon as the server allows it (module ai_auto_install).

I listed the entry points of the ai module alone, the one everybody has: the Ask AI button of the top bar (which opens the AI on the current record), the AI tab of the messaging menu and its “Chat” button, the AI button of the editor toolbar and the /AI and /Voice Transcript commands, the Ask AI button of the full email composer and of the file viewer, image generation in the media dialog, the Ask AI entry of the command palette (Ctrl+K), and meeting transcription. Nine doors, not counting those added by Documents, Knowledge, Social Marketing or the website builder.

💡 Key takeaway

In Odoo 20, the built-in AI no longer has a “my own key” mode: every use is paid in Odoo AI credits.

2. What the standard allows (and does not)

The ai module declares no group. Its access rights give every internal user read access to the AI agents, and its routes (/ai/get_direct_response, /ai/transcription, sending a message to the AI…) require one thing only: being logged in. The only server-side limit is… running out of credits.

The top bar button is hidden only for a “light” user, the new role of Odoo 20. Making someone a light user to take the AI away from them takes away much more, and does not even close the other doors. And hiding a button is not enough: a direct call to the route, from the browser console, still gets an answer.

💡 Key takeaway

The standard has no “who may use the AI” setting. A serious control must hide the buttons and refuse the calls on the server.

3. The solution: an “AI User” group

The free module AI Access Group adds a Productivity › AI right on each user form. For those who do not have it:

  • the nine entry points of the ai module disappear from the interface;
  • the server refuses the AI routes, the opening of an AI chat and meeting transcription, before any credit is spent;
  • the buttons added by the other AI apps hit the same refusal, since they open their chat through the same server method.

Nobody loses the AI at installation: every existing internal user is put in the group. You then remove the people you choose. Administrators always keep it, and new users are not in it, unless you add it to the default access rights.

What the module does not block, on purpose: automations set up by an administrator (AI fields filled by the scheduled action, AI server actions, email templates with an AI prompt), the AI agents of your live chat for website visitors, and MCP, which puts your own AI (Claude, ChatGPT) to work without any Odoo credit.

💡 Key takeaway

The module decides who uses the AI, not how much: there is no per-person credit cap (yet).

4. How I checked it

The tests call the routes directly, as someone bypassing the interface would: a user outside the group gets an access error on the direct answer, the transcription, sending a message to the AI and opening a chat; a user in the group gets their answer. The AI service is simulated: no credit was spent for the tests. I then deliberately broke the check in several places to make sure the tests notice: every time, they fail.

On performance, the cost is zero for the interface (one flag sent with the session, no extra request) and one cached group check on the server, that is zero SQL queries per call once the cache is warm.

💡 Key takeaway

A limit that is only checked on screen is not a limit: the test that matters is the refused direct call.

⚔️ The Match: standard Odoo 20 vs AI Access Group

Criterion Standard Odoo 20 AI Access Group
Keep the AI for some people No (only through the “light” role) Yes, with a right on the user form
AI buttons hidden Top bar only, for light users The 9 entry points of the ai module
Direct call refused by the server No Yes, before any spending
Automations and website chat Work Work (not restricted)
Per-person credit cap No No

Checked in the Odoo 20 Enterprise source code (ai module) and verified on a test instance, November 2026.

The Verdict: Odoo 20 AI deserves an access right, just like accounting

Odoo 20 AI is useful, but it is paid per use and the standard gives it to everybody. A group, hidden buttons and a server-side refusal: that is what AI Access Group does, for free.

Preparing your move to Odoo 20 and want to know where the AI will save you time, and who should have access to it? Let us start with an audit of your Odoo.

Request a Free Audit
Odoo make to order: why the promised date ignores your vendor lead time