Loading…
Loading…
This is Sales Invoice’s standard matrix. Asha starts as an Accounts User — try cancelling a submitted invoice.
Role Permissions · Sales Invoice
| Role | read | write | create | submit | cancel | amend | delete | If Owner | |
|---|---|---|---|---|---|---|---|---|---|
| Accounts Manager | |||||||||
| Accounts User | |||||||||
| Sales User |
Asha’s roles
Role permissions
What each role may do with a DocType. A user gets everything their roles grant, added together.
If Owner
Narrows a right to documents the user created — while the list stays open to them.
User Permissions
Narrows which records: only invoices for her territories, say. Empty fields still show unless the strict setting is on.
On top of all three, the document’s status still rules: drafts can be edited and submitted, submitted ones cancelled, cancelled ones amended — and a submitted document is never deleted.
A user gets every right that any of their roles grants. If one role can read and another can write, the user can do both.
In ERPNext’s standard Sales Invoice permissions only the Accounts Manager has Cancel and Delete. Accounts User can create, submit and amend.
It limits a right to documents the user created. They still see the list, but can only open, edit or submit their own.
Record-level limits: for example only invoices whose Territory is Kerala. Invoices with no territory still show unless “Apply Strict User Permissions” is on in System Settings.
No. A submitted document must be cancelled first; cancelled and draft documents can be deleted.
We map your teams to roles, set user permissions by company, branch or territory, and test what each person can see. Talk to a consultant.
or write to info@acube.co
Kochi (Kadavanthra & Infopark) · Thiruvananthapuram · across India & overseas · In business since 2011