Data-access patterns by record type
A comparison of important record-scope behaviours.
| Record pattern | Important scope boundary |
|---|---|
| Platform configuration | L0 System scope may operate across Companies; tenant users remain inside their Company. |
| Organization-scoped setup | Company boundary; Branch scope may not apply unless the entity carries a Branch relationship. |
| Customer and related records | Customer scope plus the Customer's Branch/Agent/ownership relationships and the specific child permission. |
| Accounts and Facilities | Owning Customer and Branch, plus Account/Facility-specific scope and permission. |
| Transactions | Header booking Branch. Line Account Branches do not replace that boundary. |
| Forward-Dated Transactions | Header transaction/booking Branch, matching the immediate Transaction model. |
| Standing Orders | Header transaction/booking Branch, matching the immediate Transaction model. |
| Workflow Applications | Application/Customer scope plus assignment and current workflow state. |
| Self-scoped records | Acting user's ownership/creation relationship as implemented for the entity. |
The four Role scope levels are System, Organization, Branch, and Self. Branch scope uses the primary Branch plus configured Accessible Branches; with no additional Branches it falls back to the primary Branch.
Scope can be enforced in list queries, detail lookup, selectors, and the final mutation. A record absent from a list is not proof that it does not exist.