Resolving “No Permission for Territory” Error in Accounts Receivable Report
A user may have the appropriate accounting roles assigned, such as Accounts User or Accounts Manager, yet still encounter a permission error when accessing the Accounts Receivable report.
This occurs because ERPNext requires users to have at least Read permission on all linked documents referenced within a report.
QUESTION
A user has the Accounts User and Accounts Manager roles assigned but receives a “No Permission for Territory” error while opening the Accounts Receivable report. Why does this happen and how can it be resolved?
Why This Error Occurs
ERPNext’s permission framework validates access not only to the report itself but also to every linked document used within the report.
The Accounts Receivable report contains a link field that references the Territory master.
If the user does not have permission to read Territory records, ERPNext blocks access to the report and displays a permission error.
Users must have at least Read permission on all linked DocTypes referenced by a report.
Example Scenario
Consider the following configuration:
- User has the Accounts User role.
- User has the Accounts Manager role.
- User attempts to open the Accounts Receivable report.
- ERPNext displays a permission error related to the Territory DocType.
Although the user can access accounting reports, they cannot access the linked Territory records required by the report.
How to Resolve the Issue
Grant Read permission for the Territory DocType to one of the roles assigned to the user.
Step 1: Open Role Permission Manager
Navigate to:
Home > Users and Permissions > Role Permission Manager
Step 2: Select Territory
Choose Territory as the Document Type.
Step 3: Update Permissions
Locate the Accounts User or Accounts Manager role and grant:
- Read Permission
Save the changes.
Step 4: Verify Report Access
After updating permissions, ask the user to reopen the Accounts Receivable report.
The report should now load successfully without any Territory-related permission errors.
Understanding Linked Document Permissions
ERPNext follows a strict permission model where reports inherit access requirements from their linked fields.
Example:
| Report | Linked DocType | Required Permission |
|---|---|---|
| Accounts Receivable | Territory | Read |
| Sales Order | Customer | Read |
| Purchase Invoice | Supplier | Read |
If access to any linked DocType is missing, ERPNext may prevent the report from loading.
BEST PRACTICE
When troubleshooting report permission issues, review all link fields used in the report and ensure users have at least Read access to the related DocTypes.
Related Topics
- Role Permission Manager
- Role Based Permissions
- User Permissions
- Accounts Receivable Report
- Territory
- Linked Document Permissions
