Best Practice for putting users or groups in project roles?

[Gustav L'Estrade]

Im going through permission administration and have a question about best practice. I understand that best practice is to create project roles that map to permission schemes to be reused by multiple projects. What i do not understand is whether i should put individual users or groups into project roles. 

Is it better to put the users right into the project roles or create groups for it? A group to me seems to be like an department or similair in an organization. Is it worth creating a group for all members of a certain project?

[Nic Brough -Adaptavist- · Accepted solution]

Best practice here is to do what works best for you!

If you have a well maintained directory of people where you can rely on things like "this person moved into my team, so they have been removed from their old team groups and added to mine", then use groups in roles, adding individuals for the outlying cases where the groups let you down.

If your group maintenance is not so hot, or you don't really want to bother with them, use individuals in roles.

Most places I know of use a mix of groups and individuals, there's no real solid good or bad practice I can lead you to without knowing your user access needs.

[Gustav L'Estrade]

That makes sense! Thank you for the reply!