Roles & capabilities

CartonCrew uses role + capability RBAC: the role gives a coarse defaults, capabilities are the fine-grained per-module on/off toggles.

Who this is for: Owner.

Roles

• Owner — billing + extensions + branding + wipes. One or two per tenant.
• Admin — manages everything except billing/extensions/branding. Typical “ED” or “ops lead”.
• Editor — creates and edits records in modules they have capabilities on.
• Viewer — read-only across the modules they have capabilities on.

Capabilities

Per-module fine-grained switches. Examples:

• events.manage — create / edit / publish events.
• requests.read — see requests but not edit.
• campaigns.send — actually fire the send button (separate from campaigns.manage, which lets you compose drafts).
• users.manage — invite + change users (Owner-only by default).

Pattern

• A Viewer with requests.read can list and open requests but can’t create or edit.
• An Editor with events.manage + volunteers.read can run events and look up the volunteer who signed up, but can’t edit the volunteer record.
• An Admin with all capabilities is the typical “ops lead” — everything short of billing.

Common issues

• A user can’t do X — check their role first, then the specific capability. The user-row’s “permissions” badge lists them.
• An Owner wants to demote themselves to Admin — fine, as long as at least one Owner remains. CartonCrew enforces the “≥1 Owner” rule.

Last updated: 2026-06-01 · Applies to: CartonCrew v1.54+