Roles & Permissions

Every account in Broccoli has exactly one role, and every role is scoped to see only the data it's entitled to. There is no "see everything" role below Super Admin, and grants are additive and explicit — nobody accumulates visibility by accident.

Role	Persona	What they can do
admin	Manager	Full control of their own team: roster, 1:1s, goals, quarters, roadmap, wiki, docs
viewer	Team Access	Read-only view of their team's roadmap and JIRA Live
agent	AI Agent	Programmatic, read-only access scoped to one team
director	Director	Read-only rollup across every team that's granted them access
executive	Executive (VP/President)	Same as Director, with a distinct title for exec-level reporting
program_manager	Program Manager	Cross-team rollup, plus edit rights (status/priority/dates) on granted teams' roadmaps
product_manager	Product Manager	Full read/write on one or more granted teams' roadmaps
architect	Architect	Same model as Program Manager — cross-team oversight with edit rights
org_admin	Org Admin	Onboards Manager/Director/Executive accounts, monitors the org-wide audit log — no visibility into any team's work data
super_admin	Super Admin	Bootstraps Organizations and their Org Admins — the top of the hierarchy

The mental model

Workspace          the company — the tenant boundary, nothing crosses it
  └─ Organization  a business unit
      └─ Manager   owns one team's data outright
          └─ Team member

A Manager owns data outright — nothing they create is visible to anyone else until they grant it. Every other role either borrows a manager's scope through an explicit grant, or sits above the team layer administering accounts rather than reading work data.

Read-only roles are read-only in two places

Director, Executive, Program Manager and Architect visibility is enforced independently by the route/permission gate and by the underlying data-access check — so a read-only grant can never be escalated by a UI bug alone.

Choosing the right role

Situation	Role to grant
Runs a team's roster, 1:1s, goals and roadmap	Manager
A team member who should see the plan, not edit it	Team Access
Shepherds delivery across many teams, needs to nudge dates/status	Program Manager
Owns the backlog for one or more teams, needs full authoring	Product Manager
Cross-team visibility for technical/architectural reasons	Architect
Needs to watch and report upward, not edit	Director or Executive
Runs account administration for a business unit	Org Admin
Bootstraps whole companies	Super Admin

See the guide written for your role for the full walkthrough: Managers · Architects · Developers · Leadership · Organizations · Product & Program Managers.