How should I set up user roles and approvals in an ERP?

Set up ERP user roles and approval rules for a small D2C team: who can buy, sell, adjust stock and see costs, without slowing daily work.

Anadoris Digital · · 4 min read

Engraved key on a branch
Photo: Katy Belcher / Unsplash (CC0)

Small teams often start an ERP with everyone as an administrator. It feels simpler. It also means anyone can change prices, delete records, adjust stock without a reason or see sensitive information such as costs and salaries. When something goes wrong, nobody can tell who changed what.

Good role design protects the business without slowing it down. The aim is that each person can do their job fully, and only their job.

Start from jobs, not people

  • Warehouse: receive goods, pick, pack, dispatch, process returns, record counts.
  • Purchasing: create purchase orders, manage vendors, track deliveries.
  • Sales and customer support: view orders, create B2B orders, handle customer queries.
  • Accounts: invoices, credit notes, payments, reconciliation and reports.
  • Founder or management: approvals, all reports, cost and margin data.
  • System owner: user management and configuration, ideally a small number of people.

Assign people to roles. One person can hold several roles in a small team, but defining roles separately makes it easy to hand work to new hires later.

Protect sensitive data

Not everyone needs to see costs, margins, supplier rates or customer contact details. Restrict cost fields to purchasing, accounts and management. Limit bulk export of customer data to a few people, both for privacy and to reduce the risk of data leaving the business. Keep payroll and HR data outside general ERP roles entirely.

Where approvals add value

  • Purchase orders above a set value or to new vendors.
  • Changes to selling prices, discounts beyond a limit and new price lists.
  • Stock adjustments and write-offs above a set quantity or value.
  • Credit notes and refunds above a set amount.
  • New SKUs and changes to tax fields such as HSN code and GST rate.
  • Vendor bank detail changes, which are a common target for fraud.

Keep approval chains short. One approver is enough for most small brands. Set a backup approver for when the main approver is unavailable, so work does not stop.

Keep approvals fast

Approvals fail when they are slow. If the founder approves on a phone in a minute, controls work. If approvals sit in an email queue for days, staff find ways around them. Choose an ERP that supports mobile approvals or notifications, and review pending approvals in your daily routine.

Roles and approvals checklist

  • No shared logins: every person has their own user.
  • Roles defined by job, with only the permissions each job needs.
  • Cost and margin data restricted.
  • Bulk export restricted.
  • Approvals set for high-risk actions only.
  • Backup approvers configured.
  • Audit log switched on and reviewed periodically.
  • Leavers’ access removed on their last day.

Reviewing access over time

Roles drift. People change jobs, temporary access becomes permanent and former staff remain active. Review users and roles every quarter. Remove access that is no longer needed and check that approval limits still fit the size of the business.

Use the audit log during reviews. It shows who changed key records such as prices, vendor details and stock, and it often reveals process gaps worth fixing.

Shared logins defeat every control on this page. Even in a very small team, give each person their own user so actions can be traced.

Separating duties where it matters

Separation of duties means the same person should not carry out every step of a sensitive process alone. In a small team you cannot separate everything, but a few splits are worth making. The person who creates a vendor or changes vendor bank details should not be the same person who releases payments. The person who records stock write-offs should not be the only one who approves them.

Where the team is too small to split duties, use review instead. The founder or accountant can look at a weekly list of vendor changes, write-offs and credit notes. A quick review catches errors and discourages misuse without adding daily approvals.

Roles for external users

Some ERPs let you give limited access to outsiders: your CA, a 3PL, a contract manufacturer or a freelance bookkeeper. Create specific roles for them with read-only access where possible, limited to the data they need. Review these users with the same care as internal staff, and remove access when the relationship ends.

Write the role design down in a simple table: role, who holds it, what it can do and what it can see. Keep the table with your ERP documentation and update it when roles change. It makes onboarding faster and gives auditors or investors a clear answer when they ask how access is controlled.

Where to start

  • List each job in the business and what it needs to do in the ERP.
  • Create roles from that list and assign people.
  • Restrict cost data and bulk exports.
  • Add approvals for the five or six highest-risk actions.
  • Schedule a quarterly access review.

Anadoris Digital can design role and approval setups that match how your team actually works, so controls stay in place without slowing dispatch.

Related service: ERP Solutions · More on this topic: ERP Solutions articles

Common questions

Should warehouse staff see product costs?

Usually not. Warehouse roles need quantities, locations, batches and order details, not purchase rates or margins. Restricting costs protects supplier terms and pricing information, and keeps the warehouse screens simpler and faster to use.

Who should be the ERP administrator in a small brand?

One or two trusted people who understand the system, often the operations head and a backup. Administrators can change configuration and access, so avoid giving this role to everyone. The founder should be able to see the audit log.

Do approvals slow down a small team?

They can if overused. Limit approvals to costly or risky actions, set sensible thresholds, enable mobile approvals and name a backup approver. Routine work, such as repeat purchase orders at agreed rates, should not need approval.

How do I handle access when someone leaves?

Disable their user on their last working day, reassign any open tasks or approvals and review whether they had access to shared systems or exports. Keep the user record disabled rather than deleted so the audit trail stays intact.

Your next chapter

Let’s build what comes next.

A new website. A better system. A simpler way to work. Tell us where you want to begin.

Discuss your project