A branch is financial context, not only an address
A branch determines where a transaction belongs, who is responsible, which limits apply, and how settlement is reported. Give it a stable name, clear internal code, operating scope, and active or suspended state. Renaming must not erase historical identity.
Add operators
Add a user through a verified membership, then define the role and branches where it applies. Avoid shared accounts: every action should be attributable to a person, role, device, and reviewable context.
Operator lifecycle
- Invite and verify the member.
- Assign role and scope.
- Approve the device or operating point.
- Start a work session or shift when required.
- Review activity periodically.
- Suspend membership or remove access when the relationship ends.
Moving an employee between branches
Do not rewrite previous transaction history. End the old scope at a defined time and activate the new scope. Yesterday’s reports then remain attached to the branch where activity actually occurred.
Control signals
Review inactive users, broad roles, old devices, and activity outside expected hours. Connect this with Roles and permissions and Daily operations and close.