Permissions
What each role can do, how project roles stack on workspace roles, and how PII clearance adds a second layer.
Tattva checks two things before it lets you act: your role (what you may do) and, for personal data, your PII clearance (what you may see). This page covers roles. Clearance is covered in Sensitive data.
How roles stack
- Workspace role: set on Settings › Workspace. See Workspaces & members.
- Project role (optional): a project can give someone a different role. If it doesn't, the workspace role applies.
- The check: actions that need a role are checked on the server. A denied action returns an error and is written to the audit log as
auth.forbidden. Some actions only check that you are signed in; they are listed below the table.
Roles rank Viewer, then Member, then Admin, then Owner. Ontology Admin ranks with Member and adds authority over the shared ontology.
What each role can do
| Action | Viewer | Member | Ontology Admin | Admin | Owner |
|---|---|---|---|---|---|
| Open projects, read sources and the ontology | ✓ | ✓ | ✓ | ✓ | ✓ |
| Ask questions in Reasoning | ✓ | ✓ | ✓ | ✓ | |
| Upload a source | ✓ | ✓ | ✓ | ✓ | |
| Create trackers and boards | ✓ | ✓ | ✓ | ✓ | |
| Approve requests in the Promotion Inbox | ✓ | ✓ | ✓ | ||
| Edit value groupings, family policies, settlement | ✓ | ✓ | ✓ | ||
| Approve a value mapping from a conflict | ✓ | ✓ | ✓ | ||
| Write to the Workspace Library | ✓ | ✓ | ✓ | ||
| Decide in Ontology › Maintain › Review on the Workspace Library project | ✓ | ✓ | ✓ | ||
| Start an ontology build (Regenerate, Build Ontology →, Rebuild) | ✓ | ✓ | ✓ | ||
| Create a project | ✓ | ✓ | |||
| Delete boards | ✓ | ✓ | |||
| Invite members, change roles, grant PII clearance | ✓ | ✓ | |||
| Read the audit log | ✓ | ||||
| Delete the workspace | ✓ |
New project in the workspace switcher only appears for Admins and Owners. The + New project link on the Home and Projects pages appears for every role, but the project is created only for Admins and Owners.
Actions any signed-in member can do
These check only that you are signed in, not your role:
- Accepting, deferring, rejecting or moving back to pending candidates, and reviewing or deleting corrections, in Ontology › Maintain › Review, in any project other than the Workspace Library. In the Workspace Library these need the Ontology Admin, Admin or Owner role (see the table); others see the queue read-only. A refused Review decision is written to the audit log as
rbac.denied. - Resolving or dismissing conflicts, except approving a value mapping (see the table).
- Saving an answer as a report, and deleting reports, trackers and sources.
- Renaming the workspace, and renaming or deleting a project on Settings › Project.
- Registering tools on Settings › Tools and editing notification subscriptions.
Agree in your team who does these. Accepting a metric definition in particular changes the numbers every answer uses, and reviewing a correction decides how the ontology is fixed; see Review what Tattva proposes.
Working answer feedback in Ontology › Maintain › Feedback (In review, team note, Create convention, Create correction, deciding or deleting a comment) needs the Owner, Admin or Ontology Admin role in every project; others see the list read-only, without team notes. Setting the project's Slack webhook for feedback on Settings › Project needs Admin or Owner. See Work answer feedback.
Starting an ontology build needs the Owner, Admin or Ontology Admin role on that project, in every project: a build rewrites what the project's answers read from and spends warehouse and model time. Anyone else, including a member of another project, is refused (HTTP 403) and the refusal is written to the audit log as rbac.denied. Following a build's progress needs any role on its project; to anyone else the build does not exist (HTTP 404). See Build the ontology.
PII clearance is separate
Your role decides what you can do. Your PII clearance decides which personal-data figures you can see in answers. Each member has a clearance tier (none, aggregated, unsafe aggregates, full), set by an Admin or Owner. A Viewer with full clearance sees raw personal data, and an Admin with none doesn't.
See Sensitive data for what each tier sees and how data analysts mark sensitive columns.
Slack channels
A Slack channel connected to a project (see Slack channels) acts in Tattva as its own member with fixed limits. It can ask questions and read the project and its glossary, nothing else, whatever role is shown. Its PII clearance is always none, so personal data in its answers is always masked. It can never sign in, and its conversations are read-only for everyone else.
Sharing
Everything in a project (sources, answers, trackers, reports, decisions, boards) is visible to the project's members. There is no link-sharing or per-item sharing with people outside the project.
A source can be used in another project of the same workspace. Its owner promotes it with ↑ Promote to workspace, and a reviewer approves the request in the Promotion Inbox. Other projects then use it read-only.
If you're denied
Most screens show an error when the server refuses an action. Two don't: on Settings › Workspace, a refused Invite or role change just leaves the member list unchanged. If you think you need the access, ask an Admin or Owner to change your role on Settings › Workspace.