Contact a manager: +998 99 723-04-44
For agencies

Who sees what: roles and database access in a real estate agency

Updated 8 min

An agency team at their desks

In a small agency everyone sees everything: a shared property spreadsheet, a shared client folder, a shared chat. While there are three agents who all trust each other, that’s convenient. But the agency grows, new people arrive, someone leaves - and one day it turns out a departing agent took half the client base with them, and a newcomer accidentally deleted a property a colleague had worked on for a month. Let’s look at how to set up roles and database access in a real estate agency to protect the shared asset without getting in the way of people’s work.

Why an agency should restrict access

The property and client database is the agency’s main asset. Years of work, advertising, calls and viewings have gone into it. When access to it isn’t restricted at all, the agency depends on the honesty and care of every employee. Most people are both honest and careful, but one resentful departure or one newcomer’s mistake is enough to lose the base.

There’s a second reason - personal data. Owners’ phone numbers and buyers’ names and requests are information about people who entrusted it to the agency. The fewer people who see it without need, the lower the risk of a leak. The third reason is disputes within the team: when you can see who registered a client first and who handled the deal, an argument about “my lead” is settled by data, not by whoever is loudest.

Roles in an agency: who sees and edits what

There shouldn’t be many roles: four or five are usually enough. What matters is that each one matches a real position and real tasks rather than being invented “just in case”.

Typical roles and their access

Scroll the table sideways

RoleWhat they seeWhat they can change
AgentWhat they seeTheir own properties and clients, the shared property base without others’ contactsWhat they can changeTheir own cards, tasks and deals
TraineeWhat they seeProperties and clients handed over by their mentorWhat they can changeOnly notes and tasks, no deleting
Team leadWhat they seeEverything for their team, the team’s overall analyticsWhat they can changeAssign and reassign clients and deals
AdministratorWhat they seeIncoming leads and the viewing scheduleWhat they can changeDistribute leads without touching deals
Director / ownerWhat they seeThe whole agency, the action log, exportsWhat they can changeSettings for roles, access and export

The scheme is approximate: in a small agency the manager and the owner are often the same person, and the administrator role may be combined with office manager.

Decide separately whether agents can see owners’ contacts on other agents’ properties. A common compromise: the property itself is visible to everyone so they can offer it to their buyers, but the owner’s phone number is visible only to the responsible agent. Then the shared base works for everyone without becoming a base for poaching clients.

Two people discussing data on a screen

Principles that save nerves

  • Least necessary access: people see what their work needs, not everything.
  • Viewing and editing are different rights: many roles can look but not edit.
  • Deleting is a rare right: an archive you can restore from beats permanent deletion.
  • Exporting the base is a separate right held by one or two people, not every agent.
  • Every client and property has a responsible person - shown on the card.

These rules aren’t about distrust. They protect the agents themselves too: if every client has a responsible agent, nobody can “intercept” someone else’s client, and there are fewer arguments about whose client it is. How to distribute leads so a client has a responsible agent from the first minute is covered in our article on lead distribution.

Think separately about access from phones. Agents work at viewings and on the move, and roles must apply on a phone just as they do on a computer. If the base can be exported from a phone with one tap but not from a computer, the protection only works halfway.

Clients, contacts and the shared spreadsheet

The most vulnerable part of the base is contacts. Properties are visible in listings anyway, but owners’ and buyers’ phone numbers with their requests are what the agency has collected over years. Compare two approaches:

Shared spreadsheet

Everyone has every contact

  • Anyone can copy the whole base in a minute
  • It’s unclear who last changed a record
  • A deleted row can’t be recovered
  • An agent leaving means part of the base leaving

Protection of the base on trust alone

Roles in a system

Everyone sees their own

  • Contacts are seen by the responsible agent and the manager
  • Every change is recorded in the card’s history
  • Deleted items go to an archive instead of vanishing
  • When someone leaves, clients are handed over, not lost

Protection of the base built into the work

Client correspondence is a separate issue. If it lives on an agent’s personal phone, it leaves with them. When Telegram conversations with clients go through the agency bot and gather in the agency’s Chats, the history of contact stays on the client card, whoever is handling them.

When an agent leaves

An employee leaving is when roles are put to the test. For it to go calmly, it’s better to write the procedure down in advance rather than make it up on the day.

What to do when an agent leaves

A manager’s checklist

  1. Revoke accessOn the day they leave

    System login, shared chats, work numbers - before the farewell conversation, not after.

  2. Hand over clientsSame day

    Every active client gets a new responsible agent.

  3. Reassign dealsSame day

    Open deals go to other agents, with a note on what stage they’re at.

  4. Check exportsFirst week

    The action log: were there any mass exports of the database in the last few days.

  5. Tell the clientsFirst week

    The new agent introduces themselves - a client shouldn’t learn about the change by accident.

The procedure is the same for any departure, amicable or not: that way nobody takes it as personal distrust.

It’s important that the rules for handing over clients are known to everyone in advance, including how commission is split on deals the departing agent took halfway. More on this in our article on commission splits.

The action log: memory, not surveillance

The action log records who opened a card and when, changed a price, exported a list or deleted a record. Many managers fear the team will see it as surveillance. In practice the log isn’t there to watch every click but to work out what happened when something goes wrong.

  • A property’s price changed without approval - the log shows who and when.
  • A client complains that two agents called them - you can see who contacted them and when.
  • There were mass exports before an employee left - you see it right away, not a month later.

Tell the team plainly that the log exists and why. An openly announced log disciplines more than hidden control and removes suspicion: if something happens, it will be sorted out on the facts. The overall picture of the team’s work, though, comes not from the log but from agency analytics: the funnel by stage and where clients come from.

How to introduce roles without a revolt

If everyone used to see everything, introducing roles can look like distrust. To avoid that, explain to the team why it’s needed before anything changes.

  • Start with the explanation: roles also protect an agent’s clients from being taken by colleagues.
  • Introduce a simple scheme of three or four roles first, not a complex matrix of rights.
  • Check that nobody has lost access to what they need for their daily work.
  • Review roles once a quarter and with every change in the team.
  • Appoint one person who is responsible for roles and to whom questions about access go.

Roles are easiest to explain to newcomers on their first day, as part of getting to know the system. How to structure a new agent’s first two weeks is covered in our article on onboarding, and what to check in an agency CRM in general in our 12-point checklist.

The roles and procedures in this article sum up agency practice; choose a specific access scheme to suit the size of your team and how work is divided in it.

Read next