Odoo rights vs STYD table hiding
Odoo access rights and STYD table hiding solve different problems. Table hiding belongs to SQL connections. For Odoo, the controls are Odoo's rights and the limits STYD applies to each member.
Two different controls
Odoo access rights & record rules
Decide what Odoo users may access inside Odoo. With an API key, Odoo applies them to every read STYD makes. The Bridge module does not apply them; STYD applies the four areas (Accounting, Sales, Purchase, Inventory) and the companies of the mapped Odoo user instead.
Decide what Odoo users may access inside Odoo. With an API key, Odoo applies them to every read STYD makes. The Bridge module does not apply them; STYD applies the four areas (Accounting, Sales, Purchase, Inventory) and the companies of the mapped Odoo user instead.
STYD table visibility
Lets an owner or admin hide tables of a SQL connection from a member. STYD then refuses any query that touches them. It applies to PostgreSQL, MySQL and to an Odoo database connected directly. It does not apply to a Bridge or API-key connection, which read Odoo models, not tables.
Lets an owner or admin hide tables of a SQL connection from a member. STYD then refuses any query that touches them. It applies to PostgreSQL, MySQL and to an Odoo database connected directly. It does not apply to a Bridge or API-key connection, which read Odoo models, not tables.
Table hiding is not a permission in Odoo
Hiding a table in STYD removes it from STYD's answers for that member. It does not change who can see that data in Odoo, and it does not change your database permissions.
A simple example
Suppose payroll data should be off-limits to most people. In Odoo, keep it in a group that the Odoo users behind your connection do not have. STYD never reads HR data through a Bridge or API-key connection in any case. On a directly connected Odoo database, hide the payroll tables for the members who should not see them, and use a read-only database user. See Hide tables from users.