Custom roles

When the five built-in roles do not fit — a supervisor who may adjust stock but not prices, say — you can author your own.

Who can do this: the Administrator, and staff whose roles include creating or editing roles — within the limit that nobody can grant a permission they do not themselves hold. On plans without custom roles the built-ins still work; the app puts it as "Your plan includes the built-in roles. Upgrade to create and edit custom roles."

The role builder#

• Name and an optional description — the description is what colleagues see in the roles list, so say what the role is for.
• Scope: a global role applies across every store; a store role is held per store. The scope cannot be changed later while anyone holds the role.
• Full access — "Grants every permission in every feature, now and as new features are added." Only a global role can carry it.
• The permission picker — features down the side, individual permissions inside each, every one described in plain language. View permissions let people see; the others let them act.

Two limits the builder enforces for you:

• Store roles cap out below global powers. Business-wide features (the product catalogue, categories, discounts, stores themselves) can only be granted to a store role at view level — changing them from inside one store would change every store.
• You can only grant what you hold. A refused save names the permission that exceeded your own.

Managing roles over time#

• Disable a role to suspend everyone holding it at once — the confirmation counts them: "{n} staff members will lose this access immediately. Re-enabling the role restores it."
• Delete is only possible once nobody holds the role.
• Editing an in-use role changes what its holders can do from that moment — there is no need to re-assign anything.

Related pages#

Roles & permissions · Permissions reference · Comparing plans