What is the fastest way to set permissions or security on projects?

Karen_srkpe8

Currently we have 5 projects that are configured with the default scheme. This has worked well for us until now. Any members of the development team can do anything, and we are happy with this lax scope for now.

We are creating a new bug tracking board for our client facing support team.

Now I need to:

• allow developers and support to have free rein on the new project
• block support from even seeing the existing projects, if this is possible. Support should not have any access / rights on the existing products

We sync our users and groups from 365, and I know that I can safely use the existing group names.

Can someone please help me with the fastest way to achieve this? I've watched the Plural Sight training on permissions and security schemes & tried Google, but I am still none the wiser.

Els Bassant

Hi Kamuzz,

You can either create a new permission scheme, or adjust the current permissions scheme to give permissions based on project roles instead of all logged in users (which is what the default scheme has, if I remember correctly).

The advantage of the second option is that you can continue to use the same permissions scheme for all projects, while still maintaining control over who has access to which projects. Whether or not this scales well in your case depends on how your user groups are organised.

For all of our projects all permissions are role based. So all projects have "user", "developer", "QA" roles (amongst others) but which users or user groups are added to a role differs per project.