Running the business

Staff & permissions

Roles, capabilities, per-person exceptions, and who can do what.

Permissions decide what each person can see and do. WeSelling uses capabilities rather than job titles, which is a small distinction with a large consequence.

Capabilities, not job titles

The app never asks "is this person a manager". It asks "can this person approve a refund". A role is a bundle of capabilities, and you can make as many roles as your business actually has.

Note This matters the first time you need a supervisor who can approve refunds but not see payroll. With job titles that is a new title and a code change. With capabilities it is two clicks.

How access is worked out

Three things combine, in this order:

The roles they hold
Everything from every role they have, added together.
Their personal grants
Extra capabilities given to this one person, on top of their roles.
Their personal denies
Capabilities taken away from this one person. A deny always wins.

The per-person layer exists because real businesses have exceptions. One cashier you trust with voids; one manager you would rather not have payroll access during a dispute. Without exceptions you end up making a role for one person, and then another, until roles mean nothing.

The owner

The owner has every capability, always. The owner cannot be stripped of a capability and cannot be the target of a deny.

This is on purpose A business must never be able to lock itself out of its own account. Any design that allows it turns a mistake into a support ticket nobody can resolve.

Adding someone

Open Staff
Go there
Add them
Name, email, branch, department.
Give them roles
Start with a role preset. Adjust once you see what they actually need.
Add exceptions if needed
The owner can grant or deny individual capabilities per person.

Roles

Settings → Roles shows a matrix of every capability grouped by area. Presets cover the common shapes — cashier, stock keeper, supervisor, accountant — and you can change any of them or start fresh.

Tip Grant the least that lets someone do their job, then add when they hit a wall. Starting broad and trimming later never happens.

Branches and departments

Everyone belongs to a branch, and stock, sales and attendance follow that. Departments group people within a branch — useful for routing a customer's staff call to the right counter.

What a role cannot do

Some pages are owner-only regardless of capabilities. Those are the ones where granting access would defeat the point of having an owner at all — the billing account, the permission matrix itself, the platform-level switches.

Seeing what happened

Settings → Activity records who did what. Sales, stock movements, permission changes and refunds all carry the name of the person who made them.

Every page in this area

Page	What it does	Needs
Staff	Your people — invite them, set what each one is allowed to do, and suspend anyone who leaves.	Staff · read
Staff intelligence	Who sold the most this month, who turns up on time, and who starts earliest. The people counterpart to customer intelligence.	Staff · read
Attendance	Who clocked in, when, and from where. This is what feeds hours and lateness into payroll.	Attendance · read
Payroll	Work out and approve what each person is paid, with attendance, queries, bonuses and unresolved shortages already accounted for.	Payroll · read