Permission set groups for job functions
Key Takeaway
Assign one permission set group built around a job function instead of many separate permission sets. Use a muting permission set when one group needs less than a shared permission set gives, instead of editing or copying the shared permission set.
A permission set group bundles several permission sets into one unit built around a job function or persona, so you assign one group instead of many separate permission sets. A muting permission set can switch off specific permissions for that group only, without changing the permission sets underneath.
Building groups around job functions
Users assigned a group get the combined permissions of every permission set in it.
For example, a "Sales Staff Users" group could hold Sales Cloud Einstein, Survey Creator, and a permission set based on the Standard User profile. Users assigned this group get the combined permissions of all three, so you assign one group instead of three separate permission sets.
Build groups around the tasks people do, not their job titles.
For example, a consultant, a sales manager, and a sales service director can all share one job function, such as managing price surveys. One "Price Surveys" group can serve all three. New hires or contractors who take over that work just get the same group.