Amr MagdySalesforce CRM Consultant
Security guide · by Amr Magdy · October 2026

Salesforce access for VAs and cold callers.

Real estate teams can give VAs and cold callers exactly the Salesforce access they need with profiles, permission sets, sharing rules and field-level security, and protect the lead list by removing export rights. Here’s what each role should see, which features do it, and a VA onboarding and offboarding checklist.

Short version
  • Most investor teams have VAs and cold callers, often in other countries. Salesforce lets you give them exactly the access they need: permission sets, sharing rules and field-level security. permission sets
  • Salesforce enforces multi-factor authentication for all employee logins; production enforcement rolled out July 20 to September 3, 2026. Plan it into VA onboarding. source
  • Field history tracking shows who changed what, for up to 20 fields per object. source

What should each role see?

RoleCanCan’t
Cold caller / VACreate and edit leads in their queue; log calls; set outcome and next dateSee deal financials, buyer list, exports, other markets
Acquisitions repOwn leads and deals; make offers; send contractsChange lead source after creation; delete records
Dispo repSee under-contract deals and buyers; send deals; log buyer offersSee seller notes beyond what’s needed
Transaction coordinatorClosing tasks, documents, datesEdit offer or assignment amounts
Owner / managerEverything, including reports and fees—

Which Salesforce security features do this?

FeatureWhat it doesEdition / limit
ProfilesDefault settings for each user; one profile per userCustom profiles in Professional and up
Permission sets and groupsAdd permissions on top of a profile; Salesforce’s recommended approachAll main editions
Sharing rulesOpen record access beyond org-wide defaults, by owner or criteriaProfessional and up; up to 300 per object
Field-level securityHide or make read-only specific fields, across UI, reports and APIProfessional and up
Login IP rangesDeny logins from outside set rangesPer profile in Enterprise and up; Professional needs an add-on for per-profile ranges
MFASecond factor for every employee login; phishing-resistant for adminsEnforced in 2026
Field history trackingWho changed a field, from what, to what, when20 fields per object; 18 months in the UI

Sources: profiles · permission sets · sharing rules · field-level security · login IP ranges · MFA · field history

A VA onboarding and offboarding checklist

Before day one

Create the user with the caller profile and permission set; add to the right queue; confirm MFA method; share the call script and the handoff rules.

First week

Review their call outcomes daily; check the fields they skip; fix the layout before blaming the person.

Ongoing

Weekly calibration: compare their warm and hot leads with what acquisitions found.

Offboarding (same day)

Freeze then deactivate the user; reassign open leads and tasks to the queue; revoke integrations or dialer seats tied to them.

How do you protect your lead list?

  • Remove the export permission from caller and VA profiles; only owners export.
  • Give VAs list views, not report builder access, if they don’t need it.
  • Track changes to lead source, phone and owner with field history.
  • Keep integration users separate from people, so a departing VA can’t take an API connection with them. API access itself is included in Enterprise and an add-on for Professional. source

The other ways data can leave, and what you can see after the fact, are in stopping reps from exporting your seller list.

Questions

How do I give a VA limited access in Salesforce?

Give them a restricted profile plus a permission set with only what they need, hide sensitive fields with field-level security, and use queues and sharing rules so they see only their leads.

Does Salesforce require MFA for VAs?

Salesforce enforces multi-factor authentication for all employee logins, with production enforcement rolled out from July 20 to September 3, 2026.

Can I stop VAs exporting my leads?

Yes. Export is a permission; leave it off caller and VA profiles and permission sets so only owners can export.

Sources

  1. Salesforce Help: user profiles
  2. Salesforce Help: permission sets
  3. Salesforce Help: sharing rules
  4. Salesforce Help: field-level security
  5. Salesforce Help: login IP ranges
  6. Salesforce Help: MFA enforcement
  7. Salesforce Help: field history tracking
  8. Salesforce Developers: API supported editions

Last updated October 2026. Product names, editions and limits change; check the linked source before you rely on one. Not legal advice.

Want your team’s access set up right?

I build Salesforce for real estate investors and wholesalers, set up around how your team actually works. Start with a free 30-minute call or the fixed-price CRM Revenue Audit (USD 1,500).

Book a free 30-minute callSee the Revenue Audit

Already on Salesforce? See a sample audit report. On Podio, REsimpli or GoHighLevel? See how a move to Salesforce works.

Or just ask one question about your setup: email · WhatsApp · LinkedIn

Amr Magdy

About the author: Amr Magdy

Amr Magdy is a Salesforce CRM Consultant for US real estate investors and wholesalers. He runs the Salesforce for a two-market home-buying company in Ohio, where he built campaign ROI by market, missed-call alerts, shared lead queues and underwriting on the deal record, and he builds the same system for other investor teams. LinkedIn · Free tools · CRM Revenue Audit

Book a free callThe audit