What each member can see in Odoo

On a connection made with an Odoo API key, each member of your workspace can be linked to their own Odoo user and get answers within their own Odoo rights, never beyond what the connection's key can read. The owner and admins set this up for each person, in one place: Settings → Members.

The rule: the lower of two rights

A linked member's answers follow the lower of two things: their own rights in Odoo, and what the connection's key can read. Their own rights apply with a key from an Odoo administrator (see below).

  • The key is the ceiling. A member never sees more than the key can read, whatever their rights in Odoo. Linking someone never widens what the key reaches.
  • Their own rights narrow it. Within what the key can read, a linked member sees what Odoo shows their own user: their areas, their companies, and rules such as a salesperson who sees only their own orders.
  • Never more than Odoo. When an Odoo rule limits a member in a way we cannot apply exactly, we close that area for them instead of showing too much, and their answer says so. The owner finds these rules in Settings → Members. An answer can show less than Odoo would show that person, never more.
  • Costs stay with the owner. Costs, margins and purchase prices are shown to the workspace owner only, whatever a member's Odoo rights.

Which key to use

Own rights for each member need a key from an Odoo administrator: an Odoo user with Access Rights, who also holds the business rights you want your members to be able to use. With that key, each linked member gets their own Odoo rights.

A narrower key gives everyone less. Say you invite your accountant, who has full Accounting rights in Odoo, but the connection's key comes from a user with no access to Accounting: your accountant gets no accounting answers. When you invite someone whose rights the key does not cover, we tell you which areas are missing, and the invitation still goes out. The fix is a key from a user who holds those rights.

Any key still works. With a key that does not come from an Odoo administrator, linked members see what the key shows, within their areas, and their own Odoo rights start once you connect a key from an Odoo administrator.

An Odoo API key can also write in Odoo, but we only read. The owner can change the key at any time in Settings → Connections.

Linking each member to their Odoo user

The owner and admins link members when they invite them. In the invitation, search for the person's Odoo user by name, email or login, and pick it. The invitation goes out once you have made a choice.

Can't find this person? There are three ways forward:

  • If the key cannot list Odoo users, we say so and explain how a key from an Odoo administrator fixes it.
  • If the person has no active Odoo user, create one in Odoo, then refresh the list and pick it.
  • Same access as you: the person sees what the connection's key sees, with no Odoo user of their own, for example an outside consultant. Costs, margins and purchase prices stay yours, and you can narrow their areas later. When an admin invites, this choice reads “The connection's full access”.

When a member's email matches one active Odoo user, we link them to it on our own, for example once you have created their user in Odoo. We never do this for a member you unlinked or gave the same access as you. Members who were in the workspace before linking was available show their match on their row, and one button, Link all matches, links them.

Until a member is linked, they see what the connection's key shows, narrowed by the areas they are allowed. They never get an empty answer because of it. The owner sees what the key shows.

A member who asks from Claude or ChatGPT gets the same answers as in the web app. If they ask about their own work (my sales, my orders) before they are linked, the answer says so in one line and points to Settings → Members.

When something changes in Odoo

  • A member's rights change in Odoo. The new rights apply within a day, or right away when an owner or admin presses Refresh from Odoo on the connection's card.
  • Their Odoo user is archived or deleted. The member is paused: they get no Odoo data from the connection, and their answer says why. That answer is free. The owner gets an email the same day and chooses on the member's row in Settings → Members: Remove from workspace, or Keep with area access (they then see what the key shows, within their areas).
  • The connection moves to another Odoo database. Links to the old database end, and members are linked again by email to the users of the new one. Anyone left without a match sees what the key shows, within their areas, until you link them. The owner and admins are told.

Limit a member to chosen areas

Owners and admins can also limit a member to chosen Odoo areas on a connection: Sales, CRM, Accounting, Purchase, Inventory, HR, Point of Sale and Manufacturing. Areas only narrow what the rule above allows; they never add to it. A member with no limit has all areas.

Where it is managed

Everything about members is in one place: Settings → Members. The invite bar is at the top, with one list of people and invitations below it. Each row shows the person's Odoo link (Linked, Not linked or Paused) and their access (Own Odoo rights, Same as you, Areas or All areas). Edit opens the row in place, to change the role, the Odoo user, the access or the areas. A line above the list repeats the rule: the key is the ceiling.

  • The owner and admins invite, link members and set areas. Only the owner changes roles, and only the owner decides for a paused member.
  • A member sees their own Odoo access there, read only.
  • Odoo Bridge connections are in the same list. On the Bridge, each member is linked to their Odoo user, and answers follow that user's areas and companies. See User mapping.
  • Your workspace's API keys, for Make or n8n, follow the same rules as a member who is not linked, unless you link them. We never link an API key on our own.

Français

Need help? Contact support