Healthcare use case · Workday + Okta + Microsoft 365
Healthcare employee onboarding
Staff wait for accounts on day one while requests move between HR and IT. New staff get the identity access and collaboration their role needs, after approval.
Architecture
One governed run
How it starts: A webhook, schedule or HTTP poll of Workday starts the run.
Step by step
How the process runs
- 01
Context
The new hire is read from Workday.
- 02
Policy
Role maps to identity groups.
- 03
Approval
Elevated access waits for the access owner.
- 04
Provision
Okta user and groups are created.
- 05
Welcome
Teams, email and induction calendar invites follow.
Control
Human decision and exception path
Human decision
Access beyond the role baseline needs the access owner's approval.
Exception path
- Missing data routes to HR.
- Okta errors are retried.
- Start date changes reschedule the run.
Evidence
What gets audited
- HR context.
- Policy result.
- Approval.
- Okta and Microsoft 365 operations.
Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- Workday-Okta integration
Integration pattern · Employee lifecycle changes become governed identity and access changes.
- Microsoft 365-Okta integration
Integration pattern · Identity changes and collaboration follow-up happen together, under policy.
- Workday connector
66 pre-built actions
- Okta connector
42 pre-built actions
- Microsoft 365 connector
45 pre-built actions
- Governed self-service
Requests with policy and approval built in.
- Appointment administration and service follow-up
Another healthcare use case.
FAQ
Questions about this use case
- Does Nexus replace any of these systems?
- No. Each system keeps its own records. Nexus runs the process between them and records each decision.
- How does the run start?
- A webhook, schedule or HTTP poll of Workday starts the run.
- What if a step is not covered by a pre-built action?
- It runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.