The counter boy can see purchase cost, and anyone can edit a printed bill.
Roles and permissions decide who sees what and who may change it. A salesman bills without ever seeing cost, a branch manager sees his own branch and no other, and nobody edits a bill after the month is closed. Each person signs in as himself, so a password on a slip under the keyboard stops being the way in.
One login, one password, and everybody uses it. It is written on a slip taped under the monitor. The temporary hand who left in June still knows it, and when a rate is changed on a Saturday, nobody can say whose hand was on the keyboard.
Each person gets a login of his own and a role that matches the job he does. The role decides which screens open, which figures appear, and whether he may approve, edit or only look. Change the role once, and everyone who holds it changes with it.
What roles and permissions does.
One login per person
His name on every entry he makes. Shared logins are what make a dispute impossible to settle.
Roles that match real jobs
Counter staff, storekeeper, service advisor, branch manager, accountant. Built from how your business is actually staffed.
Figures that stay hidden
Cost, margin, wastage, salaries. A salesman can bill a piece without ever seeing what it cost you.
Only his branch, only his territory
A manager sees his own centre and his own team. Only the owner sees every branch.
What may be changed later
Editing a bill after printing, deleting a receipt, changing a rate. Each is a right granted to a few, not to everyone.
The day somebody leaves
One switch turns the login off. His entries stay, with his name on them, which is exactly as it should be.
The people who open this every day.
Owner
Decides who may see money. It is the one setting most owners want to make themselves.
Branch manager
Works inside his own branch and requests anything beyond it.
Office admin
Adds a new joiner to a role on his first morning, and closes it on his last.
It is one part of a system, not an island.
A module earns its place by what it passes to the next one. These are the connections we set up most often.
- Audit trail
- Multi-branch consolidation
- Workflow and approvals
- Payroll
- Point of sale billing
Products that include it.
How we would put it in.
Questions owners ask about roles and permissions.
Which of your products already separate this?
Jewellery Retail Management Software lets a salesperson bill without seeing cost, wastage or the karigar account. Our grocery product keeps counter staff out of prices and profit unless you allow it, and the dealer product limits commission and payment details to the people who should see them.
We are five people and we trust each other. Is this needed?
Trust is not the question; memory is. Start with two roles, owner and staff, and add a third only when a real need appears. Ten roles in a five-person firm gets worked around by the second week.
Can we still keep one common login for the counter?
You can, and we advise against it. A common login makes every correction anonymous, which is usually discovered during a cash difference. Even two logins for two shifts is better than one for everybody.
What about two-step login?
It can be turned on for the roles that matter, usually the owner and accounts. For a counter machine used by three people through the day it tends to be more nuisance than protection.
Businesses that ask for this.
Modules that work with it.
Tell us how you handle roles and permissions today.
A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.
- No obligation
- We reply the same working day
- Your details stay private