Scope should narrow automatically down the org chart — Director, Branch Manager, Team Lead, Agent — enforced structurally, not as an unwritten rule.
A single-branch team can get away with loose permissions — everyone roughly sees everything, and it's fine because everyone knows everyone. The moment a second branch opens, that same looseness turns into cross-branch data leakage, confused dashboards, and agents seeing leads that aren't theirs to work.
The Roles That Actually Map to a Real Estate Org
- Director — sees the entire organization. Bookings, commissions, reports, across every branch, one screen.
- Branch Manager — sees their branch. Pipeline, approvals and password resets for their team, nothing from other branches.
- Team Lead — sees their team. Pipeline, overdue alerts, reassignment and approvals scoped to the people reporting to them.
- Sales Agent — sees their own pipeline. Follow-ups, site visits and bookings from their own lead records, not the whole branch's.
What makes this work isn't the labels — it's that scope narrows automatically as you go down the hierarchy, without anyone having to manually configure visibility rules per person.
Why This Needs to Be Structural, Not a Convention
"Agents shouldn't look at other branches' data" is easy to say and hard to enforce if it's just an unwritten rule. A granular permission matrix — every module, every action (View, Add, Edit, Delete, Export, and specifically Reveal Mobile Number) controllable per role — turns that rule into something the system actually enforces, rather than something that depends on everyone behaving correctly.
Org Hierarchy Should Drive More Than Access
The same reporting structure that determines who can see what should also drive dashboard scoping automatically — a Director's dashboard rolls up the whole org without configuration, a Branch Manager's rolls up just their branch — and approval routing, so a discount request finds the right approver based on actual org structure, not a hardcoded name that breaks the moment someone changes roles.
A Detail Worth Getting Right Early
Retrofitting permission structure onto a business that's already grown past one branch, with data already mixed together, is much harder than setting it up correctly from the start. If you're planning to open a second branch in the next year, it's worth structuring roles and scoping before you need to, not after the first cross-branch data mix-up.