Members who are not linked to Odoo
On an Odoo Bridge connection, STYD never guesses whose Odoo access to use. When the connection is not synced yet, or a member is not linked to an Odoo user, that member gets no Odoo data from the connection. The answer says why and who can fix it.
What it is
On the Bridge, STYD limits each member to the areas and companies of their own Odoo user. Until STYD knows that user (the connection is synced and the member is mapped), it has no safe limit to apply, so it reads no Odoo data for that member. There is no reduced “fallback” answer and no use of another person's access.
When it applies
Odoo access has never been synced for the connection, or the last sync failed. Nobody gets Odoo data from it until a sync succeeds.
The member is not linked to an Odoo user on this connection. They get no Odoo data from it until an owner or admin maps them.
The mapped Odoo user was removed or deactivated in Odoo. The member is treated as not mapped until they are mapped to another Odoo user.
The mapped Odoo user has no company. STYD refuses the question instead of answering across all companies.
What you see
In chat, an Odoo question gets a short answer instead of data. A member who is not linked reads that their account isn't linked to an Odoo user yet and to ask a workspace admin. A member whose Odoo user is no longer valid reads that and is asked to have the account linked again. If the connection is not ready, the answer says so. An owner or admin gets a link to the place that fixes it.
The answer for a member who is not linked is free. The other refusals on this page count as an answered question and use a prompt.
In Settings, the connection's card in Settings → Connections shows the sync status, and Settings → Members → Odoo access shows which members are not mapped.
A directly connected Odoo database
A member can also ask about an Odoo database that is connected directly, as a PostgreSQL connection. That path has no Odoo user for each member and no company filter. STYD reads with the database user's permissions and applies the tables hidden for that member. Prefer an API key or the Bridge when you need limits for each member.