Use casepeople ops & IT

Onboarding that doesn't need a checklist channel.

A new hire touches nine systems before lunch: HRIS, email, Slack, the wiki, the CRM, the password manager, the standup doc. Someone owns that checklist, and it's never their actual job. An agent runs it end to end — and every access grant still gets a human yes.

// the manual version

You know this week already.

Nine tabs per hire

The checklist lives in a doc, the doc lives in a folder, and the folder lives in the head of whoever ran it last quarter.

Day-one embarrassment

The new hire has a laptop but no Slack, or Slack but no calendar. Every miss is small; together they say 'we weren't ready for you.'

Offboarding is scarier

Onboarding misses are awkward. Offboarding misses — the contractor whose access outlived the contract — are audit findings.

// describe it

The whole build is a brief.

No canvas, no nodes. You write instructions the way you'd brief a teammate; the lines marked with a shield pause for a human before anything irreversible happens.

Example brief — illustrative, write yours in your own words

·When a new hire is marked 'starting' in the HRIS, begin day-minus-3 prep.

·Create their email and add them to the team calendar and standup invite.

·Draft the Slack/wiki/CRM access requests from their role's template.

Before granting any system access, wait for their manager's approval.

·Send the welcome packet and schedule the day-one check-in.

On departure: propose the reverse list, and wait for IT sign-off before revoking anything.

·Post a completion summary with anything still pending to #people-ops.

// how it runs

Autonomous on the routine. Supervised on the rest.

What starts it

An HRIS event — a hire marked 'starting' or 'departing' kicks off the run.
A form your recruiters fill when the HRIS lags reality.
A schedule that re-checks pending items daily until the list is done.

What waits for a human

Every access grant — the manager approves before any system lets the hire in.
Every revocation on offboarding — IT signs off before anything is cut.
Anything outside the role template — new tool, elevated permission, exception.

What the trace keeps

Which systems were touched for which hire, step by step.
Who approved each grant and each revocation, with timestamps.
The record your next access review asks for, already written.

// common questions

Can the agent grant access by itself?

No — access grants and revocations are gated by design. The agent prepares the request, routes it to the right approver, and executes only after the yes. That's the core of the product, not a configuration you have to remember.

What about tools you don't integrate with?

The catalog covers 1,284 tools; internal systems can connect via OpenAPI. For anything unreachable, the agent tracks it as a manual step and keeps it on the pending list instead of silently dropping it.

Does it handle offboarding too?

Yes — same agent, reverse direction, stricter gates. The agent proposes the full revocation list and waits for IT sign-off, so nothing is cut by surprise and nothing is forgotten.

How do role templates work?

They're part of the brief: 'engineers get GitHub and the on-call calendar, sales gets the CRM and the deal room.' Plain language, versioned like everything else, so changing the template is a diff you can review.

Hand off the employee onboarding.

Join the waitlist and describe it in a sentence — or ask about white glove and our team will build and run it with you.

Early access · we'll email when your workspace is ready