Enterprise use case · ADP Workforce Now + Okta + Microsoft 365
ADP recruitment to employee access
Hiring completes in ADP but access is requested separately and arrives late. Accepted applicants and work assignments in ADP lead to approved access on day one.
Systems involved
What each system contributes
13 actions
- Job Applicants3
- Work Assignment7
- Time3
42 actions
- User Management14
- Groups12
- Roles11
Architecture
One governed run
How it starts: A schedule or HTTP poll reads ADP. ADP Workforce Now has no trigger source.
Step by step
How the process runs
- 01
Applicant
ADP job applicant and work assignment records are read.
- 02
Policy
Rules + Code maps the assignment to Okta groups and roles.
- 03
Approval
The hiring manager approves.
- 04
Access
Okta user, groups and roles are applied. Teams, email and calendar setup follows.
Control
Human decision and exception path
Human decision
The hiring manager approves access. Privileged roles need IT security approval.
Exception path
- Assignments without a start date wait.
- Duplicate identities are blocked.
- Okta errors are retried.
Evidence
What gets audited
- Applicant and assignment.
- Policy result.
- Approvals.
- Okta and Microsoft 365 changes.
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.
- ADP Workforce Now connector
13 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.
- Order to cash across CRM, ERP and billing
Another enterprise 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 schedule or HTTP poll reads ADP. ADP Workforce Now has no trigger source.
- 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.