User Groups and Permission Sets: Should They Be Defined Together or Separately?
Hi all! Thoughts for the weekend. We are currently defining the future of user groups and permission sets for users in a community.
User Groups can be thought of as anything from ambassadors, nyc-members , paid-members.
Permission Sets can be thought of as a collection of permissions that allow a user to create an event, assign a badge, moderate a channel, etc.
Where we are struggling is the following: Do you all think of user groups and permissions sets as separate processes or should they be defined together?
Advantage of having them as one concept: When defining a group like ambassadors, you probably have a general idea of what permissions you want each of them to have. You also want them to be associated as a group together so that you can take common actions across the entire group. When a new ambassador comes onboard, you only need to add them in a single place rather than in 2 or more places.
Advantages of keeping them separate concepts: Granularity of permissions versus groups. If ambassadors can all be part of a group but you want to provide them all with separate capabilities, you might consider keeping the group the same but defining their roles and permissions separately.
Personally, I am leaning towards having them as one concept and allowing a user to be added to multiple groups. This would give them the superset of all permissions defined by the various groups in which they are a part of.
