Skip to content

As of

What tools get new hires fully set up on day one?

To get new hires fully set up on day one, run one sequence from the HR record: identity provider account and groups, device, apps by role, then Slack or Teams, with access written as a rule over live HR attributes. STLabs runs the identity and app steps as one workflow connecting your HR and IT systems, triggered by the HR record, and an AI agent applies the same rule again whenever the person's role, team or manager changes.

Key takeaways

  • Day one is the easiest moment in a person's access history, because HR has just created the record and every system agrees about who they are.
  • The day-one sequence starts with the HR record, then the identity provider account and groups, then the device, then apps by role, then Slack or Teams.
  • Access granted from a one-time onboarding template is right for a few months; the first team change, manager change or new project starts it drifting.
  • "Fully set up" should mean access defined as a rule over role, team, location and manager, applied on day one and re-applied every time one of those changes.
  • In STLabs, one workflow connects your HR and IT systems: the HR event triggers it, the identity provider account and the role's apps follow in order, and the same workflow runs again when someone moves or leaves.
  • STLabs keeps HR attributes current in Axiom™, defines access by role in Policies & Approvals, and adjusts access when someone changes roles (Access Lifecycle, Growth plan and up).

Day one has a reputation as the hard part of access. It's actually the easiest moment a person will have. HR has just created them, so the HR system, the identity provider and the hiring manager all agree on their role, team, location and start date. Nothing about them is stale yet.

That's why onboarding tools are built around it. HR platforms, identity providers and service desks each have a new-hire event and a template that fires on it, and most do that job well. If your hires still wait days, the fix is usually the sequence and the role definitions, covered first below.

The harder question is month three. Day-one access was right for the person HR created. A few months later they've joined another team, got a new manager or picked up a project, and the template that set them up has no reason to run again.

What tools get a new hire fully set up on day one?

Four kinds of tool, run in order from the HR record, plus access rules written over live HR attributes so the same definition can be applied again later. Here is what each category does well, and where it stops.

HR platforms with IT features. The HR system is the right trigger, because it knows the hire's role, team, manager, location and start date before anyone else does. Some HR platforms bundle device shipping and app provisioning, and for a small company with one office and a short app list, that can be the whole answer. It gets harder once identity lives in a separate provider and roles differ by country.

Identity provider lifecycle. Okta, Entra ID and similar providers create the account from the HR record, put the person in groups by attribute and push accounts to connected apps. For anything behind single sign-on with a group rule, this is the best tool you have, and group rules are the closest thing most companies have to access as a rule. Their limits are the edges: apps outside single sign-on, licenses that need a person's yes, and grants made by hand that no group rule will ever take back.

Device management. Zero-touch enrollment through Jamf, Intune or similar is how a laptop arrives configured, and it should stay with a dedicated tool.

Service desks. The service desk holds the onboarding request, a parent ticket with a task for each team, and tracks who did what well. Its unit is the request, though, so once the ticket closes, nothing in it knows that the access it granted depended on a team the person may later leave.

Each of these handles the join event. None of them, on its own, holds a definition of what a role should have that it checks again when the role changes.

The day-one sequence, step by step

The order matters, because each step depends on the one before it.

Step 1: the HR record. The hire is entered with department, title, location, manager and start date, ideally a week ahead. Entered on the first morning, nothing downstream can save the day.

Step 2: the identity provider account and groups. Created from the HR record, with the groups that department, location and title imply.

Step 3: the device. Assigned, enrolled and shipped by device management in time.

Step 4: apps by role. Licenses, shared drives and repositories that groups don't cover. Routine access is granted by rule; anything outside it goes to an approver before the start date.

Step 5: Slack or Teams. The hire joins their team's channels and knows where to ask for help on the first morning.

Every step reads an HR attribute, and those attributes are exactly what changes later.

Why day-one access is right for only a few months

Most onboarding templates are a snapshot: read the HR record once, grant a list, close.

Take an engineer hired onto the platform team. On day one they get the platform repositories and production read access, all correct. In month three they move to the data team, and HR updates their team and manager that afternoon. The identity provider moves a group or two. Everything granted by hand or by the onboarding ticket stays put, so they keep production access the data team doesn't use and wait on a ticket for the warehouse access every other data engineer got on day one.

A manager change drifts more quietly. A team gets a new lead in a reorganization, and the access requests its people file next week still route to the old one, because the form copied the approver when the person was hired.

Day one went fine in both cases. The access simply describes a version of the person that no longer exists, and the next access review finds it, months later and by hand.

What "fully set up" should mean

If day-one access comes from a rule, the rule can run again. So write access the way your HR system already describes people: by role, team, location and manager.

"Everyone on the data team gets warehouse access." "Requests outside the role go to the person's current manager." Each rule reads an attribute, so when the attribute changes, the answer does too.

Then day one stops being a special event. It's the first time the rule is applied, and every move after it is another. The engineer from the example would get warehouse access the afternoon HR records the move, and lose the production access their new team's rule no longer covers.

Group rules cover what sits behind single sign-on; the rest of a role's access needs the same treatment, with someone deciding what happens to grants the new role doesn't include. Contractors fit the same model as their own role, with narrower access, an end date set on the first day and a sponsor who approves exceptions.

How STLabs connects HR and IT systems in one workflow with an AI agent

STLabs runs onboarding as one workflow that connects your HR and IT systems. The HR system triggers it, the identity provider provisions the account, the role's apps are granted and Slack notifies, in order. The device stays with your device management tool. The same workflow runs when someone moves or leaves, and HR teams can manage onboarding in the same platform as IT. An AI agent works from a live model of your organization throughout, and your HR system, identity provider and device management stay.

Axiom™ is that live model. It syncs with your HR, identity and device systems, so when someone joins, changes roles or leaves, Axiom™ picks up the change automatically. Every fact records which system it came from and when it was observed, so the agent works from the person's role, team, manager and location as they are now.

Policies & Approvals hold the rules. A policy can allow a request, block it or require approval: a Salesforce license for everyone in sales, a repository for every engineer, production access only with a named approver. When approval is needed, it goes to the manager on the HR record that day, and the workflow waits for the decision before it acts.

Workflows act in the connected tools. On a Workday new-hire event, Axiom™ checks what people in that role already have and a workflow is generated for the role's tools, such as Google Workspace, GitHub and Slack. Workday triggers, Okta provisions, Slack notifies, and all of it lands in one audit trail. This is where being AI-native matters: the agent acts on the model it reasons over, so the record of what it did is also the record of why.

Every AI decision and workflow run goes into a searchable log: who was granted what, under which policy, with whose approval.

Onboarding is the first part of the access lifecycle; see also how to revoke access when people leave. It's included in Access Lifecycle, part of the Growth plan and up. See pricing.

How to test day-one onboarding with an AI agent on your own systems

Run two tests, not one.

For the first, take your next real hire and file nothing. Once HR enters the record, does the identity account appear with the groups that role should have? Do the apps the role needs arrive without a ticket? On the first afternoon, ask the hire what they still had to request. Each item is a rule nobody wrote down.

For the second, find someone who changed teams or managers last quarter. Compare what they can reach today with what a new hire in their current role would get. Anything extra is drift; anything missing is a request waiting to happen. Then check where their next request would route.

If only the first passes, your onboarding works and your access model doesn't.

Day one is the first run

None of this asks you to replace the tools you already run. STLabs works alongside them, and teams go from integration to results in five days, with onboarding and offboarding among the first workflows they add. The plan is in Moving to STLabs from your current service desk.

A new hire is fully set up when the rule that set them up will still be right after their first move.

Frequently asked questions

What tools do you need to automate new hire onboarding?

An HR system as the trigger, an identity provider, device management, and access rules over live HR attributes. STLabs applies those rules with an AI agent on day one and on every role change.

Why does new hire access drift after onboarding?

Most onboarding grants access once from a template. When the person changes team, manager or project, nothing re-applies it, so they keep access from the old role and wait for what the new one needs.

What is joiner-mover-leaver automation?

Automating access across a person's employment: granting it when they join, adjusting it when they change roles and removing it when they leave. STLabs includes it in Access Lifecycle, on the Growth plan and up.

Can ITSM tools handle onboarding on their own?

They can track the onboarding request well, with tasks and approvals. Keeping access right after the hire moves teams needs rules over live HR attributes that run again whenever those attributes change.

See it on your tools.