Control Each role for each part of a different project

Nicole Ogloza_x072nc

Hello, I have this challenge where I want to figure out how each permission is being controlled for EACH person and understand what it really means and how you can CONTROL each part of the role.... Meaning:

Can the admin give permission at the site level, define me as a user, in a PROD envionment and gives permission in the Sandbox at the site level and ALSO define indie of PROD, while  being a project admin for that particular project ONLY (lets say X person is in cahnge of ONLY X Project and can ONLY do X, while Y person is in charge of Y project and can ONLY do Y)

I know this has to do something with security but I want to see how I can do this across the site level and individually for certain projects and permissions.

If someone can give me a screenshot example of the steps or call me that would be great!

This is CRITICAL on our list to solve right now!!!!!

Ste Wright

Hi @Nicole Ogloza

Can I confirm I understand your need correctly?

• A site-admin needs to have site-level permissions to define users in PROD
• Site Admins also need permission in the Sandbox and be able to give you Site-Admin (independent of PROD)
• Site-Admins / Users can be Project Admins and should only have project admin access for their projects

^ Let me know if I got this incorrect. I'm assuming your Sandbox is a separate site to Production - using a method such as these here - to be clear upfront, you can manage permissions independently on each environment you have.

These pages explain permissions in more detail - so for each point:

1. Groups: To edit who is a Site Admin, see the instructions in this page on groups. These have access to user management, and you can see the differences between each group down the right-hand side of the table.
2. Global Permissions: These are site-wide permissions which affect users abilities across the whole of each environment. See the information in this page on how to set these for user groups.
3. Project Permissions: See this page on how to create these - allowing you create permission schemes per project. You can assign lots of user types to permissions, such as user groups - or, control access to permissions per project using project roles (like in your screenshot above). So for example you could set "Administer Projects" to only be possible for the project role "Administrators" - then Site Admins could be excluded from this.
4. Issue Security: For completeness, for more granular access per issue, see this page.

^ These all apply to Classic projects, for Next-Gen projects there are no permission schemes at this point just a standard set per project role. Click here to learn more about Next-Gen permissions.

Let us know if you need any more specifics to help you solve a particular problem

Ste