Broccoli for Organizations
Who this is for: the person bringing Broccoli into a company — the workspace owner, and the Org Admins who run day-to-day account administration afterwards.
See Creating a workspace for the step-by-step setup wizard. This page covers what happens after setup — running the workspace day to day.
What each role will see
Give people the narrowest role that does their job:
| Role | Sees |
|---|---|
| Manager | Their own team's data, in full |
| Team Access | Their own team's roadmap and JIRA Live, read-only |
| Director / Executive | A rollup of every team that granted them access, read-only |
| Program Manager / Architect | A rollup, plus status/priority/date edits on granted teams |
| Product Manager | Full authoring on granted teams' roadmaps, no people data |
| Org Admin | Account administration for one organization — no team work data |
| Super Admin | Every organization in the workspace |
Running it day to day
Org Admin → Monitoring is your evidence trail: every authentication, account creation, permission grant and revocation, with actor, timestamp, IP and user agent. The audit log is append-only — nothing edits or deletes an entry.
Routine tasks:
- Someone joins a team — the manager approves the request, or provisions them directly.
- Someone changes team — revoke the old access grant, add the new one; their history stays.
- Someone leaves — revoke the account. Their roster record, notes and goals stay with the team.
- A new business unit appears — add an organization, appoint an Org Admin, add its teams.
If your workspace has more than one organization, an "Administering" dropdown appears for the workspace owner — it changes which organization every action on the page applies to. A plain Org Admin is pinned to one organization.
Next: For Leadership · For Managers