Does a portal login stop working when someone leaves the dealership?

Not on its own. The portal does not know they left. The login keeps working until an admin at your store, or the portal's own support, removes it.

Can a former salesperson still pull credit?

If their credit or lender portal login was never removed, they may still be able to log in. That is why credit and lender portals should be the first logins removed.

What if the salesperson goes to work for a competitor?

Then their old login can show them your deals, customers and pricing. Remove access before or as they leave, not after you hear where they landed.

Who removes OEM portal access?

It varies by brand and by store. Often one person at each rooftop manages OEM portal users. StitchOps can do it at every rooftop using the admin logins in your vault.

Dealer guides

What happens to dealer portal logins when a salesperson quits

Usually nothing, unless someone removes them. Lender portals, OEM portals and credit tools each have their own login, and quitting does not turn any of them off. StitchOps removes a departing salesperson from every portal at every rooftop when HR marks them gone, and keeps a record of each removal.

Last updated October 2, 2026

The short answer

Each portal has its own login. When a salesperson quits, the portal does not find out. Their login keeps working until someone removes it.

Turning off their email or their computer account does not help, because most dealer portals do not use those to log in.

What they can still reach

That depends on the portal and their access level. In general:

Credit and lender portals like RouteOne, Dealertrack and 700Credit hold credit applications and deal jackets with your customers' personal information.
OEM portals like GM GlobalConnect, Ford FMCDealer, Stellantis DealerCONNECT, Hyundai WebDCS and Kia KDealer hold incentive programs, vehicle orders, sales reporting and your store's information.
The CRM, such as VinSolutions or Elead, holds every lead, customer and phone number they worked.

A salesperson who walks across the street to a competitor can take a lot with them if those logins still work.

Why portals get missed

Nobody owns the full list. HR knows the person left. The F&I director knows about RouteOne. The office manager knows about the DMS. Nobody knows about all of it.
Every rooftop is separate. A salesperson who covered two stores has two sets of logins.
Portal admins are spread out. One person manages OEM users at one store, someone else at another.
It is not urgent until it is. Removals wait until the end of the week, then the end of the month.

The manual way

Keep one list of every portal at every rooftop, and who can remove users from each. The dealership offboarding checklist is a good start.
When someone gives notice or is let go, remove credit and lender portals first, then the CRM and DMS, then OEM portals.
Change any shared portal passwords they knew.
Write down each removal with the date and time.
Check again at the end of the month.

How StitchOps handles it

Starts when HR says so. A termination in HR, or in Okta or JumpCloud, starts the task.
Removes every portal login. StitchOps logs in to each portal the way your admin would and removes the person at every rooftop. That includes portals that have no way for other software to connect.
Changes shared passwords. New passwords go into your vault.
Keeps a record. Each removal is saved with what was done, when, and the result.
Checks every month. The monthly access check catches anything missed.

The full process is in how to remove a fired employee from every dealership system. More on the automotive page.