User-specific restrictions

Within a workspace, roles and table visibility shape what each person can do and see in STYD.

Roles

Owner / Admin
Manage the workspace: connections, invitations, API keys, AI apps and table visibility. Only the owner changes roles, removes members and manages billing.
Member
Asks questions and reads the workspace settings, without changing them.
Viewer
Can read conversations but cannot ask questions, and cannot open Settings.

Private chat threads

Chat threads are private to the person who created them. Other members cannot see or open a thread unless the creator invites them, and only the creator can manage that sharing. This is per-thread and independent of role, and it is enforced on the server rather than only hidden in the interface. Conversations started with an API key are the exception: owners and admins can read them, read-only.

User-specific table visibility

Owners and admins can hide specific tables from specific members in the AI Guide. This is the only table visibility control: it is set for each member, and a new member starts with nothing hidden. STYD refuses queries on a hidden table for that member in the chat, through the API and in AI apps.

What this can and cannot control

These controls shape behavior inside STYD. They do not replace database or Odoo permissions, which decide what the underlying account can actually read. These controls are available on every plan. For sensitive data, enforce access at the database and in Odoo as well.