DOCS/Platform Docs/Team Management/Roles and Permissions

Roles and Permissions

This page is the reference anchor for Phase 14. owner and admin share ordinary management actions, but granting ownership or modifying/removing owners requires an owner (or the explicit platform super-admin bypass). The last owner cannot be removed or demoted. member and viewer can view billing state, but they cannot perform the management actions in this phase.

Use this matrix when you need to confirm what a role can do before following the invite or removal guides.

The users table state for a privileged account that can manage invitations and member access.
A privileged session exposes the role controls and member-management actions described in the matrix below.

Phase-Scoped Matrix

ActionOwnerAdminMemberViewer
View billing statusYesYesYesYes
Start Stripe CheckoutYesYesNoNo
Open Stripe PortalYesYesNoNo
Invite membersYesYesNoNo
Review pending invitationsYesYesNoNo
Cancel invitationsYesYesNoNo
Change another user's roleYesYesNoNo
Load org member list through the custom APIYesYesNoNo
Remove another memberYesYesNoNo

Implementation Caveats

The matrix describes backend organization permissions, not a guarantee that every UI control is correctly hidden. OrgContext derives UI permissions from the active org membership role, separately from platform roles. Product Subscribe and subscription-card Manage buttons are permission-gated, and the server independently rejects unauthorized billing requests. Payment-method details require owner/admin membership; subscriptions and invoices allow org-member reads.

How To Read It

  • Use the billing rows to decide whether you can start checkout or open Stripe Portal.
  • Use the team rows before you invite, cancel, re-role, or remove anyone.
  • Treat owner as the top-level role. Admins cannot grant ownership or modify/remove owners; ownership changes retain at least one owner atomically.
The read-only users table state for a viewer account without management controls.
Read-only sessions do not expose invite, role-change, or removal controls; the custom member-list API also requires owner/admin access.

Next Step

Continue to Remove Members if you need the final access-revocation guide.