A multi-branch agency needs three things a generic CRM rarely gives it: an agency-over-branch structure, role-based access so people only see and do what their role allows, and clean seat management for adding and removing staff. TenantSync CRM is built for exactly this — an agency → branch → member hierarchy with three roles (Agency Admin, Branch Manager, Agent), branch scoping enforced by the platform so each branch sees only its own portfolio while principals see everything, and team seats that make onboarding or offboarding a one-step, controlled action — all on top of RTB, PSRA and Open Banking. Free 14-day trial, no card required.
Growth is the moment most agency software quietly stops fitting. A single-office setup where everyone can see everything is fine at ten units and three people. Add a second branch, a few negotiators and an accounts hire, and "everyone sees everything" becomes a data-governance problem, a reporting problem and a trust problem all at once.
The fix isn't more discipline — it's structure. When the software mirrors how a multi-branch agency actually works, the awkward questions ("should this negotiator see the other branch's landlords?", "how do we cut off access when someone leaves?") answer themselves. This guide lays out that structure and how TenantSync CRM implements it.
This is where "we'll just use spreadsheets" ends
A shared spreadsheet or a generic CRM can't scope data by branch or enforce who does what. The day you can't safely give a new negotiator access without exposing the whole book is the day the agency has outgrown its tools — and multi-branch structure is what it has outgrown them into.
Why multi-branch breaks generic tools
Generic CRMs and spreadsheets fail a growing agency in the same few places, every time:
- No real hierarchy. There's no concept of an agency over branches, so every property and client sits in one flat pool with no clean way to say "this belongs to the Cork office."
- All-or-nothing access. Either someone can see everything or they're locked out — there's no middle setting that says "this branch, this role."
- Reporting is a manual export. Per-branch performance means filtering and re-formatting by hand, and an agency-wide roll-up means stitching exports together.
- Offboarding is a scramble. When someone leaves, revoking access is a manual hunt across tools — and access that lingers is a data-protection and PSRA risk.
None of these is a discipline failure; they're structural gaps. A tool that doesn't model branches can't scope by branch, no matter how careful the team is.
The agency / branch / member model
The whole thing rests on a simple three-layer structure. Get this right and roles, scoping and reporting all fall out of it naturally.
| Layer | What it is |
|---|---|
| Agency | The top level — your firm. Principals operate here and see across every branch. |
| Branch | An office or location. Every property, tenancy and landlord client sits under a specific branch. |
| Member | A team member, given a role and (for branch staff) attached to their branch, so access follows responsibility. |
Because every record lives under a branch, and every person has a role and a scope, the system always knows the answer to "can this person see this record?" — without anyone maintaining a spreadsheet of who's allowed to do what.
Structure your agency and branches in minutes
TenantSync CRM gives you an agency-over-branch structure with role-based access out of the box — each branch scoped to its own portfolio, principals with an agency-wide view, and clean seat management as you grow.
No credit card required · Live in under 10 minutes
Roles: who can see and do what
On top of the structure sit roles. Rather than a long list of individual permissions to maintain, each member gets one of three organisation roles, and access follows from it. That keeps the model simple to reason about — and simple is what survives contact with a busy agency.
| Role | Typical person | What they see & do |
|---|---|---|
| Agency Admin | Principal / director | An agency-wide view across every branch, with full control — structure, people, reporting and settings. |
| Branch Manager | Office / branch lead | Runs their branch and sees its full portfolio — properties, tenancies, clients and the team in that branch. |
| Agent | Negotiator / lettings agent | Works within a branch on its properties, tenancies and enquiries — without visibility of other branches. |
Role, not a pile of toggles
The value of role-based access is that responsibility and access stay in sync by design. You don't hand-configure twenty switches per person and hope they're right — you pick the role, and the scope follows. New starters are safe by default, because "Agent in the Galway branch" already means exactly what it should.
Branch scoping, enforced — not just hidden
Here's the part that separates real multi-branch software from a CRM with a few view filters: scope is enforced by the platform, not inferred in the browser. Every member has a scope — individual, branch, agency or platform — and the system applies it server-side when it decides what data to return.
The practical difference is a security one. When branch separation is just a UI filter, the data is still sent to the browser and merely hidden — the wrong person is one export or one clever URL away from seeing it. When the scope is applied on the server, a branch-scoped negotiator's device is simply never given another branch's data in the first place. For an agency handling landlords' and tenants' personal and financial information, that's the difference between a display preference and a genuine boundary.
"Can the Cork negotiator see the Dublin landlords?" shouldn't depend on someone remembering to tick a box. With enforced scoping, the answer is no by construction — and stays no.
Team seats: onboarding & offboarding safely
Growth means people joining and leaving, and both need to be controlled, one-step actions rather than risky manual jobs. TenantSync CRM handles this with team seats:
- Invite by email. Add a new team member into an available seat with their name and email; they show as pending until they first log in, then become active.
- Seats that scale. Each plan bundles a number of seats, and you can add extra seats as a per-seat add-on (€15/month each) when the team grows — so capacity tracks headcount. (See current pricing.)
- Clean offboarding. When someone leaves, revoking their access is a single action — so access never lingers with a former employee, which matters for both GDPR and PSRA governance.
Get the agency roles & permissions planning template
Start a free 14-day trial and set up your agency, branches, roles and seats in minutes — the planning template below, put straight to work in TenantSync CRM.
Per-branch vs agency-wide reporting
Once the structure and scoping are in place, reporting stops being a manual export and becomes a matter of which level you're looking at. Because every record is attached to a branch, the same data answers two different questions:
- Per branch. A Branch Manager sees their office's own performance — its portfolio, tenancies, enquiries and client activity — without noise from other branches.
- Agency-wide. Principals get the roll-up across every branch from the same single source of truth, so comparing offices or reporting to the firm is a view, not a spreadsheet-merge exercise.
This is also where multi-branch structure pays off for PSRA governance. Access control plus an audit trail means the agency can show who did what and who could see what — the kind of data governance a regulated property services provider is expected to maintain. It's the same discipline that underpins per-client money handling and reporting and the approval controls on landlord disbursements.
The mistakes multi-branch agencies make
The failure modes are consistent — and every one is a structure problem, not a people problem.
| Mistake | Why it costs you |
|---|---|
| One flat pool of data | No agency-over-branch structure, so nothing is truly separable by office and everyone drifts toward seeing everything. |
| All-or-nothing access | Without roles, you either over-expose data or block people from doing their job — and usually over-expose. |
| Scoping that's only a UI filter | Data hidden in the interface is still sent to the device — a display preference, not a security boundary. |
| Manual onboarding/offboarding | Access that lingers after someone leaves is a GDPR and PSRA risk; slow onboarding stalls new hires. |
| Reporting stitched by hand | Per-branch and agency-wide numbers reconstructed from exports are slow and error-prone. |
Notice the pattern: not one of these is fixed by trying harder. They're fixed by software that models an agency, its branches and its people — so the right access is the default, not a thing someone has to remember to configure.
How TenantSync CRM runs a multi-branch agency
TenantSync CRM is built around the agency/branch/member model, so multi-branch operation isn't a bolt-on — it's the shape of the product:
- Agency & branch structure. Create the agency and a branch per office; every property, tenancy and client is attached to a branch, so the whole book is cleanly separable.
- Three clear roles. Agency Admin, Branch Manager and Agent map to how an agency actually staffs — principals, office leads and negotiators — so access matches responsibility without per-person fiddling.
- Enforced scoping. A member's scope (individual, branch, agency) is applied by the platform, so a branch negotiator is never served another branch's data — separation by construction, not by filter.
- Team seats. Invite staff by email into bundled or added seats, watch pending become active, and revoke in one step on exit — controlled onboarding and offboarding.
- Per-branch & agency-wide views. The same single source of truth reports at branch level for managers and agency level for principals, with the audit trail PSRA governance expects.
And it all sits on top of the three pillars every Irish agency has to get right anyway — RTB compliance across the whole book, PSRA and client-money compliance, and Open Banking rent automation — so multi-branch structure and compliance aren't two systems, they're one. If you're moving from Letman or spreadsheets, our guide to migrating a letting agency off Letman and spreadsheets covers the switch.
How to get started
- Start your free 14-day trial — no credit card required.
- Create your agency and branches — one branch per office.
- Invite your team into seats and assign each a role and branch.
- Report per branch and agency-wide from one source of truth — and book a demo if you'd like it walked through.
Frequently asked questions
What is multi-branch letting agency software?
It lets an agency with more than one office run all its branches from one system while keeping each branch's data and access separate — an agency-over-branch structure, role-based access, per-branch and agency-wide reporting, and controlled ways to add or remove staff. TenantSync CRM does this on top of RTB compliance, PSRA compliance and Open Banking rent automation.
How do roles and permissions work in a letting agency system?
Each team member gets a role that determines what they can see and do. TenantSync CRM has three organisation roles: Agency Admin (principals, agency-wide view and full control), Branch Manager (runs a branch and sees its portfolio), and Agent (a negotiator within a branch). Access follows the role and the branch a member is scoped to, so a negotiator in one branch doesn't see another branch's data.
Can each branch see only its own portfolio?
Yes. A member's scope — individual, branch, agency or platform — is enforced by the platform, not just hidden in the interface. A branch-scoped member sees only their branch's properties, tenancies and clients, while Agency Admins keep an agency-wide view. Because scope is applied server-side, branch separation is a security boundary, not a display preference.
How does adding or removing a team member work?
You invite a team member into an available seat by email; they're pending until they first log in, then active. Plans bundle seats and you can add extra seats as a per-seat add-on. When someone leaves, revoking access is a single, controlled action — so access never lingers with a former employee, which matters for GDPR and PSRA governance.
Why don't generic CRMs work for a multi-branch Irish agency?
They weren't built around a lettings agency's structure or Ireland's rules. They rarely model an agency-over-branch hierarchy with proper scoping, so negotiators can see other branches' data and per-branch reporting is a manual export — and they don't understand RTB, the national rent cap or PSRA client-money obligations. TenantSync CRM combines multi-branch structure with the three compliance and rent-automation pillars in one Irish-built system.