Odoo settings
Odoo is managed in two places in Settings. The connection itself, meaning how STYD reaches Odoo, its sync status and its AI Guide, lives under Settings → Connections. Who gets which Odoo access lives under Settings → Members → Odoo access. There is no separate Odoo tab.
Settings → Connections: the Odoo connection
Owners and admins add an Odoo connection with Add Odoo connection and choose how STYD connects:
Paste an API key of one Odoo user, works with Odoo 15 to 20 (STYD detects the version; Odoo 15 to 18 also need the Odoo login and the database name). Everyone in the workspace sees what that one Odoo user sees. No member mapping.
Install the module from Odoo Apps (Odoo 15, 16, 17, 18 or 19). Each member is mapped to their own Odoo user, and STYD applies that user's areas (Accounting, Sales, Purchase, Inventory) and companies.
Each Odoo connection has a card that shows:
Whether Odoo access is synced, when it was last synced, and why the last sync failed if it did. Re-sync fetches the latest Odoo users, companies and rights. It never asks for the key or token again: it reuses the one stored with the connection.
For an API key connection: the Odoo rights and companies of that one Odoo user, which everyone in the workspace shares.
The stored description of your Odoo data that STYD uses to answer. It is rebuilt when you press Re-sync, which owners and admins can do at any time.
How many members are mapped, and a Map members button that opens Settings → Members → Odoo access for this connection.
Members who are not owners or admins see the card read-only, with a short summary of their own access.
Settings → Members → Odoo access: member mapping
On a Bridge connection, each workspace member needs their own Odoo user. Owners and admins pick the Bridge connection, then choose the matching Odoo user for each member. Answers then use that person’s Odoo areas and companies.
The Odoo users to choose from come from the last sync of the connection.
Choose the Odoo account that represents this person in Odoo.
A mapping is flagged when its Odoo user is no longer in Odoo, is inactive, or lost companies. Choose another Odoo user for that member.
Why mapping matters
In Odoo, two users may see different companies, records, or business objects. Mapping keeps STYD from treating all workspace users as if they had the same Odoo access.
Odoo security model
For Odoo workspaces, STYD relies on Odoo's users and companies: the API key's Odoo user, or each member's mapped Odoo user on the Bridge. Table hiding does not apply to these connections, because they read Odoo models, not tables.
When to re-sync
Best practices
For an API key, create the key on a dedicated Odoo user with only the rights you want to share.
On the Bridge, make sure each STYD member is mapped to the correct Odoo user.
Keep STYD aligned with Odoo permissions and company access.