DocumentationRoles & PermissionsDefault Roles

Default Roles

Every new team receives four built-in roles. You can create additional custom roles in Team Settings → Roles.

Roles are ordered by rank (zIndex). Higher rank can manage lower rank—not the reverse.

Owner

  • Rank: highest (system maximum)
  • Colour: red (#ef4444)
  • Permissions: Administrator flag — bypasses all permission checks
  • Special rules:
    • Cannot be removed from the team
    • Cannot leave the team voluntarily
    • Only Owners see Delete Team
    • Billing and Stripe portal require Owner or explicit Manage Billing

There is exactly one logical “owner” member (the user who created the team, unless transferred manually via DB/admin).

Admin

  • Rank: 90
  • Colour: orange
  • Typical use: team leads, ops, IT

Includes all standard permissions except the Administrator bypass:

  • Manage Team, Members, Billing
  • Create & Manage Spaces
  • Full space/page defaults: read, write, manage spaces; read, write, delete pages; comment, attach, manage comments

Admins can approve/reject decisions and reset lifecycle status.

Editor

  • Rank: 80
  • Colour: blue
  • Typical use: contributors who propose and discuss decisions

Can:

  • Read spaces; write in spaces (create pages)
  • Read & write pages; comment; upload attachments

Cannot:

  • Manage team settings, billing, or members
  • Delete pages (unless given custom role)
  • Approve/reject decisions (unless promoted)

Member

  • Rank: 70 (lowest default — default for new invites)
  • Colour: grey
  • Typical use: read-only participants

Can:

  • Read spaces and pages
  • View decisions and discussions

Cannot create pages/decisions or comment unless given a higher role or scoped overrides (Pro+).

Changing roles

Team Settings → Members — requires Manage Members and sufficient rank.

Team Settings → Roles — edit permission checkboxes for custom roles; Owner role name is reserved.