Roles & permissions

Who can do what inside a workspace, and how that changes by plan.

Role types

Roles are scoped to a single workspace. The same person can be an owner in one workspace and a viewer in another.

RoleIntended forSummary
OwnerAccount creator / workspace ownerFull control over billing, workspace settings, members, and data import/export.
AdminOps / team leadsManage initiatives and most workspace configuration, invite/remove members, but cannot transfer ownership.
MemberCore contributorsCreate and edit initiatives, comment, and export views they can see. Cannot change billing or member roles.
ViewerStakeholders / read‑only accessView dashboards and leave comments. Cannot create or edit initiatives or change settings.

Permission matrix

This table reflects the current behaviour in the app (see dashboard + Settings). Rows marked “owner / admin only” are enforced in the UI, and are progressively being tightened at the API layer.

CapabilityOwnerAdminMemberViewer
View initiatives and dashboards✓✓✓✓
Create / edit initiatives✓✓✓—
Delete initiatives✓✓——
Import data (AI parsing, files)✓✓✓—
Export data (CSV from views)✓✓✓—
Manage workspace settings✓✓——
Invite / remove members✓✓——
Access billing & plan changes✓owner‑only in current version——
View audit log✓✓——

Plan‑level differences

Roles control who can perform an action; plans control how much a workspace can do. The most important interactions between the two:

  • Free: 1 member maximum (owner only). Invitations are blocked once the workspace reaches its member limit.
  • Team: up to 5 members included. Owners / admins can invite up to the limit; beyond that, upgrades are required.
  • Business: up to 25 members included. Same role semantics as Team, higher member cap.
  • Enterprise: custom limits and approvals. Exact rules are configured per‑account with our team.

Member limits are enforced at the API layer when creating invitations and adding workspace members. See /docs/billing for pricing details.