The Odoo Agent works as the employee who asked

The Odoo Agent is the staff product, and it is in beta. It is the answer to a different question from the eCommerce Agent. Shoppers get a sales flow. Employees get an assistant that behaves as them.

The Odoo AI agent guide covers setup, MCP, and the price. For the shopper side, see the AI chatbot for Odoo guide.

Their Odoo rights are the ceiling

The agent acts as the signed-in employee. Access rights and record rules in Odoo still decide what can be opened. If that person cannot see a sales order, the agent cannot see it either. If they can confirm an order or post an invoice, the agent can run that same action.

Some models are refused before the request is sent, even when the user could open the form by hand. Those are passwords, API keys, mail servers, access rules, and security groups. The refusal is the platform’s, not a prompt asking the model to be careful.

What a person can ask it to do

They can search records, create and update them, run actions, and generate a PDF report or a quick export such as unpaid invoices. They can read and add log notes and schedule activities. The dashboard chat is one place to ask. Cursor and Claude are another, using the MCP key together with that employee’s Odoo login. The same tools are on the REST API.

Every action is logged with the person, the tool, and the record. That log is how a team reviews what the assistant changed.

How this sits next to the store agent

The eCommerce Agent uses the store connection you configured, and its public tools are the sales flow: search, cart, checkout, and, on paid plans, order status. It is the wrong tool for an employee who needs to post an invoice.

The Odoo Agent is the wrong tool to embed on a product page. It has no free plan. Starter is $49 a month for 25,000 AI responses, and the allowance rises on the higher plans. During beta you should expect the surface to keep moving, which is why the agent page marks it beta rather than live.