consolidate permission schemes

[Anuradha Yadav]

Hi Team,

We have 68 permission scheme and we want to identify and consolidate which are similar.

What is best way or practice.

Regards,

Anu

[Anuradha Yadav · Accepted solution]

@Mark Segall Thanks for your answer but we have different/unique ones. or do we need to compare and check the one which has all permissions in it and come to conclusion to ideal one.

[Mark Segall]

In my experience, many admins just go with whatever permission scheme is created when the project is created and haven't given a second thought to what the permissions are doing unless they come across an issue with it and even then, they probably aren't following best practices (e.g. adding an individual to a specific permission rather than role or group). 

This is why I just bring key parties into a room and hash it out.  You set a lofty goal of one permission scheme to rule them all with realistic expectation that it may end up being more than that.  Essentially you want people to justify why a shared permission scheme won't work for them. For example... challenging them on why they can't use the same role strategy as other projects.

[Mark Segall · Accepted solution]

Hi @Anuradha Yadav - I've found that rather than trying to reverse engineer 68 permission schemes, that it's best to bring a team of top Project Admins together and hash out an ideal permission scheme (or set of permission schemes) that will serve as the benchmark going forward. Then simply change all of the projects to one of the final schemes and delete the old ones.