A record is outside your data-access scope

Permission answers “may this user perform this action?” Data-access scope answers “on which records?” A user may have Read or Update and still receive Not Found, Forbidden, an empty selector, or an empty list for an out-of-scope record.

Diagnose scope

1. Confirm the record belongs to the selected Company.
2. Check the Role's scope: System, Organization, Branch, or Self.
3. For Branch scope, confirm the user's primary Branch and Accessible Branches. An empty additional list falls back to the primary Branch; it does not mean every Branch.
4. Confirm the record's owning Customer, Branch, creator, assignee, Agent, or other entity-specific scope relationship.
5. Confirm the user is allowed to see every referenced Customer or Account needed by the task.

Transactions, Forward-Dated Transactions, and Standing Orders use the header booking/transaction Branch as their authorization scope boundary; lines may reference Accounts in other Branches. Other entities can scope by their own Branch, Customer, assignment, or ownership. Do not apply the Transaction rule to every entity family.

Ask an administrator to correct the data or scope only after identifying which boundary failed. Avoid moving a record or granting Organization scope merely to work around a selector problem.