← The journalPLATFORM / ACCESS

Roles and permissions that match how you work

How to design ERP access around jobs, records and approval limits, so people see what they need and nothing they should not.

Glass facade and people with directional camera-motion blur.PLATFORM / SUNDIAL
Photography: Vincent Tint / Unsplash ↗ · Sundial motion treatment
THE PRACTICAL TAKEAWAY

Build roles from jobs, restrict records by company, warehouse or territory, put limits on approvals, and review access every quarter.

Start from jobs, not from people

The fastest way to make a mess of permissions is to configure them person by person. Each new hire gets a copy of someone else's access with a few changes, and within a year nobody can say why a given person can see payroll or cancel invoices.

Start instead with a short list of jobs: accounts payable, accounts receivable, purchase, sales, warehouse, production, quality, support, and management. For each job, write down what they create, what they only read, what they approve and what they must never touch. Turn each job into a role. A person then gets one or more roles, and their access is the sum of those roles.

Keep the number of roles small. Ten well-understood roles beat forty slightly different ones.

Name roles after the job, not the person or the department head who asked for them. "Accounts Payable" will still make sense in three years; a role named after one person will not. Write a one-line description for each role saying what it is for, and keep that list where team leads can see it. When someone asks for extra access, the first question becomes which existing role fits, not what to bolt onto their account.

Restrict records, not just screens

Role permissions decide which types of document someone can work with. That is usually not enough. A warehouse lead in Newark should see stock entries for the Newark warehouse, not every warehouse. A sales manager for the Midwest region should see Midwest customers, not the whole book. In a group with several companies, an accountant may work for one company only.

The ERPNext engine underneath Sundial handles this with user permissions: you restrict a user to particular values of a linked record, such as a company, warehouse, territory or cost center, and every list, report and link field then respects that restriction. Set these up from the start. Adding them later means finding everything people have already seen.

Fields that only some people should see

Sometimes the document is fine to share but a few fields are not. Salespeople may need the item and price on an order but not the cost and margin. Warehouse staff need quantities but not values. Field-level permission levels let you group sensitive fields together and grant read or write access to that group separately from the rest of the document.

Be deliberate. Hide fields only where there is a real reason. Over-hiding forces people to ask colleagues for information they legitimately need, which wastes time and spreads data through messages instead.

Approval limits and separation of duties

Approvals work best when they follow amounts and risk rather than titles. A purchase order up to a set value might need the purchase manager; above it, the finance head; above a higher figure, a director. Discounts beyond the price list's normal range need someone other than the salesperson who offered them.

Separation of duties matters most in money flows. The person who creates a supplier should not be the person who approves payments to that supplier. The person who records a payment should not be the only person who reconciles the bank. In small teams this is harder, but even a second reviewer on high-value payments catches most problems. Workflows in the engine let you define these states and who may move a document between them.

Review access every quarter

Permissions drift. People change jobs, cover for colleagues on leave and keep the extra access afterwards. Contractors finish their work and their accounts stay active. Put a quarterly review in the calendar: export the list of users and their roles, have each team lead confirm their people, and remove anything that cannot be explained.

Also review who holds the system manager role. It should be very few people, and their actions should be recorded like everyone else's.

How this fits with AI agents

As Sundial builds AI agents into the product, we are designing them to work inside the same permission model as people: an agent acting for a user can see and do only what that user could, and the actions it drafts wait for a person to approve. Getting roles right now means that work will sit on a solid foundation later.