1. Home
  2. Blog
  3. Role-based access
ERP basics

Role-based access in ERP: control who can see and change what

In most small businesses, everyone who uses the computer can do everything. That is how wrong discounts, deleted bills and missing stock happen, usually by mistake, sometimes not. Role-based access fixes this without slowing anyone down.

  • Published
  • Updated
  • 3 min read
  • Milaan ERP team

Key points

  • Role-based access gives each person only the screens and actions they need.
  • Restrict the risky actions: discounts, rate changes, deletions and back-dated entries.
  • Use approval limits instead of blanket bans.
  • Combine roles with an audit trail, so every change is recorded.
  • Set it up on day one; changing habits later is harder.

What role-based access means

Instead of giving rights to each person one by one, you create roles, such as cashier, store keeper or accountant, and decide what each role can see and do. Then you assign people to roles. When someone joins or changes job, you just change their role.

Typical roles in a small business

RoleCan doUsually cannot do
Cashier / counterMake bills, take payments, close own shiftChange rates, give big discounts, delete bills, see profit
Store / godownReceive goods, issue stock, transfers, stock countsSee sales values or customer balances
PurchasePurchase orders and billsChange sales prices
SalesmanBook orders, see customer balance and stockMake final invoices, change schemes
AccountantVouchers, ledgers, GST reportsDelete old bills without approval
Owner / adminEverything, including user setup—

Actions worth restricting

  • Discounts above a set percentage or amount.
  • Rate changes on the bill.
  • Deleting or cancelling bills.
  • Back-dated entries into closed periods.
  • Viewing cost and profit for counter staff.
  • Exporting customer lists.

Approval limits, not just yes or no

Blanket bans slow the counter down. A better approach is limits: a cashier can give up to 5% discount; above that, a manager approves with a PIN or from their phone. The sale continues, and the exception is recorded.

Roles and the audit trail work together

Roles decide who can do what. The audit trail records what was actually done, by whom and when. Together they protect the business without anyone feeling watched all the time.

Setting it up

  1. List your people And what each one does every day.
  2. Create four or five roles Most small businesses need no more.
  3. Set limits Discounts, rate changes and deletions.
  4. Test with real staff Make sure nobody is blocked from normal work.
  5. Review every quarter Remove access for people who have left.
FAQ

Common questions, answered.

Short answers to the questions we hear most about this topic.

Have a question we didn’t answer?

Message us and a real person from our team will reply.

What is role-based access in ERP?

A way of giving each user only the screens and actions their job needs, by assigning them to roles such as cashier or accountant.

Which actions should be restricted?

Discounts above a limit, rate changes, deleting bills, back-dated entries and viewing cost and profit.

Will restrictions slow down billing?

Not if you use approval limits. Normal work continues; only exceptions need approval.

How many roles does a small business need?

Usually four or five: counter, store, purchase, accounts and owner.

Is an audit trail still needed if we have roles?

Yes. Roles control access; the audit trail records what actually happened.

Give every person the right access

Milaan ERP lets you set roles, limits and approvals. Try it free for 7 days.