How long should new hire setup take?

Ideally, the new hire can log in to everything on their first day. In practice, setup often waits on whoever has admin access to each system, so it drags into the first week.

Can StitchOps set up the same person at more than one rooftop?

Yes. If a new hire works at two stores, StitchOps sets up their logins at both, in each system they need there.

How does StitchOps know what access a new hire needs?

You decide that once per job. For example, a salesperson gets the CRM, the DMS and credit tools; an F&I manager also gets lender portals. StitchOps follows that list for each new hire.

What about role changes, like sales to F&I?

The same task handles them. When HR records the new job, StitchOps adds the new access and removes what the old job needed.

Where do the new passwords go?

Into your password vault, such as 1Password or Keeper, or the StitchOps vault. The AI never sees them.

Dealer guides

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.

Last updated October 2, 2026

The problem

A new salesperson starts Monday. By Wednesday they still cannot log in to the CRM. By Friday they have the DMS but not RouteOne, so their first deal waits on someone else.

Meanwhile the office manager is setting them up one system at a time, in between payroll, titles and month end. In a dealer group, each rooftop does this its own way, with its own list, if there is a list at all.

The manual way

1. HR adds the new hire

The process starts in HR or payroll, such as ADP Workforce Now, UKG Pro, Paylocity or Paycom. Someone then has to tell each store's office manager.

2. Work out what the job needs

A salesperson, an F&I manager, a service advisor and a title clerk each need different systems. Without a written list per job, setup depends on who remembers what.

3. Create logins system by system

Typical first day systems for a salesperson:

The DMS: CDK Drive, Tekion ARC or Reynolds ERA-IGNITE
The CRM: VinSolutions or DealerSocket
Credit: RouteOne or Dealertrack
OEM portals: GM GlobalConnect, Ford FMCDealer, Kia KDealer and others, depending on your franchises

Repeat at every rooftop they will work at.

4. Hand over passwords safely

Put new logins in your password vault, not in an email or on a note.

5. Write down what was set up

You will need it later when they change jobs or leave.

Why it gets harder with more rooftops

Every store has its own admin for each system. Each store may run a different DMS or sell a different brand. A group of a few rooftops can mean dozens of separate setups for one hire. That is the work that eats the office manager's week.

How StitchOps handles it

Starts from HR. When HR adds someone, StitchOps begins the same day. It works with any HR or payroll system, with no API tax or SCIM tax to pay first: it uses a connection you already have, or reads the HR screens your team uses when there is none.
Follows a list per job. You set once which systems each job needs. StitchOps uses it every time.
Sets up every rooftop. It logs in to each system the way your admin would, at each store the person works at, including systems with no way for other software to connect.
Handles role changes too. When someone moves from sales to F&I, their access changes to match.
Keeps a record of every step. Each login added is saved with what was done and when.

When the same person leaves, the same list drives removal. See how to remove a fired employee from every dealership system. More on the automotive page.