Permission Sets

Permission Sets

Combine Multiple Roles into one single attachable entity, which would be attached to a User account, to provide total cumulative permissions of the Permission Set.


Description:

A single user can be, and often is, assigned to multiple roles. Users inherit the most-permissive setting of all roles that are assigned to them.

You could build all permissions into a single role. For low-complexity environments, this works well.

You could build discreet roles for sets of permissions, and assign multiple roles to a user account.
This approach does introduce complexity; but it allows for easy scalability and identification of total permissions, and compartmentalizes changes to the roles.

image


Example/Use case(s): See visual examples below

re: implementation,

I’m toadally :frog: open to whatever the UX people think best; but for flow parity with current UX I’m thinking:

  1. Add a button to create the new entity, either in the Admin menu as a second-level menu, or in the Admin > Roles menu.

  2. Specify which Roles to add.

  3. Add the Permission Set to a User.

image

image