One new hire. Three processes. One connected journey.

Priya Sharma's name anchors all three cases in the Woodgrove Life workspace — Hiring, Onboarding, and IT Access. Each is a real, independent case, created and connected automatically as her journey progresses.

Filtering the case list to Priya shows her whole journey at a glance: one candidate, one cohesive experience, three coordinated processes working together.

Priya's hiring case: every step complete. Her manager, Elena Vasquez, personally approved five key decisions along the way. The decline path was never needed — Priya qualified.

An AI assistant reviewed Priya's resume and assessed her as qualified — but the decision didn't proceed on AI alone. It waited for Elena Vasquez to review and approve. People stay in control of the decisions that matter.

Elena Vasquez signed in as Hiring Manager and approved the interview outcome — one of five points in the hiring case where a real person made the call.

The final step of hiring securely notified the onboarding process and created Priya's onboarding case — no copy-paste, no manual re-entry. Her details carried forward on their own.

The Offer Accepted approval — Elena's last sign-off in hiring. Once it was complete, Priya's onboarding case opened automatically.

Priya's onboarding case: complete. Every step ran — HR data review, access planning, manager approval, equipment setup, access provisioning, the onboarding package, and the handoff to IT.

Elena Vasquez approved the onboarding plan — the same manager who guided Priya's hiring. One person, accountable across both cases. She made the call from Microsoft Teams, replying to the request without leaving the app she already works in — shown below.

The final onboarding step securely notified IT and created Priya's access case. Her details — name, role, department, and assigned device — carried forward automatically.

Behind the scenes, the onboarding case passed Priya's details straight into the access case — department, role, employee ID, and device. No one re-typed anything; the system carried the data forward.

Woodgrove decides which channels are allowed to act on a case. Approving by replying to a message is an explicit, per-workspace choice: here, email and Microsoft Teams are both switched on, and WhatsApp runs on the very same pipeline whenever they want it — the same approval, from wherever the approver already works.

Elena received the approval request as a Microsoft Teams message and simply replied — no app login required. The case keeps the exchange on the record exactly as it happened: the request went out over Teams, she replied APPROVE, and her confirming reply moved the gate — closing Manager Approval and releasing IT access provisioning. Her reply is a real Teams message delivered through the live bot: confirming who sent it, reading the approval, and advancing the case are all the product's own logic — running here, for real. The record also shows an earlier reply the system didn't recognize: it changed nothing, said so on the record, and waited — a message is never guessed into an action.

This is the manager's own view. The Regisseur bot direct-messaged Elena the assignment; she replied APPROVE; the bot confirmed exactly what would happen — complete Manager Approval and unlock Equipment Setup — and asked her to confirm; she replied YES; the bot answered "Done." A real Teams conversation moved a real case forward — no app to open, and a confirmation step before anything executed.

Priya's IT access case: complete. Request intake → entitlement planning → IT Security approval (Marcus Webb) → provisioning → access confirmed.

A different approver, by design. Marcus Webb, IT Security Manager, approved Priya's privileged access — separate from her hiring manager. Sensitive system access requires IT Security sign-off, not just a manager's.

After Marcus Webb's approval, the provisioning step recorded Priya's granted access — her primary grant (the Underwriting Workbench) and who approved it. In this walkthrough the grant is recorded in Regisseur as the system of record; connecting to a live identity provider is a configuration step.

The complete record of what Priya was granted: the approver, the status, the systems she can use including the privileged Underwriting Workbench, and her security groups — all captured as one clear, auditable record.

The final Access Confirmed step completed the moment provisioning finished, and the case closed itself. Each process in the journey wraps up on its own once its work is done.

The operations dashboard reflects all three completed cases — real cycle times, automation rate, and cost, measured from the actual runs.

The worklist is clear — every human approval in Priya's journey has been completed by Elena Vasquez and Marcus Webb. The journey is fully resolved.

All three cases at rest in the Woodgrove Life workspace, every one completed. Priya Sharma is hired, onboarded, and has the system access she needs to start work.

Open any case and the Related Cases panel shows the whole journey — Hiring → Onboarding → Access — each one a real, linked case you can click straight through to. The connections aren't buried in the data; the product shows you how one step led to the next.