Permissions Reference
Permissions are stored as a bitmask on each role. The UI groups them into three sections when editing roles.
Team permissions
| Permission | What it allows |
|---|---|
| Manage Team | Edit team name, avatar, visibility; manage roles (with rank rules) |
| Manage Members | Invite, revoke, kick members; change roles (with rank rules) |
| Manage Billing | View invoices, edit billing profile, open Stripe portal, change plan |
| Create Spaces | Create new top-level spaces |
| Manage Spaces | Edit/delete any space in the team; team-wide space admin |
| View Tasks | See other members’ Gantt charts and the team-wide workload/overburdened summary on the Tasks page |
Space & page defaults
These apply team-wide as defaults for roles. Private spaces/pages still require explicit membership.
| Permission | What it allows |
|---|---|
| Read Spaces | View spaces and their contents |
| Write Spaces | Create pages inside spaces |
| Manage Spaces | Space settings, members, delete space |
| Read Pages | View decision lists and decision detail |
| Write Pages | Create/edit decisions (subject to lifecycle freeze) |
| Delete Pages | Archive/delete pages and decisions |
| Post Comments | Add comments on decisions |
| Upload Files | Attach files to decisions/comments |
| Manage Comments | Moderate or delete others’ comments |
Global authority
| Permission | What it allows |
|---|---|
| Administrator (Owner flag) | Full bypass — equivalent to Owner role |
Decision-scoped permissions
Separate from the team/space/page bitmask above, each involvement position carries its own small permission set that only applies on decisions using that position’s configuration, and only to the people currently assigned to that position:
| Permission | What it allows |
|---|---|
| View | See the decision even if space/page visibility would otherwise hide it |
| Comment | Post comments on the decision |
| Edit Content | Edit decision fields while it is in Draft |
| Sign Approve | Sign the Proposed → Approved transition when this position gates it |
| Sign Reject | Sign the Proposed → Rejected transition when this position gates it |
| Sign Implement | Sign the Approved → Implemented transition when this position gates it |
| Manage Positions | Reassign who holds each position on this specific decision |
These stack on top of—never replace—your regular team/space/page permissions. See Involvement Positions & Signatures.
Rank rules
When editing members or roles:
- You cannot modify users at or above your rank (except Owner).
- You cannot assign a role above your own rank.
- You cannot grant permission bits you do not hold (except Owner).
Private spaces & pages
If a space or page is Private, the user must appear in that space’s or page’s member list even if their team role would otherwise allow access. Owner always bypasses this.
API vs UI
The app exposes effective permissions as myPermissions on team/space/decision payloads, and myDecisionPermissions for the decision-scoped bitmask above. The UI hides buttons (Create Space, Decision, Settings, Export, Sign, etc.) when the relevant bit is absent.