Real Estate CRM Contact Privacy: Who Sees a Phone Number

A lead’s phone number is the one piece of data an agent cannot work without. It is also the piece a departing employee can copy in minutes: a screenshot, an export, a message to a personal phone.

For a brokerage, the client list is a core asset built with portal spend, campaigns and years of follow-up. Real estate CRM contact privacy is about deciding who inside the company can read those details, rather than assuming everyone who can see a lead needs to contact them.

This guide explains the thinking, and how IRM365 implements it.

Seeing a lead is not the same as contacting them

Many CRMs treat access as one switch: if you can open the lead, you can read the phone number. That is too blunt.

• A team manager reviews pipeline and coaching, and does not need to call every client.
• A marketing role measures campaign results across all leads.
• A reporting analyst needs counts, not contact details.

To protect real estate leads, separate the right to see a record from the right to read its contact details. Everyone keeps doing their job, and the number of people who can lift the full client list shrinks.

Three levels of visibility

IRM365 uses three levels for a lead’s phone number and email:

Level	What the viewer sees
Full	The whole phone number and email address
Masked	Something like +971 ••• •• 67, enough to recognise a lead, not enough to contact it
Restricted	Nothing, the field reads “Restricted”

Masked values are built from the stored number, so they always match the real one.

Who gets which level

The first rule that matches the viewer wins:

1. Super admins see Full, always.
2. The agent the lead is assigned to sees Full. The owner of the work can always contact their lead.
3. Anyone holding the View Contact Details permission sees Full on every lead they can see. The Leads Admin role holds it by default.
4. A manager of the agent who owns the lead sees whatever the company has set for managers. It ships as Masked.
5. Everyone else who can reach the lead sees whatever is set for other viewers. It ships as Restricted.

The fifth rule is the important one. A role that can see every lead, such as marketing, reporting or an analyst, falls here rather than in the manager line. It cannot browse the whole company’s contacts, even in masked form.

The two settings, one for managers and one for other viewers, can each be set to Full, Masked or Restricted under Settings → Lead Contact Privacy. A live preview on the page shows what each group would see before you save. Changes take effect immediately.

Why masking works for managers

A masked number lets a manager recognise a record they already know: “this is the 67 number from the Marina enquiry”. It does not let them dial it. That fits a manager’s real job of reviewing a team’s work, and it prevents the manager from becoming the easy route to the full list.

When a manager genuinely needs more, there is a clean answer: set managers to Full, or grant View Contact Details to one person or role, such as a call-centre supervisor. It should not be a substitute for assigning the lead.

It has to apply everywhere

Privacy that applies only to the lead page is easy to bypass. IRM365 applies the same decision wherever a lead’s contact details could appear:

• the lead page and the leads table
• opportunities, customers, campaigns and sales offers that carry the lead
• global search
• exports
• lead notification emails
• the sales offer PDF

Two practical details are worth knowing.

Search. Searching by phone number or email is limited to people who can read those details on every lead they can see. Searching by name or reference works for everyone.

Notification emails. One notification email goes to the agent, their manager and the leads admins together, so it cannot show each of them a different amount. It carries the reference and a button that opens the lead, where each reader sees what they are entitled to. Contact details inside submitted form answers are removed.

The decision is also made on the server: a viewer without access never receives the value, so it is not just hidden on the page.

The exception: reviewing an approval

Privacy should not get in the way of a reviewer’s decision. When a manager is asked to approve a lead disqualification with a reason like “fake number”, they need to see the number to judge it.

So on an approval request page, and only there, a reviewer sees the full phone and email when all of these hold: they are the request’s reviewer, the request is still open, and the lead’s agent is in their own team. Once the request is decided, or for anyone else, the normal setting applies. See how approvals and audit fit together for the wider picture.

A practical setup for a brokerage

1. Decide who truly needs Full access beyond assigned agents, and keep that list short.
2. Leave managers on Masked unless there is a clear reason, so they can recognise records.
3. Keep other viewers on Restricted.
4. Grant View Contact Details only to roles whose job is to contact any lead.
5. Review the audit log when roles change.

Combine this with proper lead management and assignment rules, so an agent’s access follows the leads they own.

The bottom line

Contact privacy does not replace trust or contracts. It reduces how much of the client list sits within reach of any one person, while leaving agents free to work their own leads and managers able to recognise records.

To see how roles, permissions and audit history work together, explore admin and security and how IRM365 supports UAE real estate teams.