This table shows what each organisation role can do. It reflects both what the workspaces offer and what the database allows. App access applies on top: apart from Admins, everyone sees only the apps they’ve been granted.
Legend: ✅ yes · 🔸 limited (see note) · — no
Roles: Adm Admin · PM Product Manager · Dev Developer · Tst Tester · UID UI Designer · Cli Client · Vwr Viewer
| Capability |
Adm |
PM |
Dev |
Tst |
UID |
Cli |
Vwr |
| Add, edit, revoke, restore, delete members |
✅ |
— |
— |
— |
— |
— |
— |
| Assign roles, app access, tester groups |
✅ |
— |
— |
— |
— |
— |
— |
| See all apps without being granted |
✅ |
— |
— |
— |
— |
— |
— |
| Read the audit log; delete aged entries |
✅ |
— |
— |
— |
— |
— |
— |
| Manage approval rules |
✅ |
— |
— |
— |
— |
— |
— |
| Capability |
Adm |
PM |
Dev |
Tst |
UID |
Cli |
Vwr |
| Create, edit, delete apps, tester groups, modules, submodules |
✅ |
— |
— |
— |
— |
— |
— |
| Create, edit, delete tasks; assign developer and groups |
✅ |
— |
— |
— |
— |
— |
— |
| Bulk import |
✅ |
— |
— |
— |
— |
— |
— |
| Edit planning fields and dependencies |
✅ |
— |
— |
— |
— |
— |
— |
| Browse the hierarchy tree and Kanban board |
✅ |
— |
— |
— |
— |
— |
— |
| Capability |
Adm |
PM |
Dev |
Tst |
UID |
Cli |
Vwr |
| See assigned tasks |
✅ all |
— |
🔸¹ |
🔸² |
— |
— |
— |
| Change a task’s workflow stage |
🔸³ |
— |
🔸⁴ |
— |
— |
— |
— |
| Cascade a stage to children (apps, modules, submodules) |
✅ |
— |
— |
— |
— |
— |
— |
| Reassign work |
✅ |
— |
— |
— |
— |
— |
— |
| Capability |
Adm |
PM |
Dev |
Tst |
UID |
Cli |
Vwr |
| Start and submit QA runs |
✅ |
— |
— |
🔸² |
— |
— |
— |
| View all QA runs and evidence |
✅ |
— |
— |
own |
— |
— |
— |
| Set device defaults |
— |
— |
— |
✅ |
— |
— |
— |
| Submit task requests |
— |
— |
🔸⁵ |
✅ |
— |
— |
— |
| Review task requests (publish, merge, review, reject) |
✅ |
— |
— |
— |
— |
— |
— |
| Update issue status and internal notes |
— |
— |
🔸¹ |
— |
— |
— |
— |
| View feedback history |
✅ |
— |
🔸¹ |
own |
— |
— |
— |
| Capability |
Adm |
PM |
Dev |
Tst |
UID |
Cli |
Vwr |
| View the release board and readiness |
✅ |
✅ |
— |
— |
✅ |
✅ |
✅ |
| Decide Admin, Security, Compliance approvals |
✅ |
— |
— |
— |
— |
— |
— |
| Decide Client approvals |
✅ |
— |
— |
— |
— |
🔸⁶ |
— |
| Decide Product Manager approvals |
✅ |
🔸⁶ |
— |
— |
— |
— |
— |
| Decide Developer approvals |
✅ |
— |
🔸⁷ |
— |
— |
— |
— |
| Decide QA approvals (normally recorded from QA runs) |
✅ |
— |
— |
🔸⁷ |
— |
— |
— |
| Send issue reports and suggestions |
— |
— |
— |
✅ |
— |
— |
— |
| Promote to Production (with or without override) |
✅ |
— |
— |
— |
— |
— |
— |
| Capability |
Adm |
PM |
Dev |
Tst |
UID |
Cli |
Vwr |
| Read and post comments on accessible items |
✅ |
✅ |
🔸⁸ |
🔸⁸ |
✅ |
✅ |
🔸⁹ |
| Read status history and activity timelines |
✅ |
✅ |
— |
— |
✅ |
✅ |
✅ |
| Own notification inbox and preferences |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
| See other members’ notifications |
✅ |
— |
— |
— |
— |
— |
— |
| Organisation-wide analytics |
✅ |
— |
— |
— |
— |
— |
— |
| Portfolio, roadmap and release analytics (own apps) |
✅ |
✅ |
— |
— |
✅ |
✅ |
✅ |
| Personal delivery analytics |
— |
— |
✅ |
— |
— |
— |
— |
| Personal QA analytics |
— |
— |
— |
✅ |
— |
— |
— |
- Developers see tasks where they are the assigned developer, in apps they can access, and the feedback on those tasks.
- Testers see and run QA on tasks that are in Staging, assigned to one of their tester groups, in apps they can access.
- Admins can set any stage except Production (reached only by promotion). Moving to Ready to Ship requires a passed QA result.
- Developers can move their own tasks: Backlog → Planned → In Progress → In Review → Staging, In Review → In Progress, and Staging → In Progress.
- Developers create task requests only by escalating a tester’s suggestion, once per suggestion.
- Product Managers decide Product Manager Approved, and Clients Client Approved, on items in Ready to Ship or Production in apps they can access.
- Permitted by the database (Developers on tasks only, and not their own task unless the rule allows self-approval), but the Developer and Tester workspaces don’t include the release board. QA Approved is recorded automatically when a tester submits a QA run.
- Permitted for items Developers and Testers can access, but their workspaces don’t show a comments panel yet.
- The Viewer workspace is intended to be read-only, but the comments panel on release candidates is available to Viewers.
Super Admin is a QA Sync platform role, not an organisation role, and doesn’t appear in this table. See Organisations and tenancy.
