DMS · 10 systems
DMS user access across every rooftop, handled for you.
StitchOps gives new hires their DMS login the day HR adds them and removes it at every store the moment they leave. Each month it checks who can still log in to the DMS at each rooftop, and it keeps a record of every change.
See all 10 below ↓The DMS is where the money lives.
Deals, customer files, parts, service and the books all sit in the DMS. A former salesperson or office clerk who can still log in can still see all of it. In a dealer group, that login usually exists at more than one store.
The manual way does not scale past one store.
Today the office manager or the controller sets up and removes DMS users by hand, one rooftop at a time. When three people leave in the same week, someone gets missed. Nobody has time to compare the DMS user list against who actually works at each store.
What StitchOps does across your DMS.
When HR adds a new hire, StitchOps sets up their DMS login with the right access for their job. When someone moves from sales to F&I, it updates what they can reach. When someone leaves, it removes them at every store, and each month it flags DMS users who no longer work for you.
Reports pulled on a schedule.
StitchOps can also pull the DMS reports your controller runs every month and put them where they expect them. It logs in the way a person would, so it works whether your stores run CDK, Reynolds, Tekion, Dealertrack, PBS or another DMS.
Every DMS system we support.
If yours is not here and it has a login, we can still run it.
CDK Drive
US · CanadaCDK Global
CDK's dealer management system, where deals, parts, service and accounting live.
How StitchOps runs it →CDK Unify
US · CanadaCDK Global
CDK's newer cloud dealer management system.
Reynolds and Reynolds
US · CanadaReynolds and Reynolds
The Reynolds dealer management system many stores have run on for decades.
How StitchOps runs it →Reynolds ERA-IGNITE
US · CanadaReynolds and Reynolds
The Reynolds DMS screens your office, parts and service staff use every day.
How StitchOps runs it →Reynolds POWER
US · CanadaReynolds and Reynolds
Reynolds' older DMS platform, still running at many rooftops.
Tekion ARC
US · CanadaTekion
Tekion's cloud dealer management system.
How StitchOps runs it →Dealertrack DMS
US · CanadaCox Automotive
The Dealertrack dealer management system from Cox Automotive.
How StitchOps runs it →PBS Systems
US · CanadaPBS Systems
A dealer management system used by stores across Canada and the US.
How StitchOps runs it →Quorum
US · CanadaQuorum Information Technologies
A Canadian dealer management system.
Auto/Mate
USAuto/Mate
A dealer management system used by many single and small group stores.
Common questions.
Does this work if our stores run different DMS systems?
Yes. StitchOps logs in to each DMS the way your staff would, so a group with CDK at some stores and Reynolds at others is handled the same way. Every change is recorded.
Can you remove a user from the DMS at every store when they leave?
Yes. When HR or your identity system marks someone as gone, StitchOps removes their DMS login at every rooftop where they had one, along with the CRM and the portals you choose.
Do you need our DMS admin password?
StitchOps uses the admin login kept in your password vault, such as 1Password or Keeper, or in the StitchOps vault. It is used only on a secure computer inside your network, and the AI never sees it.
Can it tell us who still has DMS access but should not?
Yes. The monthly access check pulls the DMS user list at each store, compares it to who actually works there, and flags anyone who should not have access.
Guides for this.
- 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 →
For your IT team
- Where it runs
- An agent runs an unattended desktop session on a dedicated worker VM in your environment, on Windows or macOS. It connects outbound only over TLS 1.2 or later. No inbound ports are opened.
- Credentials
- Credentials stay in your vault (1Password or Keeper) or in the StitchOps vault, encrypted with AWS KMS and resolved on the worker at run time. Models never see the values.
- Identity systems
- Changes in Okta, Entra ID or Active Directory can start a task. StitchOps carries them into dealer systems that have no SCIM or API. JumpCloud is supported through our joint program. StitchOps is listed in the Okta Integration Network.
- APIs where they exist
- Where a system offers an API, such as Authenticom DealerVault or Fortellis, StitchOps uses it. Everything else runs through browser or desktop automation, anywhere a person can log in and act.
- Logs and telemetry
- Every run keeps step level logs with status, timing and redacted results. Telemetry is content free: no field values, no personal data, no screenshots.
- Security reviews
- SOC 2 Type 2 audit completed. ISO 27001 certified. Penetration tested by a third party. The security packet is shared under NDA.
- AI assistants
- Approved tasks are available as MCP tools to Claude, ChatGPT and Copilot. Destructive actions need explicit confirmation.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with your DMS logins.
Fifteen minutes on your top three manual jobs. We tell you which one to hand off first.