Your seller list is the business. Stopping reps from exporting it in Salesforce

How can data leave Salesforce?

No setting makes leaking impossible. The goal is to close the easy routes, make the hard ones slow and visible, and keep what each person can see to what they need.

Which permissions should you remove?

From Salesforce's own permission descriptions:

• Export Reports "allows the user to use Export Details and Printable View to export reports." Take it off reps, callers and VAs. Keep it for the owner, the manager who runs reports and the admin.
• API Enabled "allows the user [to] execute API calls," which is what Data Loader and similar tools need. Remove it from people who don't need it, but test first: some phone, texting and email tools connect as each user and stop working without it.
• Weekly Data Export lets a user run the weekly Data Export Service. Admins only.
• View All Data and Modify All Data let a user see or change everything in the org, regardless of sharing. Admins only, and as few of them as possible.

The clean way to set this up is a rep profile with none of these, plus an "Export" permission set you assign to the two or three people who need it. Then the answer to "who can export?" is a list you can read in Setup. More on profiles and permission sets for each role in Salesforce access for VAs and cold callers.

Setup Audit Trail shows changes made in Setup, including many profile and permission changes, so you can spot someone quietly given export rights. Salesforce keeps it for 180 days and shows the 20 most recent entries on screen; download it to see the rest.

Limit what each rep can see

This is the biggest lever, and the one most investor orgs skip. A rep who can see 40,000 sellers can photograph 40,000 sellers. A rep who sees their own 300 and their market's open queue can't.

• Set leads to private by default, then open up what each role needs with queues and sharing rules: their own records, their market's shared queue, and the deals they work on.
• Keep the archive for managers. Closed deals, dead leads and other markets don't need to be visible to every rep.
• Hide what callers don't need with field-level security: assignment fees, profit, buyer lists.

There's a trade-off. Investor teams like shared queues because they're fast, and locking everything down slows the team. The middle path above keeps speed where it matters, on new and open leads, and protects the years of history behind them.

Login hours and IP ranges

Both are set per profile. Login IP ranges limit logins to addresses you list, such as your office or VPN, which works well for VA teams in one office. Login hours limit logins to set times, such as a calling shift. Neither suits reps who work from their phones at odd hours, so use them where they fit.

Give every person their own login. Shared logins for a dialer, a texting tool or Salesforce itself mean you can't tell who did what, and you can't shut one person out without locking out everyone.

Can you see who exported what?

Partly, and the useful part costs extra.

• Free: login history shows who logged in, when and from where. Salesforce's free Event Monitoring tier covers a few event types, such as logins, logouts and total API usage, with one day of storage.
• Paid: report exports are a separate event type that needs the Event Monitoring add-on, also part of Salesforce Shield. It covers more than 70 event types, with up to 30 days of storage.
• Blocking: with that add-on, a Transaction Security policy can block a report export above a set number of rows and email someone when a user tries.

For most teams of 10 to 50, the add-on isn't worth it. Removing the permission is the cheap control. It starts to make sense when you have many users, a history of leaks, or a lot of money riding on one list.

What should you do when a rep gives notice?

1. Decide on access first. Whether they work their notice period, and with what access, is the owner's call. Make it before anything else happens.
2. Reassign their open leads, deals and tasks the same day, and take them out of round robin, queues and alerts. The steps are in the new rep and offboarding checklist.
3. Freeze their user. Freezing blocks login right away; it doesn't free the license. Deactivate once nothing depends on the user, such as a report, an automation or an integration running under their name. The admin handover plan covers what to check.
4. Close the side doors. Their dialer and texting logins, shared drives, the data tools where your lists live, and any password they knew.
5. Look at recent activity: logins, and report exports if you have Event Monitoring.
6. Keep the phone numbers. If sellers have been calling a rep's personal cell, they'll keep calling it after the rep leaves. Company numbers in your dialer stay with the company.

What about agreements and the law?

Permissions slow people down. Agreements give you recourse. Whether a confidentiality or non-solicitation agreement holds up depends on your state, so that's a conversation for an employment attorney. Not legal advice.

One thing worth knowing: under the federal trade secrets law, information only counts as a trade secret if the owner took reasonable measures to keep it secret. Removing export rights, limiting who sees what and giving everyone their own login are part of showing that you did.

Questions

Related guides

Sources

Checked in October 2026. Salesforce features and add-ons change, so check the linked page before you rely on a detail. Nothing here is legal advice.

1. Salesforce Help: User profile permission descriptions. Export Reports, API Enabled, Weekly Data Export, View All Data and Modify All Data
2. Trailhead: Learn the core concepts of Event Monitoring. Free event types with one day of storage; report exports and 70+ event types on the paid tier
3. Trailhead: Create a Transaction Security policy. Blocking report exports above a row count, with an email alert
4. Gearset: Salesforce Setup Audit Trail. What the audit trail records, how long Salesforce keeps it and the 20 entries shown on screen
5. Salesforce Help: Login IP ranges. Restricting logins to listed addresses by profile
6. Trailhead: Restrict login hours and IP ranges. Setting login hours on a profile
7. Salesforce Help: Freeze or unfreeze user accounts. Freezing blocks login without freeing the license
8. Ninth Circuit model jury instruction 23.16: trade secret defined (18 U.S.C. 1839(3)). The reasonable-measures requirement