Roles and rights
A capability is one thing Classifyre allows, such as source.manage. A
role is a fixed list of capabilities. A grant gives a group a role
on a place: one workspace, the workspaces a group owns, or the whole tenant.
Every API route and every MCP tool checks exactly one capability, so what a
role allows is exactly the list below.
The tables on this page are generated from the API’s own definitions
(apps/api/src/identity/roles.ts and capabilities.ts) every time the
API’s client is generated, so they always match what Classifyre enforces.
The roles
| Role | Key | Given | Capabilities |
|---|---|---|---|
| Viewer | viewer | On one workspace, every workspace a group owns, or the whole tenant | 15 |
| Investigator | investigator | On one workspace, every workspace a group owns, or the whole tenant | 21 |
| Curator | curator | On one workspace, every workspace a group owns, or the whole tenant | 21 |
| Source manager | source-manager | On one workspace, every workspace a group owns, or the whole tenant | 12 |
| Workspace admin | workspace-admin | On one workspace, every workspace a group owns, or the whole tenant | 44 |
| Data reader | data-reader | On one workspace, every workspace a group owns, or the whole tenant | 3 |
| Data reader, unmasked | data-reader-unmasked | On one workspace, every workspace a group owns, or the whole tenant | 4 |
| Dataset publisher | dataset-publisher | On one workspace, every workspace a group owns, or the whole tenant | 2 |
| Code author | code-author | On one workspace, every workspace a group owns, or the whole tenant | 2 |
| Workspace manager | workspace-manager | On every workspace a group owns, or the whole tenant | 45 |
| Auditor | auditor | On the whole tenant | 5 |
| Tenant admin | tenant-admin | On the whole tenant | 50 |
| Platform operator | platform-operator | Not granted in Classifyre: the identity server's realm role `classifyre-operator` | 1 |
| Visitor | visitor | Never granted: people who have not signed in, on the public tenant | 10 |
In plain words:
| Role | For |
|---|---|
| Viewer | Reading everything in a workspace, and personal MCP tokens, which can only read too. |
| Investigator | A Viewer who also triages findings, tags assets, works on cases and inquiries, reviews leads and asks the assistant. |
| Curator | A Viewer who also writes and approves glossary terms, manages entities and decides duplicates. |
| Source manager | Connecting sources, running scans and managing detectors. Sees findings and assets, not cases or inquiries. |
| Workspace admin | Everything in a workspace, settings and access included, except writing code and reading masked columns in clear. |
| Code author | An add-on, next to another role: custom source notebooks and code detectors run code on your infrastructure. |
| Data reader | An add-on, next to Viewer: reading the rows of tables with SQL. Can also be given on a single source or a single table. |
| Data reader, unmasked | Data reader who also reads the columns governance masks or hides (personal, sensitive, secret data) in clear — see Masked and hidden columns. Given on the same places. |
| Workspace manager | Creating workspaces for a group they belong to, and being Workspace admin on every workspace that group owns. |
| Auditor | The tenant’s audit trail and who has access, without seeing findings or content. |
| Tenant admin | Everything in the tenant: every workspace, every grant, the tenant’s activity. |
Roles sit side by side; none includes another by name. Someone who needs to investigate and curate gets both, through two groups or two grants to one group.
Roles nobody grants
- Platform operator is not a grant. Operators are the people with the
realm role
classifyre-operatorin the identity server (see The Platform page). They manage tenants and, through the identity console, people and groups. They never see inside a workspace unless a tenant also gives them a role. - Visitor is what everyone gets on a public workspace they have no grant on: people who have not signed in (first tenant only) and members of the tenant. It reads, but not who has access, not the tenant’s activity, no notifications and no MCP tokens. It is never offered.
Every capability, by role
● means the role holds the capability. Workspace manager is given on a group’s workspaces or the whole tenant; Auditor and Tenant admin on the whole tenant only; the others on any place.
| Capability | Viewer | Investigator | Curator | Source mgr | WS admin | Data reader | Data reader, unmasked | Dataset publisher | Code author | WS manager | Auditor | Tenant admin |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Workspace | ||||||||||||
workspace.viewOpen the workspace. | ● | ● | ● | ● | ● | · | · | · | · | ● | ● | ● |
workspace.settingsChange workspace settings, embeddings, maintenance and background queues. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
workspace.pausePause and resume the workspace. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
workspace.publishMake the workspace public (read-only for everyone of the tenant, and for visitors of the first tenant) or private again. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
workspace.deleteDelete the workspace. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
access.viewSee who has access to the workspace. | ● | ● | ● | · | ● | · | · | · | · | ● | ● | ● |
access.manageGive and remove access to the workspace. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
| Sources and scans | ||||||||||||
source.viewRead sources and their scans. Their configuration and notebook code need source.manage. | ● | ● | ● | ● | ● | · | · | · | · | ● | · | ● |
source.manageCreate, change and delete sources. | · | · | · | ● | ● | · | · | · | · | ● | · | ● |
source.runStart, stop and re-run scans. | · | · | · | ● | ● | · | · | · | · | ● | · | ● |
source.purgeRemove the assets or findings a source produced. | · | · | · | ● | ● | · | · | · | · | ● | · | ● |
| Findings and assets | ||||||||||||
finding.viewRead findings, extractions and their evidence. | ● | ● | ● | ● | ● | · | · | · | · | ● | · | ● |
finding.triageChange finding status and severity, alone or in bulk. | · | ● | · | · | ● | · | · | · | · | ● | · | ● |
asset.viewRead assets, lineage, connections and duplicates. | ● | ● | ● | ● | ● | · | · | · | · | ● | · | ● |
asset.tagTag assets, add or remove connections, save explore views. | · | ● | · | · | ● | · | · | · | · | ● | · | ● |
asset.governGovern assets: owners, stewards, custodians, descriptions and lifecycle. | · | · | ● | · | ● | · | · | · | · | ● | · | ● |
| Detectors and code | ||||||||||||
detector.viewRead detectors, their tests and training history. | ● | ● | ● | ● | ● | · | · | · | · | ● | · | ● |
detector.manageCreate, change and delete detectors and their tests. | · | · | · | ● | ● | · | · | · | · | ● | · | ● |
detector.trainTrain detectors and give them feedback. | · | · | · | ● | ● | · | · | · | · | ● | · | ● |
code.authorWrite and run code: custom source notebooks and code detectors. | · | · | · | · | · | · | · | · | ● | · | · | ● |
| Investigations | ||||||||||||
case.viewRead cases, their boards, threads and timelines. | ● | ● | ● | · | ● | · | · | · | · | ● | · | ● |
case.editCreate cases and work on them. | · | ● | · | · | ● | · | · | · | · | ● | · | ● |
case.manageClose, reopen, clean up and delete cases. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
inquiry.viewRead inquiries and their matches. | ● | ● | ● | · | ● | · | · | · | · | ● | · | ● |
inquiry.editCreate, change and delete inquiries. | · | ● | · | · | ● | · | · | · | · | ● | · | ● |
lead.reviewPropose, accept and dismiss case leads. | · | ● | · | · | ● | · | · | · | · | ● | · | ● |
| Glossary and entities | ||||||||||||
glossary.viewRead the glossary, bindings and semantic links. | ● | ● | ● | · | ● | · | · | · | · | ● | · | ● |
glossary.editWrite glossary terms, schemes, relations and bindings. | · | · | ● | · | ● | · | · | · | · | ● | · | ● |
glossary.approveApprove glossary terms, bindings and suggestions. | · | · | ● | · | ● | · | · | · | · | ● | · | ● |
entity.viewRead entities and their values. | ● | ● | ● | · | ● | · | · | · | · | ● | · | ● |
entity.manageCreate, merge and change entities. | · | · | ● | · | ● | · | · | · | · | ● | · | ● |
correlation.reviewDecide duplicates and change correlation settings. | · | · | ● | · | ● | · | · | · | · | ● | · | ● |
| Assistant, export and MCP | ||||||||||||
agent.viewRead agent configuration, runs, memory and AI providers. | ● | ● | ● | · | ● | · | · | · | · | ● | · | ● |
agent.configureConfigure agents, AI providers and MCP servers. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
agent.useAsk the assistant and use AI completion. | · | ● | ● | · | ● | · | · | · | · | ● | · | ● |
data.exportExport data out of the workspace (query results, CSV). | · | · | · | · | ● | · | · | · | · | ● | · | ● |
data.queryQuery the rows of tables with SQL: every table here, or only the sources and tables a grant names. | · | · | · | · | ● | ● | ● | · | · | ● | · | ● |
data.unmaskRead the columns governance masks or hides (personal, sensitive, secret) in clear. | · | · | · | · | · | · | ● | · | · | · | · | ● |
data.connectCreate your own SQL connections for BI tools and drivers (PostgreSQL protocol). | · | · | · | · | ● | ● | ● | · | · | ● | · | ● |
data.connection.manageSee, give and revoke the SQL connections of everyone in the workspace. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
mcp.token.ownCreate and revoke your own MCP tokens. | ● | ● | ● | ● | ● | · | · | · | · | ● | · | ● |
mcp.token.adminSee and revoke every MCP token of the workspace. | · | · | · | · | ● | · | · | · | · | ● | · | ● |
| Tenant | ||||||||||||
tenant.workspace.createCreate workspaces for a group you belong to. | · | · | · | · | · | · | · | · | · | ● | · | ● |
tenant.access.manageManage grants across the tenant. | · | · | · | · | · | · | · | · | · | · | · | ● |
tenant.categories.manageManage workspace categories. | · | · | · | · | · | · | · | · | · | · | · | ● |
tenant.audit.viewRead the tenant audit trail. | · | · | · | · | · | · | · | · | · | · | ● | ● |
Where a grant applies
| Given on | Reaches | Where to give it |
|---|---|---|
| One workspace | That workspace | The workspace’s Settings → Access, or Tenant access |
| The workspaces of a group | Every workspace owned by that group or by a group under it, now and later | Tenant access |
| The whole tenant | Every workspace of the tenant, and the tenant’s own pages | Tenant access |
A grant can end on a date (Until). After that it counts for nobody and stays listed until someone removes it.
Rules that always hold
- Access only adds up. No grant takes anything away.
- Nobody gives more than they have. A workspace admin cannot make anyone a Code author, because writing code is not theirs to give — nor give Data reader, unmasked, unless a tenant admin gave them that role on the workspace.
- Creating a workspace needs membership. A Workspace manager creates workspaces only for a group they are in (or under). Only tenant admins may create one for any group of the tenant.
- MCP tokens act as their creator, and never beyond what the creator may do at the moment the token is used.