Table restrictions

You can restrict which tables a member can use, so STYD focuses on the right data and stays away from tables a member should not touch.

What restriction does

Hiding a table from a member removes it from that member's AI Guide view and from the queries STYD runs for them. If their question needs the table, the answer says that part of the data is hidden for them. It is managed as part of the AI Guide table visibility, one member at a time.

This helps reduce accidental exposure and keeps STYD focused on relevant data.

Restriction is not a database permission

Restricting a table in STYD is not the same as a database GRANT or REVOKE. It changes what STYD does for that member; it does not change who can read that table at the database. For sensitive tables, also protect them at the database and, for Odoo, in Odoo.

Use both layers

Combine STYD table restriction with database (and Odoo) permissions. Restriction simplifies and reduces exposure in STYD; database controls are the real enforcement.