Docs › Workspaces and folders
Workspaces and folders
Roles
A workspace has owners and members. Members ask questions, upload data, pin dashboards and send reviews. Owners also manage members and roles, folder access, groups, the metric glossary, provider keys, the workspace API key and the connected database. The first account in a workspace is its owner; owners can promote members.
To add people, share the workspace's invite code (Workspace page). Signing up with it joins that workspace as a member. Owners can disable a member — their sessions end immediately and their data stays attributed to them.
Personal and shared folders
Tables and documents live in folders. An upload goes to your personal folder by default: visible to you and to the owners, to nobody else. Choosing a shared folder at upload, or moving an item out of a personal folder later, publishes it — the confirmation names who will be able to see it.
Owners control shared folders on the Workspace page: a folder can be open to everyone in the workspace, limited to named members, or limited to groups (for example a department). Access lists decide what a person can query and see; a folder someone cannot see does not appear for them anywhere — not in the data panel, not in search, not in the schema map. Pending access changes are shown before they are saved, and nothing changes until you apply them.
Chats and dashboards
Chats are private to the person who asked. Dashboards are visible to the whole workspace; a tile runs the saved query through the viewer's own access, so a tile on a table you cannot see shows nothing. A tile remembers the chat it was pinned from for its owner.
Reviews
A question's SQL can be sent for review. Owners choose who may review; a request goes to a shared queue, a reviewer records a verdict and can reply in a thread. The verdict is advisory: it tells the requester what a colleague concluded; it does not block or approve anything, and the requester, the reviewers and the owners are the only people who see it. A reviewer can propose a metric definition from a review; an owner saves it to the glossary.
Single sign-on
Multi-user installations can use an OpenID Connect provider (for example Microsoft Entra ID) for sign-in; the operator configures it per deployment. Hosted workspaces use email and password.
Owner tools on the Workspace page
| Section | What it does |
|---|---|
| Members | roles, invite code, disable, one-time password reset links |
| Access log | who changed access, roles and shared data, and when |
| Folder access | the folder × members matrix with explicit save |
| Groups | named member groups for folder access |
| Metric glossary | house definitions shown to the model as guidance |
| Provider keys | your own OpenAI, Anthropic or Ollama key; questions then run on your account |
| Workspace API key | programmatic access; metered as one seat of your plan |
| Connected database | PostgreSQL connection, tested before saving |
Deleting an account or a workspace
Open your profile (the credits chip, top right). A member deletes their own account by typing their email: their chats, personal tables and documents, settings and messages go; shared workspace data stays, and the audit trail keeps its rows with the email replaced by an opaque handle. A workspace owner deletes the whole workspace by typing its name: every member's account and all data go. Both are immediate and cannot be undone. A workspace on a paid plan must cancel its subscription in the billing portal first. Backups taken before a deletion age out on the operator's backup schedule.