Company access

In multi-company Odoo setups, the company shapes the answer. STYD limits Odoo answers to the companies of an Odoo user, which matters for getting the right numbers.

How company scope is applied

Odoo users have a set of allowed companies. How STYD picks the set depends on the connection:

Bridge: each workspace member is mapped to an Odoo user, and answers use that user's companies. A member who is not mapped (or whose Odoo user was removed or deactivated) gets no Odoo data until an owner or admin maps them. STYD never falls back to another person's companies.
API key: there is one shared identity. Everyone sees the companies of the key's Odoo user, and that user needs at least one company.

STYD adds the company filter to every read of an Odoo model that has a company, instead of running a blind query across all companies. If a mapped Odoo user has no company, STYD refuses the question rather than answering across all companies.

What you see when it is refused

A member who is not linked to an Odoo user is told that their account is not linked yet and to ask a workspace admin to link it. That reply is free. A mapped member whose Odoo user has no company gets a general message that they have no access to this Odoo data with their current Odoo permissions, and that reply counts as an answered question.

Why company context matters

The same question (revenue, invoices, stock) can give different numbers for each company. For a figure that matters, say which company you mean in the question.

Check important figures

The company filter applies to the models that carry a company. It is not the whole of Odoo's access control: record rules are not reproduced on a Bridge connection. For important multi-company figures, check the result before acting.