Roles and Permissions
This page is the reference anchor for Phase 14.
ownerandadminshare 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.memberandviewercan 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.

Phase-Scoped Matrix
| Action | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| View billing status | Yes | Yes | Yes | Yes |
| Start Stripe Checkout | Yes | Yes | No | No |
| Open Stripe Portal | Yes | Yes | No | No |
| Invite members | Yes | Yes | No | No |
| Review pending invitations | Yes | Yes | No | No |
| Cancel invitations | Yes | Yes | No | No |
| Change another user's role | Yes | Yes | No | No |
| Load org member list through the custom API | Yes | Yes | No | No |
| Remove another member | Yes | Yes | No | No |
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
owneras the top-level role. Admins cannot grant ownership or modify/remove owners; ownership changes retain at least one owner atomically.

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