Workspaces and roles
Who can see what, who can change what, and how a machine gets in.
Workspaces and members
A workspace is the unit of sharing. Its members share the audiences, surveys, runs, focus groups and uploads made inside it, and they share one credit balance. Rows are always scoped to the workspace, and each one shows who made it. No query in the product returns another workspace's rows.
Members are invited by email from /app/settings#workspace. There is no public sign-up form: an invitation, or an access request that someone approves, is how an account comes to exist. A member who should no longer have access is disabled rather than deleted, so the work they did keeps its author.
Roles
| Role | Can do |
|---|---|
| Member | Everything the product does inside the workspace: build audiences, run surveys and focus groups, upload, export, create their own API keys. |
| Workspace admin | All of that, plus rename the workspace, invite and remove members, change roles, and manage the plan and credits. |
| Superuser | A platform operator, not a workspace role. Sees every workspace, sets plans and grants credits anywhere, and uses the system admin area. Being an admin of a workspace does not make you one. |
Pages you do not have the role for return a not found rather than a forbidden, so the existence of an admin area is not advertised by the response. Signed out, any app page sends you to the login screen and back to where you were headed afterwards.
API keys
API keys are personal, not shared. Create one at /app/settings#keys; it is shown once, on the page that created it, and only a hash is kept, so it can never be shown again and never travels through a URL or an email. Keys look like uk_ plus 32 characters and are sent as Authorization: Bearer uk_....
A key acts as you, in your workspace, spending your workspace's credits. Revoke one from the same page and it stops working at once. The list shows only the first few characters of each key, which is enough to tell them apart. Personal API keys are part of the Pro plan and above.
Connected apps
Applications that connect through the sign-in flow rather than a key, such as Claude as a custom connector, appear under Connected apps at /app/settings#connected. Each entry names the application and when it was approved.
Disconnecting one revokes its access immediately. Its access tokens are short-lived and its refresh token is rotated every time it is used, so a disconnected application cannot quietly carry on. Setting one up is on Connect to Claude.