Access control
CRM user roles: give every sales role the right access, not the whole spreadsheet
Every sales team has people with different jobs: reps who work leads and deals, a manager who reviews the pipeline, someone who looks after pricing, contractors who help for a season. A shared spreadsheet gives all of them the same access to everything. This article follows one illustrative team through the usual workarounds, what Microsoft and Australia’s privacy regulator say about their limits, and how Saleslox user roles fix it.
The scenario: twelve people, one workbook, one password
Illustrative scenario. Kestrel Bay Packaging, its people and its numbers are invented to show a common pattern. It is not a Saleslox customer, and no results are claimed for it.
Kestrel Bay sells packaging to food producers. It has nine reps, a sales manager, a part-time pricing analyst and, for the busy season, two contract agents. Everything runs from one shared “Sales master” workbook: Accounts, Pipeline, a Price list with a margin column reps are not supposed to see, and a Commission tab.
The contract agents were given the link on day one because there was nothing smaller to give them. The pricing analyst password-protected the Price list, then shared the password with the manager, who passed it to a senior rep one busy Friday. One Monday, someone sorted the Pipeline tab on a single column and deal values landed against the wrong customers. Nobody knew who did it, and the last clean copy was a week old.
Nobody here did anything malicious. The problem is structural: the only access levels a workbook offers are “has the file” and “does not”, so every new person gets everything.
The problem: different jobs, identical access
A sales cycle passes through several hands: reps work leads and deals, a manager reviews the pipeline, someone maintains prices, finance invoices. Each needs a different slice of the same records.
When everyone shares one file, people see what they have no reason to see, such as margins or commission; they change what they should not, usually by accident; and when someone moves on, their copy goes with them.
Security practice has a name for the fix. NIST defines least privilege as the principle that a system should restrict the access privileges of users to the minimum necessary to accomplish their assigned tasks [4]. For a sales team, that simply means each person opens the parts of the CRM their job needs, and no more.
What teams use today, and what it costs
Sheet protection and shared passwords
The first workaround is protecting the sensitive sheet. Microsoft is direct about what that does: worksheet-level protection is not intended as a security feature, and it simply prevents users from modifying locked cells within the worksheet. Microsoft also warns that you should not assume a workbook or worksheet is secure just because it is protected with a password [1]. Protection can stop an accidental overwrite. It does not stop a rep from reading the margin column.
File passwords for read-only and edit access
The next step is file-level protection. Microsoft’s own example is a team status report where managers can edit and team members only read: you protect the file with two passwords, one to open and one to modify, and share the appropriate password with each person [1]. That gives two access levels, but each is a shared secret: you cannot take a password back from one person without changing it for everyone.
Separate copies for separate people
So teams split the file into cut-down copies for agents and reps and a master for the manager. The access problem becomes a version problem: every copy drifts, and someone merges them by hand.
What it adds up to
The cost is partly time, in the clean-ups and merges, and partly risk. Australia’s privacy regulator, the OAIC, received 532 data breach notifications from January to June 2025. Human error caused 37% of them (193 notifications), up from 29% in the previous period, and the OAIC notes that the human factor remains a notable threat regardless of how secure an organisation’s systems are [2]. Those figures cover all reporting organisations, not sales spreadsheets specifically, but a file everyone can open, copy and email gives human error plenty of room.
The OAIC’s guidance on securing personal information makes the same point in practical terms. To reduce trusted insider risk, it recommends limiting internal access to those who need it to do their job, on a “need to know” basis, and asks whether the number of users with administrative privileges is limited and whether access is revoked promptly when it is no longer required [3]. A shared workbook makes all three questions hard to answer with a yes.
How Saleslox gives each person the right access
The fix is not a stricter workbook. It is keeping the records in one system and deciding, per person, which parts of it they can open. The screenshots below are real Saleslox screens from a demo workspace on the Enterprise plan; where a feature depends on the plan, we say so.
Step 1: start from roles, not from the file
In Saleslox, access is set in Organization settings on the User Roles tab. As the screen puts it, preconfigured roles bundle the tabs a person can open. The Sales person role, for example, covers companies, leads, products, the deal board, quotes, orders, timesheet and expense, and here it has two active users assigned. Each tab is a tick box: in this demo workspace Companies, Leads, Products, Opportunities and Quotes are ticked for sales people, and Commercial agreements is not. Kestrel Bay’s price-list problem becomes a setting, not a password.
Step 2: give admin rights tab by tab
Beside every tab in a role sits its own Admin tick box, so the person who maintains products can be an admin of Products without becoming an admin of everything else. Saleslox also states the boundary plainly on screen: app admin only elevates the tabs a role already opens, so a sales person who is also app admin does not get Support, Dashboards or Documents. Tabs above your current plan stay visible, so they light up after an upgrade.
Step 3: create a custom role for the people in between
Some people never fit a standard role, like Kestrel Bay’s seasonal agents. On the same screen, an admin names a custom role, adds a description, ticks the tabs it should open and clicks Create role, then assigns it to people on the Users tab. The agents get leads, companies and the deal board; the analyst gets products. Custom user roles are on the Pro and Enterprise plans, and the 30-day trial is Pro.
Step 4: everyone works the same records
Roles only help if there is one set of records to apply them to. In Saleslox, the people who can open Leads all work the same board, with stages from New and Working through Pre Qualif to Qualified, with a territory filter and grouping by salesperson, company or contact. Search covers company, contact name, email, phone, source, notes and salesperson. There is no agents’ copy to merge back.
Step 5: the history stays with the company, not the person
Because work happens on shared records, changing someone’s access does not take the customer history with them. A company record keeps its details, contacts, activities, leads and agreements in tabs. When a contract agent’s season ends, you change their user, not your data. Organization settings also has Recycle bin and Audit log tabs alongside Users and User Roles, and on Enterprise you can add an IP allowlist for tenant access.
Shared workbook vs Saleslox user roles
| Task | Shared workbook | Saleslox |
|---|---|---|
| Hide prices or margins from reps | Sheet protection, which Microsoft says is not a security feature | Leave that tab unticked in the role |
| Read-only vs edit | Two shared file passwords | Each person signs in with their own role |
| Admin rights | Whoever knows the password | An Admin tick box per tab; app admin only elevates tabs the role opens |
| Onboard a contractor | Send the link or make a cut-down copy | Create a custom role and assign it on the Users tab (Pro and Enterprise) |
| Someone leaves | Their copy leaves with them; change every password | Change their user; the records stay in Saleslox |
| Which version is right? | Merge the copies and hope | One set of records for everyone |
How to test this on your own team
- List everyone who opens your sales workbook, and the tabs each person actually needs.
- Count how many people know the passwords to your price, margin or commission sheets.
- In a Saleslox trial, compare that list with the preconfigured roles, and create a custom role for anyone who does not fit.
- Sign in as a test user in each role and check that they see the tabs they need, and nothing else.
The trial is 30 days of Pro, with no card required. For the related problems of a rep leaving and inconsistent data, see handing over accounts when a sales rep leaves and consistent CRM data.
Frequently asked questions
What does a user role control in Saleslox?
A role is a named bundle of the tabs a person can open, such as Companies, Leads, Products, Opportunities and Quotes. You assign roles to people on the Users tab in Organization settings. Each tab in a role also has its own Admin tick box.
Does making someone app admin give them every tab?
No. On the User Roles screen Saleslox explains that app admin only elevates the tabs a role already opens. A sales person who is also app admin does not get Support, Dashboards or Documents.
Which Saleslox plans include custom user roles?
Custom user roles are on Pro and Enterprise. The 30-day trial is Pro, so you can build and test your own roles during it. The screenshots here are from Enterprise; see compare plans for what each plan includes.
Is Excel sheet protection enough to control who sees our pipeline?
Microsoft says worksheet-level protection is not intended as a security feature; it only stops people changing locked cells. File passwords can separate read-only from edit access, but the same password is shared by everyone who holds it.
Is Kestrel Bay Packaging a real Saleslox customer?
No. Kestrel Bay Packaging and every person and number in its story are invented to illustrate a common pattern. No customer results are claimed.
Sources
- Microsoft Support. “Protection and security in Excel.” support.microsoft.com
- Office of the Australian Information Commissioner (4 November 2025). “Latest Notifiable Data Breach statistics for January to June 2025.” oaic.gov.au
- Office of the Australian Information Commissioner. “Guide to securing personal information”, section on trusted insider risk. oaic.gov.au
- NIST Computer Security Resource Center. Glossary: “least privilege”. csrc.nist.gov