Access that matches responsibility
Rather than an all-or-nothing access model, Muhasib's permission engine lets each role's visibility be scoped precisely — a branch manager sees their own branch's bookings, customers, and financials in full, without visibility into other branches they have no operational reason to see.
How this is configured in practice
Role templates (branch staff, branch manager, general manager, and others) come pre-configured with sensible default scopes, which an agency can adjust — so setting up appropriate access for a new branch doesn't require designing a permission structure from scratch.
What this prevents
This structure prevents both accidental and deliberate overreach — a staff member at one branch simply can't pull up another branch's customer list or pricing, because the system itself doesn't expose it, not because of a policy staff are trusted to follow.
Why this matters for growing agencies
As an agency adds branches, this structure scales without requiring a manual permission audit every time — each new branch inherits the same role-based model that's already proven to work.