What Each Role Can Do
What you can use and change in EM-OS depends on your role. This page lists who can do what, and the exceptions. For how roles are assigned, see Administration; for the features each plan includes, see Plans and Features.
Kinds of roles
There are two kinds of roles, and every user has both.
| Kind | Role | Description |
|---|---|---|
| Organization-wide | Admin | Manages organization settings, members, the subscription, and salary and rate information |
| Organization-wide | Member (user) | Everyone who is not an admin. Uses the standard features |
| Team | Lead | Responsible for a team. Edits and approves the team's information |
| Team | Member | A member of the team |
- Team roles are set per team. You can be a lead of one team and a member of another.
- A lead of a parent team is treated as a lead of the teams below it.
- Being an admin does not always let you edit a team's information. Team settings, adding members, and 1on1s belong to the team's lead (admins create and edit teams and assign members from the admin screens). That depends on whether you are the team's lead or an admin (see the table below).
Screens in the side menu
The side menu shows only the screens you can use.
| Screens | Shown to |
|---|---|
| Personal (dashboard, skills, 1on1s, work log, and so on) | Everyone who is logged in |
| Team (overview, members, capability analysis, tech skill management) | Leads of the team |
| Team (OKRs, surveys, expectation definitions) | Everyone (who can edit is in the table below) |
| Technical and Product | Everyone (who can edit is in the table below) |
| Admin screens (employees, teams, organization settings, audit logs, and so on) | Admins only |
What each role can do, by feature
"Lead" means a lead of the team concerned. A feature marked "not admins" cannot be changed by an admin who is not also the team's lead.
| Feature | View | Create | Edit or delete |
|---|---|---|---|
| ADRs (architecture decision records) | Everyone | Leads, admins | Lead of the ADR's team, admins |
| Technical debt | Everyone | Leads, admins | Lead of the item's team, admins |
| Services (products) and SLOs | Everyone | Leads, admins | Lead of the service's team, admins |
| Post-mortems | Everyone (only the owning team before publishing) | Team members and leads | Drafts: members and leads. Publishing: leads only |
| Technical roadmap | Everyone | Leads, admins | Leads, admins |
| Engineering metrics | Everyone | Lead of the team | Lead of the team (not admins) |
| Team surveys | Everyone | Leads, admins | Lead of the team, admins |
| Projects and backlog | Everyone | Leads, admins | Lead of the team, admins |
| Resource allocation | Everyone | Your own | Others' allocations: lead of the project's team, admins |
| Growth loops | Everyone | Leads, admins | Lead of the team, admins |
| OKR cycles | Everyone | Admins | Admins |
| OKR objectives | Everyone | Organization: admins. Team: lead of the team, admins. Personal: the owner, the owner's team lead, admins | Same |
| 1on1s | Participants and the team lead | Everyone | Participants and the team lead (not admins) |
| Team settings, adding members | Team members | — | Lead of the team (not admins; admins add members from the admin screens) |
| Skill approval | — | — | Lead of the applicant's team (not the applicant) |
| Tech skill approval | — | — | Admins (not the applicant) |
| Job titles and grades | — | — | Admins |
| Salary, rates, and costs | Admins | — | — |
| Inviting members | — | Admins | — |
| Subscription and invoices | Admins | — | Admins |
| Organization settings, team topology | Everyone | — | Admins |
Exceptions
ADRs
- Review (approve or reject): besides the ADR's team lead and admins, the person named as the reviewer can review, even from another team. The person who proposed the ADR cannot, even as a lead or an admin.
- Pinning: only people who can edit the ADR (its team lead or an admin) can pin or unpin it, because the pin is part of the ADR that everyone sees.
- Moving to another team: moving an ADR, technical debt item, or backlog item to another team takes a lead of both the current and the new team (or an admin).
- ADRs and technical debt without a team: only admins can edit them.
Post-mortems
- Only the lead of the product's team can publish.
- Content under review cannot be changed, even by a lead. To change it, reject it and send it back to draft.
- Deleting is for the team lead, or for the author before publishing.
- Only the team lead can change the owner.
R&D management
- Only the person who created a theme can change or delete it or add people to it. Admins cannot.
- The creator and the assigned people can register outputs.
Personal information
- Member activity insights: visible to the member and to leads of the member's teams. Admins cannot see them.
- The contents of skill requests (evidence and comments): visible to the member, the team lead, and admins. Other members see only approved skills.
- 1on1s: visible to participants and the team lead.
Admins
- Admin screens and features, including viewing, are for admins only (they include employees' labor costs).
- Admins assign the admin role. The platform super user role is assigned by the platform operator only.
If something does not work
- If you see a "no permission" message, check the role you need in the tables above and ask an admin or your team lead.
- Admins change roles from the admin screens.
