How to remove a fired employee from every dealership system
List every system the person could log in to, remove them from each one the same day, change any shared passwords they knew, and keep a record of what you did. StitchOps does this automatically: when HR marks someone as gone, it removes their access in the DMS, the CRM, lender portals and OEM portals at every rooftop, and saves a record of each step.
Last updated
Why this goes wrong at most stores
A salesperson is let go on a Tuesday. HR runs the final paycheck. IT turns off their email. And then everyone assumes the rest is handled.
It usually is not. A dealership runs on dozens of systems, and most of them have their own login. The DMS, the CRM, RouteOne, Dealertrack, 700Credit, every OEM portal, the inventory tools, the phone system. Each one needs its own removal. In a dealer group, multiply that by every rooftop the person touched.
Until each login is gone, a former employee can still:
- Look up customers, deals and phone numbers in the CRM
- Pull credit or submit a deal through a lender portal
- See incentive and warranty information in an OEM portal
- Use a shared password they learned on the job
The manual way
If you do this by hand, here is the order that works.
1. Start from HR the same day
Make the termination in HR or payroll the trigger. If HR is not told first, nothing else starts. Systems like ADP Workforce Now are usually the first to know.
2. Pull up your list of every system
You need one written list of every system at every rooftop, with who holds admin access to each. If you do not have one yet, start with the dealership offboarding checklist.
3. Remove access system by system
Work from the most sensitive down:
- Credit and F&I: RouteOne, Dealertrack credit and eContracting, 700Credit
- The DMS: CDK Drive, Reynolds and Reynolds, Tekion ARC, Dealertrack DMS
- The CRM: VinSolutions, DealerSocket, Elead
- OEM portals: GM GlobalConnect, Ford FMCDealer, Stellantis DealerCONNECT
- Everything else: inventory, marketplaces, phones, chat, service tools
Do it at every rooftop where they had a login, not just their home store.
4. Change the shared passwords they knew
Any login shared by a department, like a marketplace account or a parts site, needs a new password. Put the new one in your password vault, not on a sticky note.
5. Write down what you did
Note each system, the time, and who removed the login. If an auditor, a lender or an OEM asks later, you want that record.
The hard part is not any single step. It is doing all of them, at every store, every time, during a week when the office manager is also closing the month.
How StitchOps handles it
StitchOps runs the removal for you, in every system that has a login, whether or not that system has a way for other software to connect to it.
- Starts from HR or your identity system. When HR, Okta or JumpCloud marks someone as gone, StitchOps begins.
- Removes access everywhere. It logs in to each system the way your admin would and removes the person at every rooftop: DMS, CRM, lender portals, OEM portals and the rest.
- Changes shared passwords. Shared logins the person knew get new passwords, stored in your vault.
- Keeps a record of every step. Every removal is saved with what was done, when, and the result.
- Checks again every month. The monthly access check catches anyone who slipped through.
The work runs on a secure computer inside your network. Your logins stay in your password vault, and the AI never sees them.
See the full picture for dealer groups on the automotive page.