Sales manager and salesperson talking across a white sales desk in a dealership showroom, a silver car parked beside them
Resources / Blog

Dealership CRM User Permissions: Who Should See Credit Applications

By Brandon DorseyNovember 16, 2026 · 11 min read

Dealership CRM permissions should follow the job. A salesperson gets what selling needs, not manager-level access to customer data, and full credit applications stay with F&I and the managers whose duties require them.

Last updated: November 16, 2026

Jason Wilkins, dealer principal of Joshua Tree Chrysler Dodge Jeep Ram and Victorville Mitsubishi in California, said on an October 28 episode of Daily Dealer Live, from Car Dealership Guy (CDG), that he saw no issues on his end after Cox Automotive confirmed the VinSolutions incident. His stores made changes anyway. CDG’s Market Pulse of November 3, 2026, quoted how he’d tighten access:

“Make sure that your access [to] the data is specific for each employee. Make sure your salespeople don’t have manager access [to] the data.”

Those two sentences cover most of what a CRM access policy needs to say. A dealership CRM can hold every lead and phone number the store has collected, notes from the desk, trade details, and, depending on how the store is set up, credit applications. What a login can open comes from the role attached to it, and roles can drift as people get promoted or change departments, so the only way to know what a salesperson can see today is to look.

CRM roles are one piece of the access work in dealership cybersecurity, and they’re a piece a store can check on its own.

Who Should See Credit Applications in a Dealership CRM?

The people who work the financing: F&I, plus the sales managers whose job includes structuring or approving deals. A salesperson needs to know where an application stands, and that’s a status, not the application. BDC agents and receptionists shouldn’t be able to open one at all.

Finance manager at her desk in a dealership F&I office with one hand resting on a closed folder

Here’s how I’d sketch CRM user roles at a dealership before anyone touches a setting.

RoleWhat the job needs in the CRMFull credit application?
SalespersonLeads, appointments, and contact history for the customers they work, plus where each deal’s credit standsNo. Status only, if your CRM can show it that way
BDC agentContact details, appointment times, and lead notesNo
Sales or desk managerDeals in progress, trade details, and deal structureOnly if structuring or approving deals is part of the job
F&I managerThe applications for the deals they’re workingYes
General manager or dealer principalStore-wide reports and the pipelineWhen approving deals is part of their role
CRM administratorUser setup and role changesNot by default; admin rights are for setup

Role names and permission settings differ from one CRM to the next, so treat the table as a starting point. If your CRM ties credit applications to a permission a salesperson needs for something else, ask your vendor how to separate the two before anyone settles for manager access on the sales floor.

Giving a salesperson the manager role so they can see a credit decision sooner trades a short wait for one more login that can reach everything a manager reaches, and it gets used at a desk on the showroom floor.

For a dealer group, I’d build the roles once and use the same ones at every rooftop. Standardized roles are simpler to review and easier to support, and a manager who covers two stores gets the same access at both.

The job decides the access.

What Does the FTC Safeguards Rule Say About CRM Access?

For a dealership it covers, the rule requires access controls that admit only authorized users and limit each one to the customer information their duties require. It doesn’t mention CRMs or say how to set up user roles. It sets the standard, and the roles in your CRM are one of the places a store applies it.

Paragraph (c)(1) of 16 CFR 314.4, as published by Cornell’s Legal Information Institute, reads:

(1) Implementing and periodically reviewing access controls, including technical and, as appropriate, physical controls to:

(i) Authenticate and permit access only to authorized users to protect against the unauthorized acquisition of customer information; and

(ii) Limit authorized users’ access only to customer information that they need to perform their duties and functions, or, in the case of customers, to access their own information;

Small silver key in the lock of a gray metal filing cabinet in a dealership finance office, a folder resting on top

Two notes on scope. The FTC’s Safeguards Rule FAQ for automobile dealers treats dealers that finance or facilitate financing for consumers, or that lease vehicles for longer than 90 days, as financial institutions under the rule. And the quoted text protects customer information. The rule’s definitions call someone who applies to you for personal credit a consumer “regardless of whether the credit is extended,” while a customer is a consumer with a continuing relationship with your store, such as a lease or vehicle credit you arranged. Where a walk-away applicant’s file lands is a question for your attorney, and our post on whether the Safeguards Rule applies to your dealership walks through who’s in. In the CRM, I’d protect every credit application the same way.

Two more items in paragraph (c) touch the CRM. Item (5) requires multi-factor authentication for any individual accessing any information system, unless your Qualified Individual has approved reasonably equivalent or more secure access controls in writing. Item (8) requires policies, procedures, and controls “designed to monitor and log the activity of authorized users,” so if your CRM keeps a log of who opened or exported records, someone at the store should be reading it.

The rule leaves the design of the roles to you.

How Do You Review CRM User Roles at a Dealership?

Give one person with CRM admin rights a current staff list and some time away from the desk. Start from the user list: every login should belong to someone who works for you today, in a role that fits the job they do now. Then fix the settings around those logins, and write down what changed.

CDG gave the rest of Wilkins’s checklist in one line: “No shared logins, remove former employees immediately, turn on IP filtering, ban saved browser passwords, and set computers to lock when people step away.” Here it is as a review your store can run this week, with the role checks added.

Two dealership managers at a small office table going over a printed list, one marking it with a yellow highlighter
  1. Pull the active user list and match every login to someone who works for you today. Anyone who has left comes off now, and our employee offboarding checklist covers the rest of their systems.
  2. Replace shared logins with named accounts, so every action traces back to one person.
  3. Check each salesperson’s role against the job. Nobody on the sales floor needs manager-level access to customer data.
  4. Who can open a full credit application? Write down who should, and then compare it with who can.
  5. Exports and bulk downloads: only for the roles that need them.
  6. Turn on multi-factor authentication and IP filtering, if your CRM supports them.
  7. Clear saved CRM passwords out of browsers on shared computers, and set screens to lock when people step away.
  8. Record what changed, who approved it, and the date. Then put the next review on the calendar.

IP filtering, where a CRM offers it, accepts logins only from network addresses you approve, such as the store’s own internet connections, so a stolen password alone won’t get someone in from an address you haven’t approved. It also needs an owner, because salespeople who work from their phones or from home need an approved way in, and the list needs updating whenever the store’s internet addresses change, such as after a switch in providers.

Saved passwords are the other one. A shared computer that remembers a manager’s CRM password lets whoever sits down next open the CRM as that manager, and any activity log will show the manager’s name. Passwords belong in a password manager, not in a browser on a shared desk. Screen locks close the same hole from the other side: a computer on the sales floor that stays signed in while its owner walks a customer out to the lot is open to the next person who sits down.

Every change gets a name and a date.

What Should You Tighten When a Vendor Is Hit?

The first “Do” on CDG’s list from dealers was this one: “Tighten access as soon as a vendor is hit, even if you see no impact.” A clean network at the store doesn’t tell you what happened to records on the vendor’s side, so reset the accounts that see the most and check what connects to the system.

Dealer principal and general manager talking in a dealership office, a closed folder on the desk between them

I agree with that rule. A known risk is the time to act, and a vendor incident is a known risk even when nothing at the store looks different. Resetting passwords for the managers, F&I, and anyone with admin rights, removing accounts nobody can explain, and confirming multi-factor authentication is on are small jobs next to finding out later what an old manager login could reach.

For the record, Cox told CDG News on October 26 that the activity “was quickly contained.” A vendor can handle an incident well, and you’d still tighten access, because the accounts in question are yours. Our post on the VinSolutions incident has the fuller list for that event, including the integrations that connect other systems to the CRM.

Wilkins’s stores went past permissions, too. According to CDG, they made “proactive changes to limit the data going into the CRM, credit apps in particular.” If the full application already sits where F&I works, it’s worth asking whether the CRM needs a copy or only the status. Data that never goes into the CRM can’t come out of it.

CRM Roles Carry Over Into AI Tools

If your store connects an AI tool to the CRM, or switches on an AI feature inside it, the roles you set either come along or get skipped. An assistant that reads the CRM through an admin account can answer a salesperson’s question with an admin’s reach, which undoes the role you gave that salesperson without anyone changing a setting. Before an AI tool reads customer data, connect it with the narrowest access it needs, and if it can respect each user’s own permissions, turn that on.

Rex Marchant, our Vice President of Service, covers the AI side in his post on least-privilege access for AI tools. Fix the roles before AI inherits them.

Questions to Expect When You Tighten CRM Access

Won’t salespeople lose deals if they can’t open credit applications?
They need the answer, not the application. A salesperson’s next move depends on whether the deal is approved, conditioned, or declined, and if your CRM can show that status on its own, the full application can stay with F&I.
Our CRM vendor handles security. Isn’t that enough?
Only for the part they run. The vendor secures the platform, but the users, roles, and export rights inside your store’s account are your store’s decisions, even when the vendor’s support team is the one making the change.
How often should a dealership review CRM permissions?
The rule’s own words are “periodically reviewing access controls,” with no schedule attached, so pick one you’ll keep. I’d suggest a quarterly pass, plus a check whenever someone changes jobs and whenever a vendor that holds your customer data reports an incident.
Who should own CRM permissions at a dealership?
One named person, with a manager approving every role change. Ownership is the point. In a group, the same person or team can keep the roles standardized across stores, which makes them simpler to review and easier to support.

Start With the Credit Application List

If you do one thing from this post, pull the list of people who can open a full credit application in your CRM and go through it with whoever runs F&I. Every name on it should have a reason. Once that list is right, the other roles follow the same logic, and they become something your store can operate and defend instead of settings nobody remembers changing.

Helion Technologies has spent nearly 30 years working only with automotive and heavy truck dealerships and has 2,000-plus of them under management. If you’d like an outside look at the bigger picture, our Complimentary IT & Cybersecurity Assessment reviews your current technology setup, your cybersecurity posture, vendor spend, where you stand against the FTC Safeguards Rule, and whether staff are using AI tools outside your security controls, with no cost and no obligation. The findings come back in a written report.

Access that matches the job is simpler to run and easier to defend.

About the author

Brandon Dorsey

Vice President of Technology Strategy, Helion Technologies

Brandon Dorsey is Vice President of Technology Strategy at Helion Technologies and a Certified Information Systems Security Professional (CISSP). In more than 20 years with Helion, he has worked across dealership IT support, infrastructure, cybersecurity, compliance and design.

Brandon Dorsey on LinkedIn

Confidence in your current setup and actual protection aren't always the same thing. The only way to know which one you have is to look.

Get Your Complimentary IT & Cybersecurity Assessment →