A branch manager has no reason to see another branch orders, its till or its people. And whoever runs the network has no reason to log in branch by branch. Both at once, without building permissions by hand for each one.
A branch access is not a regular user with modules switched off: it is a different kind of user, and everything it queries goes through the list of branches it may see. No screen bypasses it, because the filter is on the server, not in the menu.
Every new branch is an afternoon deciding what it can see. And the day someone moves branches, it has to be redone.
Or less. A hand-trimmed permission is always trimmed wrong somewhere, and nobody notices until it matters.
Ten branches are ten logins. The full picture does not exist, or someone builds it in a spreadsheet.
Each location gets its access link. Whoever enters through it belongs to that branch and sees that branch. It can be revoked and regenerated when the manager changes.
Fifty branches in one file: name, address, zone. And all their links at once. A franchise goes up in a morning.
Orders, sales, drivers, till: everything that access queries is filtered by its branches on the server. Not a menu with hidden items.
The company access sees orders, sales and reports of every branch, per branch. Without entering any.
| One user per branch, permissions by hand | Delorean | |
|---|---|---|
| Adding a branch | Create user, pick permissions, test it does not see too much | Load the branch and send its link |
| Fifty branches | Fifty afternoons | One file |
| What the manager sees | Whatever someone remembered to switch off | Their branch. The filter is on the server |
| The manager changes | Permissions are redone | The link is revoked and another generated |
| A franchise | A user that sees the whole company, or nothing | Its branch, like any other |
| The network picture | Branch by branch, or a spreadsheet | The company access, per branch |
| Reports | Whatever each one exports | Times, sales and drivers per branch, in one place |
| If data leaks between branches | Nobody notices | It cannot: the visible-branch list applies to every query |
Written from each product's public documentation. They are mature tools and this page says where they are still better. No prices here: they change on their own and the page would end up lying without anyone touching it.
Both brands branches are loaded from a file and each gets its link. Managers enter and see their own.
Delivery times, sales by channel and drivers, per branch. The company stops building the spreadsheet.
Franchises come in as branches. One system for the whole network, everyone seeing their own.
Only its branch: orders, sales, drivers, tickets. Everything it queries is filtered by its branches on the server, not in the menu.
With the branch link. No user to create, no permissions to pick: the link already belongs to that branch.
Revoke the link and generate another. The old one stops working immediately.
As many as you have. From a file, at once, with all their links. The plan sets the cap, not the system.
Yes. A franchise is one more branch: it sees its own, the company sees everything.
Everything, per branch: orders, sales and reports of each one, without entering any.
Each brand has its branches. A Pizza Hut manager does not see a KFC branch, and the company sees both.
No. The visible-branch list applies to every server query. It is not a permission someone can forget to set.
No. Same system, one link. From the branch phone or computer.
Loading the branches is a morning. Each manager enters as soon as they get their link.