Admin & Governance

Permission matrix

Who can view, edit, approve, restrict, and grant access to revenue-impacting changes.

securityaccessgovernance
Last updated May 19, 2026

Solvren separates visibility from authority. Being able to see a change does not mean a user can edit its financial assumptions or make an approval decision.

| Role | View | Edit | Approve | Restrict / grant access | | --- | --- | --- | --- | --- | | Owner | Any active organization change, including restricted records | Any active change | Yes | Yes | | Admin | Any active organization change, including restricted records | Any active change | Yes | Yes | | Reviewer | Assigned, explicitly granted, or domain-visible in-review/approved changes | Assigned submitted or in-review changes | Yes, when domain review is allowed | No | | Submitter | Own changes, assigned changes, explicit restricted grants, and approved domain-visible changes | Own draft or ready changes | No | Own changes only | | Viewer | Approved domain-visible changes | Never | No | No |

Restricted changes require creator, assigned-reviewer, admin/owner, or explicit unexpired access. Domain review requires an explicit domain permission row for non-admin reviewers.

Trust commitments

  • View permission is not edit permission.
  • Time-boxed access grants remain valid until expiration and stop applying after expiration.
  • Revenue exposure edits, restriction changes, approval decisions, evidence changes, domain permission changes, integration changes, executive decisions, support access, and tenant purge actions are audit-relevant events.
✏️ Edit this page on GitHub
Was this page helpful?
Send feedback