Origin
Origin for People Ops
A policy-aware employee service agent that answers, coordinates, and completes work across HR and IT.
Eight-agent operating model
One request, eight bounded specialists, one verified result
Select each agent to inspect its work, evidence, control, and handoff in a realistic People Ops example. No specialist receives standing authority over the full outcome.
Workflow · People Ops
Eight specialists, one governed outcome
Example request
Complete a governed internal team transfer
“Move Priya to the Platform team next Monday, update her manager and cost center, add the standard engineering access bundle, and remove access she no longer needs.”
Request context
Current manager · India · effective Monday
Select an agent
Agent 01 of 08
Intake agent
Reads the manager request, identifies the effective date, and separates the worker change from the downstream tasks.
- Evidence produced
- Structured transfer case
- Control enforced
- Required fields + manager attestation
Governed handoff
Passes the normalized case to Identity. The request, evidence, policy decision, and version stay attached; the next agent receives no broader authority.
End-to-end progress
1 / 8Target outcome
A policy-valid worker change, approved access diff, coordinated HR and IT tasks, employee confirmation, and one auditable case.
Verified result
HRIS change scheduled; manager approved; new access time-bound; obsolete entitlements queued for removal; employee and owners notified.
Systems kept authoritative
- Workday
- Oracle Cloud HCM
- Okta
- Slack
- SharePoint
Priority use cases
Start with high volume, a clear owner, and explicit policy. Expand once the outcome, controls, and audit trail are proven.
- Policy, leave, benefits, and payroll answers grounded in approved sources
- Joiner, mover, and leaver orchestration across HRIS, identity, devices, and access
- Employee and manager case intake with routing, status, and specialist handoff
- Approvals and sensitive people workflows with regional policy controls
- One compliant record of the request, citations, decisions, actions, and closure
End-user surface and control systems
Employees meet Origin in Slack, Teams, chat, or voice. Developers can work from Git, delivery tools, and engineering channels. Operators keep ITSM, HRIS, IAM, cloud, repositories, pipelines, and cost platforms authoritative. Origin preserves one trail from request through approval, execution, verification, and rollback.
Operating model: before and after
Before
Employees email HR for policy answers, payroll questions, onboarding status, and job changes. Managers chase checklists across HRIS, identity, devices, payroll, and IT.
With Origin
Origin answers with citations, coordinates HR and technology tasks, applies regional policy and approvals, nudges owners, and keeps one employee-facing case from request to verified closure.