Inviting members
A workspace becomes useful the moment a second person can see what you're doing in it. This page covers how to add people, the three roles, and the limits of what workspace membership grants.
Goal
You finish this page with one or more teammates added to your workspace at the right role.
Prerequisites
- A workspace you own or where you have admin role.
- Your teammate's account already exists in your tenant. Workspace invites add existing accounts to the workspace; you can't invite someone who isn't already a QRY user (an admin has to provision their account first).
Steps
1. Open the workspace settings
Click the workspace card from Workspaces and open Settings from the workspace's top toolbar.
2. Add a member
In the Members section, type the user's email or name. QRY autocompletes from existing tenant users.
3. Pick a role
Choose one of three roles for the new member:
| Role | Can read | Can edit | Can manage |
|---|---|---|---|
| Viewer | Conversations, files, dashboards in the workspace | — | — |
| Editor | Same as viewer | Create / edit / delete conversations, files, dashboards | — |
| Admin | Same as editor | Same as editor | Invite / remove members, change roles, change workspace settings, delete the workspace |
A workspace must have at least one Admin. The owner is always an admin and can't be downgraded by themselves.
4. Save
The member sees the workspace immediately on their next page load.
What workspace membership does and doesn't grant
Membership grants:
- Read access to every conversation in the workspace.
- Read access to every uploaded file in the workspace, including for RAG context in chat.
- Access to the workspace's shared AI memory (read for everyone; write for editors and admins).
Membership does not grant:
- Datasource access. RBAC at the datasource / catalog / schema / table level is checked separately. A workspace member without a datasource grant will see workspace files and conversations, but cannot run new queries against the datasource. They'll see Permission denied on attempting to chat against it.
- Cross-workspace visibility. Other workspaces remain invisible.
Removing a member
Same place: click Remove on the member's row. Their access is revoked immediately. Conversations they authored stay in the workspace; they just can't see them anymore.
Common issues
The autocomplete returns no results when I type a teammate's email. That email isn't on the tenant yet. An admin needs to invite them at the tenant level first (see Users and groups).
A member can see workspace conversations but every query fails. RBAC, not workspace. Confirm the member has a datasource grant — see Connecting databases for the admin side.
I want to give a member read-only access but they can still upload files. Editor uploads files; Viewer only reads. Pick Viewer for read-only.
The "Remove" button is missing. You're not an admin of the workspace. Ask the workspace owner.
See also
- Creating a workspace — set up the workspace before inviting.
- Shared files and memory — what members can see and write into.
- Moving conversations — bring an existing conversation into the workspace.
- RBAC — datasource-level grants, separate from workspace membership.