Enterprise use case · Personio + Okta + Microsoft 365
Personio onboarding and attendance workflow
Access changes and attendance exceptions are handled by email between HR and IT. Personio records drive approved access and attendance follow-up with exceptions recorded.
Architecture
One governed run
How it starts: A schedule or HTTP poll reads Personio. Personio has no trigger source.
Step by step
How the process runs
- 01
Person
Personio persons, attendances and documents are read.
- 02
Policy
Rules + Code decides access for new starters and flags attendance outside policy.
- 03
Act
Approved access is applied in Okta. Attendance follow-up goes to managers in Teams or email.
- 04
Exceptions
Missing documents hold access until HR confirms.
Control
Human decision and exception path
Human decision
Managers approve access. HR approves any exception to attendance policy.
Exception path
- Missing documents pause onboarding.
- Unknown roles route to IT.
- API errors are retried.
Evidence
What gets audited
- Person record.
- Policy decisions.
- Approvals.
- Okta changes and notifications.
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.
- Personio connector
12 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 Personio. Personio 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.