Start with what the person needs to do. Someone who needs to file a bug does not necessarily need control of billing, integrations, or the rest of the organization.
These steps are for organization admins.
Change a person's organization role
- Open Organization Settings and choose Users.
- Find the person and check that you have the right account.
- Open their Role field and choose the intended role.
- Read any confirmation and check the saved role.
Admin gives full organization control. Developer and Member are more limited starting points. Custom roles and additional permissions can change what a person can do, so do not rely on the role's name alone.
The app protects the last remaining admin and prevents you from changing your own role through this table.
Limit which projects a person can access
- In Users, find the person's Projects control.
- Open Project access.
- Choose All projects, including ones added later, or Only the projects I choose.
- Select the intended projects and choose Save project access.
Project-limited access also affects what appears elsewhere in the app. It can restrict areas such as Lyra and reports, not just hide project names. Organization admins retain access to all projects.
Make someone an admin of one project
- Open the project and choose Manage, then People and approvals.
- Find Project admins.
- Select the person in Admins of this project only.
- Choose Save Project Admins.
Project-admin access applies to that project. It does not make the person an organization admin or grant billing and membership control. Some actions, including choosing other project admins and deleting a project, remain organization-admin actions.
If a control is still unavailable, check the person's actual role permissions and project access before granting broader access.