REFERENCEReference
Who sees and does what in Forge
Forge access comes from each member's role on the team: user, manager, or admin. Whoever has no Forge role doesn't see the module. Roles are set in team member management.
What each role sees
| Page | User | Manager | Admin |
|---|---|---|---|
Inbox, Issues board, Ciclos, Initiatives, Domains, Design | Yes | Yes | Yes |
Bloqueios (Impediments) | — | Yes | Yes |
Repositórios (Repositories) | — | — | Yes |
GitHub (integration) | — | — | Yes |
Items outside the role don't show up in the navigation — for a user, it's as if Bloqueios, Repositórios, and GitHub didn't exist.
What each role does
| Action | Who can |
|---|---|
| Create and edit issues, cycles, initiatives, domains, and designs | All roles |
| Flag an impediment | Managers and admins on any issue; users only on the issues assigned to them |
| Resolve an impediment | Managers, whoever flagged it, or the issue's assignee |
| View another engineer's Inbox | Managers and admins |
| Delete a design | Admins, managers, or whoever created the design |
| Connect GitHub and manage the installation | Admins |
| Sync repositories and link them to domains | Admins |
| Generate and re-analyze the repository profile | Admins |
Two exceptions that don't follow the Forge role
Gerar notas de release(Generate release notes) depends on the permission to edit Wiki pages — see Wiki permissions.Fechar issues ao mesclar PR(Close issues on PR merge) can only be changed by team admins or team managers — the team role, not the Forge one — and saving requires two-factor authentication.
For the general role model in Movitera®, see workspace permissions.