Table visibility

Table visibility controls which tables each member can use when asking questions about a PostgreSQL or MySQL database. It is managed as part of the AI Guide.

Where it is managed

Open Settings → AI Guide, select a table, and use Table visibility for users. Owners and admins pick a member and choose Hide from this user. To show the table again, remove that member from the list.

It is set for each member

Visible tables
Tables a member can use. Every table starts visible for every member, including members who join later.
Hidden tables
Tables hidden from one member. They are removed from that member's AI Guide view, and STYD refuses any query that touches them for that member.
There is no switch to hide a table from the whole workspace. To hide a table from everyone, hide it from each member, and do the same for each new member when they join.

What the member sees

When a question needs a table that is hidden for that member, the answer says so plainly: part of the data the question needs is hidden for them in this workspace, set by the workspace admin. It does not show a zero or “nothing found”, and it does not name the table. This holds in the chat, through the API and in AI apps.

Hiding in STYD is not a database permission

Hiding a table in STYD controls what STYD uses for a member. It does not change your database’s own permissions. It should be treated as an extra safety layer, not the only one.

True access control belongs at the database level. A read-only database user with access only to the tables STYD should read is the real boundary; table visibility in STYD complements it.

Good to know

  • Table hiding applies to PostgreSQL and MySQL. On Odoo, what a member sees follows their own Odoo user (STYD Bridge) or the Odoo user of the API key.
  • Hiding works table by table. If the same data is copied into another table, hide that table too.
  • The Security section covers table restrictions and access controls in more depth.