User permissions — who can change what on your team
Each person on your Team PM OS has a role that controls what they can edit directly and what goes through an approval step.
When to use this
- You want to understand what your role lets you do
- You are onboarding a new teammate and need to explain the permission model
- You are an Admin setting up roles for your team
Setup
- Open mySecond and go to Team in the sidebar.
- Your role appears next to your name — Admin, Lead, or Contributor.
- To change a teammate's role, you must be an Admin. Select the teammate and choose a new role from the dropdown.
How it works
There are three roles: Admin, Lead, and Contributor.
| Role | Context files | Change requests | Users and billing | Product areas |
|---|---|---|---|---|
| Admin | Edit directly | Approve or deny | Manage | Restricted to assigned products |
| Lead | Edit directly | Approve or deny | No access | Restricted to assigned products |
| Contributor | Submit for approval | Cannot approve | No access | Restricted to assigned products |
Contributors cannot edit context files directly. When a Contributor makes a change, it becomes a change request that a Lead or Admin reviews. The Lead or Admin approves or denies it before anything updates in the PM OS.
Leads can edit context files directly and approve or deny change requests. They cannot manage billing or add and remove users.
Admins have all Lead capabilities, plus the ability to manage billing and manage users on the team.
All roles — including Admins — are restricted to the product areas they are assigned to. A Lead on the mobile app product cannot edit context for the platform team.