Roles and permissions
A workspace has three roles. Every member can query data through an AI tool, Admins also manage the workspace, and the Owner is the one Admin who cannot be removed.
What each role can do
The roles are Member, Admin and Owner. In the product's own terms, a Member is an analyst: the same role names are used for API keys and AI tools, so the permissions of a person and of a machine are the same sets.
| Action | Member | Admin | Owner |
|---|---|---|---|
| Connect an AI tool and query data | Yes | Yes | Yes |
| See products and the event list | Yes | Yes | Yes |
| Save queries, run them again and export results | Yes | Yes | Yes |
| See the AI tools connected to the workspace | Yes | Yes | Yes |
| Disconnect their own AI tools | Yes | Yes | Yes |
| Change their own profile, password and email | Yes | Yes | Yes |
| Leave the workspace | Yes | Yes | After transferring ownership |
| See API keys | – | Yes | Yes |
| Create and revoke API keys | – | Yes | Yes |
| Rename and delete products, delete events | – | Yes | Yes |
| Invite and remove members | – | Yes | Yes |
| Change a member's role | – | Yes, except the Owner | Yes |
| Disconnect another member's AI tools | – | Yes | Yes |
| Change the workspace name and the event retention | – | Yes | Yes |
| Transfer ownership | – | – | Yes |
| Delete the workspace | – | – | Yes |
The Owner
A workspace always has exactly one Owner, and at least one Admin, counting the Owner.
- The person who creates the workspace is its Owner.
- The Owner cannot leave, be removed or be demoted. To step down they transfer ownership to another member, and the previous Owner becomes an Admin.
- An Admin can leave or be demoted freely, because the Owner remains.
- Before the Owner deletes their account, each workspace they own that has other members must be transferred. A workspace where they are the only member is deleted with the account.
- An invitation carries a role: Member or Admin. Nobody can be invited as Owner.
- Deleting a workspace ends access within a minute: its keys and AI-tool connections stop working, and its data is destroyed after 30 days.
API keys and AI tools
Role and plan are separate. The role decides what a member may manage; the plan decides how much they can query. A Member can be on Max and an Owner can be on Free. A member sees their own plan and query credits on the Account page, see Plans and billing.
API keys hold a role of their own. A key is never an Owner. Keep an analyst or admin key on your server; never ship it in a client application.
| Key role | What the key can do |
|---|---|
ingest |
Sends events and nothing else. It cannot read data, so it is the key for a client application |
analyst |
Reads and queries data, for example for a dashboard. It cannot send events |
admin |
Everything an analyst can do and sends events, and manages products and keys and files and lists deletion requests through an AI tool's tools |
A key can never be given more than the member who creates it holds. Keys belong to the workspace, and each key records the member who made it: its queries run under that member's plan and use that member's query credits.
AI tools act with the role of the member who connected them, and a change of role reaches the tool within a minute. A Member's tool can read and query data, save queries and export results. An Admin's or the Owner's tool can also manage products and API keys and file requests to delete data. No AI tool can send events, invite people, change roles or settings or delete the workspace, whatever the role of the member behind it.
Removing a member disconnects their AI tools within a minute. The API keys they created keep working, because keys belong to the workspace, except that a key can run queries only while the member who made it is still in the workspace.