ERPNext is a multi-user system with no licence limit on users. It supports role-based permissions, record-level restrictions by company, branch, or warehouse, multi-level approval workflows with conditions, automatic task assignment, notifications, and a full audit trail of every change. Organisations from 5 to several thousand employees run cross-department processes such as purchase requisition to payment entirely within it.
Key facts
- User limit: none in the licence. Capacity is a function of hosting.
- Permission layers: role permissions, user permissions, permission levels on fields, and sharing on individual documents.
- Workflow engine: configurable states, transitions, approver roles, and conditions, without coding.
- Audit trail: every document stores a version history showing user, timestamp, and field-level changes.
What is a multi-employee workflow?
It is any process where a transaction passes between people with different responsibilities. Example: a storekeeper raises a Material Request, the purchase executive converts it to a Purchase Order, the purchase head approves it, the CFO approves if it exceeds INR 5 lakh, stores receive the goods, quality inspects them, accounts book the invoice, and treasury releases payment.
For this to work in an ERP, five capabilities are needed: identity, access control, routing, visibility, and traceability. ERPNext provides all five.
How do roles and permissions work in ERPNext?
| Layer | What it controls | Example |
| Role | A named set of rights assigned to users | Accounts User, Purchase Manager, Stock User |
| Role permissions | What a role can do per doctype: read, write, create, submit, cancel, amend, delete, print, email, export, report | Purchase User can create POs but cannot submit them |
| User permissions | Restrict a user to specific records | Chennai branch users see only Chennai warehouse and cost centre |
| Permission levels | Field-level security within a document | Only HR Manager sees salary fields on the employee record |
| “If owner” rule | Users see only documents they created | Sales executives see only their own quotations |
| Document sharing | One-off access to a single record | Share one project with an external auditor |
| Role profiles and module profiles | Bundles for fast onboarding | “Stores Executive” profile assigns all relevant roles at once |
ERPNext ships with over 40 standard roles, and custom roles can be created in minutes.
How do approval workflows work?
The Workflow feature lets an administrator define, for any doctype:
- States: for example Draft, Pending Purchase Head, Pending CFO, Approved, Rejected
- Transitions: which action moves a document from one state to another
- Allowed roles: who may perform each action
- Conditions: Python-style expressions such as doc.grand_total > 500000
- Document status mapping: which states are draft, submitted, or cancelled
- Email alerts: automatic notification to the next approver, with approve and reject links
Example: purchase order approval matrix
| PO value | Approval path |
| Up to INR 50,000 | Purchase Executive, then Purchase Head |
| INR 50,001 to 5,00,000 | Purchase Executive, Purchase Head, then Finance Controller |
| Above INR 5,00,000 | Purchase Executive, Purchase Head, Finance Controller, then Managing Director |
This is built entirely through configuration. Users with the approver role see pending items in their Workflow Action list and receive email alerts.
Authorization Rules provide an alternative for value-based limits, for example restricting discounts above 10 percent to the Sales Manager role, or applying limits per customer or item group.
How is work assigned and tracked across employees?
| Feature | Purpose |
| Assign To | Assign any document to a colleague with a due date and priority; creates a ToDo |
| Assignment Rules | Auto-assign leads, issues, or tasks by round robin, load balancing, or field value |
| Notifications | Email, system, or SMS alerts triggered by events, dates, or value changes |
| Comments and mentions | Discuss within the document using @mentions, keeping context with the record |
| Timeline | Chronological log of every action, email, and comment on the document |
| Document follow | Subscribe to updates on specific records |
| Kanban and calendar views | Visual tracking of tasks, opportunities, and work orders |
| Energy Points | Optional gamification rewarding timely actions |
| Auto Repeat | Scheduled creation of recurring documents |
| Email integration | Incoming and outgoing email linked to documents |
How many concurrent users can ERPNext handle?
There is no software cap. Practical capacity depends on infrastructure and usage pattern.
| Concurrent users | Typical infrastructure |
| Up to 25 | Single server, 2 to 4 vCPU, 8 GB RAM |
| 25 to 100 | Single larger server or split application and database, 8 vCPU, 16 to 32 GB RAM |
| 100 to 500 | Separate database server, multiple web workers, dedicated background workers |
| 500+ | Load-balanced application servers, database replicas, performance engineering |
Concurrency conflicts are handled safely. If two users edit the same draft, ERPNext warns the second user that the document has been modified and prevents silent overwrites.
Does ERPNext support segregation of duties?
Yes, and this is where a finance-led implementation adds the most value.
| Process | Incompatible duties to separate | ERPNext control |
| Procure to pay | Supplier creation, PO approval, goods receipt, invoice booking, payment | Separate roles per step; workflow on Supplier master and PO; three-way match of PO, receipt, and invoice |
| Order to cash | Customer creation and credit limit, pricing, invoicing, receipt, credit notes | Role restrictions; credit limit check; workflow on credit notes and price lists |
| Inventory | Custody, recording, and reconciliation | Stock User vs Stock Manager; approval workflow on Stock Reconciliation and write-offs |
| Payroll | Employee master, salary structure, payroll processing, payment | HR User vs HR Manager vs Accounts; field-level permission on salary |
| General ledger | Journal creation vs approval | Workflow on Journal Entry; Accounts Frozen Till Date; period closing |
| System administration | Configuration vs transaction processing | System Manager role limited to non-transacting users; periodic access review |
Observation from reviews of existing ERPNext sites: the most frequent control gap is excessive System Manager access. In one typical review, 9 of 22 users held it. Risk: any of those users can alter permissions, workflows, and naming series, and delete documents. Recommendation: limit to two named administrators, enable the audit trail settings, and review the role assignment report quarterly.
How does the audit trail work?
- Version history: each save records the user, time, and old and new values of changed fields
- Submitted documents are immutable: changes require Cancel and Amend, producing a linked new version such as SINV-0001-1
- Deletion controls: submitted documents cannot be deleted; deleted drafts are recorded in Deleted Documents
- Activity and access logs: logins, report exports, and print actions can be reviewed
- Audit trail setting (India): supports the MCA requirement for accounting software to maintain an edit log that cannot be disabled
What do multi-department workflows look like end to end?
Procure to pay: Material Request (stores) > Request for Quotation and Supplier Quotation (purchase) > Purchase Order with approval workflow > Purchase Receipt (stores) > Quality Inspection (QC) > Purchase Invoice (accounts) > Payment Entry with approval (treasury).
Order to cash: Lead and Opportunity (sales) > Quotation > Sales Order with credit check > Pick List and Delivery Note (warehouse) > Sales Invoice with e-invoice and e-Way Bill (accounts) > Payment Entry and reconciliation (collections).
Plan to produce: Sales Order or forecast > Production Plan (planning) > Material Requests and Work Orders > Job Cards (shop floor) > Quality Inspection > Finished goods Stock Entry > costing review (finance).
Hire to retire (Frappe HR): Job Requisition > Job Applicant > Offer > Employee onboarding > Attendance and leave with approvals > Payroll > Separation and full and final settlement.
Each handoff uses the “Create” button, which copies data forward and keeps documents linked for traceability.
Where are the limits?
- No visual drag-and-drop BPMN designer; workflows are configured in a table
- Parallel approvals, where two approvers must both sign in any order, need scripting
- Delegation of authority during leave requires manual role reassignment or a small customisation
- Escalation on approval delay needs a Notification or Server Script
- One active workflow per doctype, though conditions allow branching within it
Frequently asked questions
Is there a limit on the number of ERPNext users? No. The licence allows unlimited users. Hosting capacity is the only practical constraint.
Can different employees see different data? Yes. User permissions restrict records by company, branch, warehouse, cost centre, territory, customer, or any linked field.
Can ERPNext do maker-checker? Yes. Separate create and submit permissions, or a Workflow with an approver role, enforce maker-checker on any document.
Can approvals be done on mobile or email? Yes. Approvers can act from the mobile interface or through approval links in workflow emails.
Does ERPNext track who changed what? Yes. Every document has a version log with user, timestamp, and field-level changes.
Can workflows differ by company or branch? Yes, using conditions within the workflow that reference company, branch, department, or amount.
The bottom line
ERPNext handles multi-employee workflows well, with control features that satisfy auditors when configured deliberately. The design of the approval matrix and the role structure matters more than the tool.
Designing your delegation of authority? Finstein’s team combines ERPNext configuration with internal audit expertise to build role matrices and approval workflows that pass audit. Book a demo.
