Multiple Permission Sets per User

What it is

Admins will be able to assign multiple permission sets to a single user, with the most permissive combination of permissions taking precedence. Today's permission system requires admins to either build custom sets for every variation or manage individual permissions one user at a time, which gets messy fast when someone wears two hats. This is in public beta for Content, Marketing, Operations, Sales, and Service Hub Enterprise.

Why it matters

The cleanest example is the person who does both sales and marketing, or the team lead who needs slightly elevated access on top of their function-specific permissions. Today, admins handle this by creating one-off custom sets that nobody else can use, or by manually adjusting individual permissions and hoping they remember to revoke them later. Stacking permission sets is how this should have worked from the start. For larger Enterprise portals, this will quietly remove a category of admin overhead.