Dealer guides

Who can still log in, and how to fix it.

Plain answers for office managers, controllers and the IT person who covers every rooftop. Each guide covers the manual way first, then how StitchOps handles it.

How to automate user provisioning without upgrading every app to its SCIM plan
Keep SCIM where your plan already includes it, and automate the rest on the plans you have. Sort your apps into three groups: SCIM included, SCIM only on a higher plan, and no SCIM at all. Your identity provider handles the first group. StitchOps carries the same joiner, mover and leaver events into the other two, so you only upgrade where you need the higher plan for something else.
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.
The dealership offboarding checklist
When someone leaves a dealership, their access has to come out of far more than email: the DMS, the CRM, credit and lender portals, OEM portals, inventory and marketplace sites, phones and chat, service tools, keys, and every shared password they knew. Use this checklist at every rooftop they worked at, or let StitchOps run it for you.
The FTC Safeguards Rule and who can log in at your dealership
Dealerships that arrange financing are generally covered by the FTC Safeguards Rule, which requires a security program that limits access to customer information to the people who need it. Removing access the day people leave, checking every month who can log in where, and keeping a record of both are practical ways to support that. StitchOps does all three across every rooftop.
How to run a monthly access check across your dealer group
Each month, pull the user list from every system at every rooftop, compare it to who actually works for you, and remove or question anyone who should not be there. StitchOps does this automatically: it downloads each user list, compares it to your HR roster, flags the mismatches, and keeps a record of the check.
How dealer groups handle new hire setup across multiple rooftops
Most groups set up new hires by hand: the office manager at each store creates logins in the DMS, the CRM, lender portals and OEM portals one at a time. StitchOps starts from HR instead: when a new hire is added, it sets up their logins in every system they need at every rooftop they work at, the same day, with a record of each step.
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.
How to stop paying for unused DMS and CRM seats
Find out how many paid seats each DMS and CRM has, match each seat to a current employee, and release the seats held by people who left or never log in. StitchOps pulls the user lists on a schedule, matches them to your HR roster, and shows which seats you are paying for that nobody uses.

Every supported dealer system → · StitchOps for auto dealerships →

Start with one workflow that never had an API.

Fifteen minutes on your top three manual processes. We tell you which one to run first.

Book a free workflow audit Get a demo

Who can still log in, and how to fix it.

How to automate user provisioning without upgrading every app to its SCIM plan

What happens to dealer portal logins when a salesperson quits

The dealership offboarding checklist

The FTC Safeguards Rule and who can log in at your dealership

How to run a monthly access check across your dealer group

How dealer groups handle new hire setup across multiple rooftops

How to remove a fired employee from every dealership system

How to stop paying for unused DMS and CRM seats

Start with one workflow that never had an API.