Skip to Content
Access & Sign-inRoles and rights

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

RoleKeyGivenCapabilities
ViewerviewerOn one workspace, every workspace a group owns, or the whole tenant15
InvestigatorinvestigatorOn one workspace, every workspace a group owns, or the whole tenant21
CuratorcuratorOn one workspace, every workspace a group owns, or the whole tenant21
Source managersource-managerOn one workspace, every workspace a group owns, or the whole tenant12
Workspace adminworkspace-adminOn one workspace, every workspace a group owns, or the whole tenant44
Data readerdata-readerOn one workspace, every workspace a group owns, or the whole tenant3
Data reader, unmaskeddata-reader-unmaskedOn one workspace, every workspace a group owns, or the whole tenant4
Dataset publisherdataset-publisherOn one workspace, every workspace a group owns, or the whole tenant2
Code authorcode-authorOn one workspace, every workspace a group owns, or the whole tenant2
Workspace managerworkspace-managerOn every workspace a group owns, or the whole tenant45
AuditorauditorOn the whole tenant5
Tenant admintenant-adminOn the whole tenant50
Platform operatorplatform-operatorNot granted in Classifyre: the identity server's realm role `classifyre-operator`1
VisitorvisitorNever granted: people who have not signed in, on the public tenant10

In plain words:

RoleFor
ViewerReading everything in a workspace, and personal MCP tokens, which can only read too.
InvestigatorA Viewer who also triages findings, tags assets, works on cases and inquiries, reviews leads and asks the assistant.
CuratorA Viewer who also writes and approves glossary terms, manages entities and decides duplicates.
Source managerConnecting sources, running scans and managing detectors. Sees findings and assets, not cases or inquiries.
Workspace adminEverything in a workspace, settings and access included, except writing code and reading masked columns in clear.
Code authorAn add-on, next to another role: custom source notebooks and code detectors run code on your infrastructure.
Data readerAn 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, unmaskedData 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 managerCreating workspaces for a group they belong to, and being Workspace admin on every workspace that group owns.
AuditorThe tenant’s audit trail and who has access, without seeing findings or content.
Tenant adminEverything 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-operator in 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.

CapabilityViewerInvestigatorCuratorSource mgrWS adminData readerData reader, unmaskedDataset publisherCode authorWS managerAuditorTenant admin
Workspace
workspace.view
Open the workspace.
●●●●●····●●●
workspace.settings
Change workspace settings, embeddings, maintenance and background queues.
····●····●·●
workspace.pause
Pause and resume the workspace.
····●····●·●
workspace.publish
Make the workspace public (read-only for everyone of the tenant, and for visitors of the first tenant) or private again.
····●····●·●
workspace.delete
Delete the workspace.
····●····●·●
access.view
See who has access to the workspace.
●●●·●····●●●
access.manage
Give and remove access to the workspace.
····●····●·●
Sources and scans
source.view
Read sources and their scans. Their configuration and notebook code need source.manage.
●●●●●····●·●
source.manage
Create, change and delete sources.
···●●····●·●
source.run
Start, stop and re-run scans.
···●●····●·●
source.purge
Remove the assets or findings a source produced.
···●●····●·●
Findings and assets
finding.view
Read findings, extractions and their evidence.
●●●●●····●·●
finding.triage
Change finding status and severity, alone or in bulk.
·●··●····●·●
asset.view
Read assets, lineage, connections and duplicates.
●●●●●····●·●
asset.tag
Tag assets, add or remove connections, save explore views.
·●··●····●·●
asset.govern
Govern assets: owners, stewards, custodians, descriptions and lifecycle.
··●·●····●·●
Detectors and code
detector.view
Read detectors, their tests and training history.
●●●●●····●·●
detector.manage
Create, change and delete detectors and their tests.
···●●····●·●
detector.train
Train detectors and give them feedback.
···●●····●·●
code.author
Write and run code: custom source notebooks and code detectors.
········●··●
Investigations
case.view
Read cases, their boards, threads and timelines.
●●●·●····●·●
case.edit
Create cases and work on them.
·●··●····●·●
case.manage
Close, reopen, clean up and delete cases.
····●····●·●
inquiry.view
Read inquiries and their matches.
●●●·●····●·●
inquiry.edit
Create, change and delete inquiries.
·●··●····●·●
lead.review
Propose, accept and dismiss case leads.
·●··●····●·●
Glossary and entities
glossary.view
Read the glossary, bindings and semantic links.
●●●·●····●·●
glossary.edit
Write glossary terms, schemes, relations and bindings.
··●·●····●·●
glossary.approve
Approve glossary terms, bindings and suggestions.
··●·●····●·●
entity.view
Read entities and their values.
●●●·●····●·●
entity.manage
Create, merge and change entities.
··●·●····●·●
correlation.review
Decide duplicates and change correlation settings.
··●·●····●·●
Assistant, export and MCP
agent.view
Read agent configuration, runs, memory and AI providers.
●●●·●····●·●
agent.configure
Configure agents, AI providers and MCP servers.
····●····●·●
agent.use
Ask the assistant and use AI completion.
·●●·●····●·●
data.export
Export data out of the workspace (query results, CSV).
····●····●·●
data.query
Query the rows of tables with SQL: every table here, or only the sources and tables a grant names.
····●●●··●·●
data.unmask
Read the columns governance masks or hides (personal, sensitive, secret) in clear.
······●····●
data.connect
Create your own SQL connections for BI tools and drivers (PostgreSQL protocol).
····●●●··●·●
data.connection.manage
See, give and revoke the SQL connections of everyone in the workspace.
····●····●·●
mcp.token.own
Create and revoke your own MCP tokens.
●●●●●····●·●
mcp.token.admin
See and revoke every MCP token of the workspace.
····●····●·●
Tenant
tenant.workspace.create
Create workspaces for a group you belong to.
·········●·●
tenant.access.manage
Manage grants across the tenant.
···········●
tenant.categories.manage
Manage workspace categories.
···········●
tenant.audit.view
Read the tenant audit trail.
··········●●

Where a grant applies

Given onReachesWhere to give it
One workspaceThat workspaceThe workspace’s Settings → Access, or Tenant access
The workspaces of a groupEvery workspace owned by that group or by a group under it, now and laterTenant access
The whole tenantEvery workspace of the tenant, and the tenant’s own pagesTenant 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.
Last updated on