Roles

A role is a named list of permissions. People get their abilities from the roles they hold, so roles are how you decide who can issue receipts, who can reprint them, who can see every customer and who can only see their own.

Open them at Settings → Administration → Roles.

How roles work

• Your organisation starts with no roles. There are no built-in roles and no templates; the first role is whatever you create. Until then, only the owner can do anything.
• The owner needs no role. The owner automatically has every permission, including ones added to the platform later. Roles only shape what other people can do.
• A person's permissions are the union of their roles. Two roles combine; nothing in one role can take away what another grants.
• A person with no roles can sign in but do nothing. They see the dashboard with no module cards and Settings with only My Settings.
• Changes take effect at the next sign-in (or when the app silently refreshes its session, roughly every 15 minutes). Someone already signed in keeps their old permissions until then.

The list

Columns: Role, Description and Permissions (a count). Empty state: "No Roles yet. Create the first one to start granting permissions."

Creating or editing a role

"Role" card

Name

Required and unique within the organisation. For example Cashier, Supervisor, Bookkeeper.

Description

Optional, for your own reference.

"Permissions" card

Permission chips grouped by what owns them: Platform first (Users, Roles, Locations, Tenant, Subscription, Audit, Configuration, Reports), then one group per licensed module using its name (Receipts, Customers, Products, Inventory). Tap a chip to grant it; the subtitle counts how many are selected. Long-press or hover a chip for the plain-language description of what it allows.

Modules your organisation does not license are not offered. If you license a module later, its permissions appear in every role editor the next time you open it, and you grant them then; nobody gets them automatically except the owner.

"Mine" permissions: all versus only my own

For each module, the View, Edit and Delete permissions (and Inventory's Adjust) come in two flavours. Customers.View reaches every customer; the chip labelled Customers.View · mine reaches only the customers that person created themselves.

• Holding the plain permission always wins: a role with both sees everything.
• The narrowing happens inside the query, so counts and lists agree with what the person is allowed to see.
• A record outside someone's scope behaves as if it does not exist ("Customer Not Found"), rather than announcing that it exists but is off limits.
• Reports need the plain permission. A person with only the "mine" flavour of a module's View is offered no report for that module, because an organisation total that silently omits everyone else would look like the whole picture.
• "Mine" means the records that person created. For inventory that is the person who switched tracking on for a record, not whoever last adjusted it.

Every key and what it allows is listed in the Permissions reference.

Deleting a role

Delete asks "Delete this role?" and explains that only roles not assigned to any user can be deleted. Remove the role from every person first (under Users), then delete it. People who held it in the past are unaffected.

Suggested starting roles

These are suggestions, not built-ins. Adjust to taste.

How this connects