People triggers

People triggers start automations from employee lifecycle dates. They’re ideal for orchestrating onboarding/off boarding and scheduled employee touch points without opening a request first.

Available triggers

• Start date

• End date

• Work anniversary

• Birthday

• Probation period

When to use

• Onboarding: coordinate tasks across IT, HR, Facilities on the employee’s start date.

• Off boarding: revoke access, collect equipment, and notify stakeholders on end date.

• Check‑ins: probation reminders to manager and HR.

• Recognition: send automated anniversary or birthday messages.

Conditions you can add

• People attributes: department, location, manager, employment type (employee/contractor), legal entity, job title/level.

• Groups: teams and custom groups you defined.

• App/device context: whether the person owns certain apps or equipment.

Common workflows

• Day‑1 onboarding

  • Trigger: Start date

  • Conditions: Department = Engineering, Location = London

  • Actions: Okta “Add to groups,” create Jira/Linear tasks, send welcome kit email, notify hiring manager

• Off boarding

  • Trigger: End date

  • Conditions: Employment type = Employee

  • Actions: Revoke sessions, remove app access, create pickup request for equipment, DM manager with completion summary

• Probation review

  • Trigger: Probation period

  • Conditions: Department = Sales

  • Actions: Send checklist to manager, open a request if feedback is missing after 3 days

• Celebrations

  • Trigger: Work anniversary

  • Actions: Post a message in #all‑hands and DM the manager with a recognition template

Best practices

• Keep sensitive steps (de-provision, wipe) behind approvals for contractors if needed.

• Use categories (HR, Security) and roles to restrict who can edit these flows.

• Add “owner” chips to actions that hit external systems for clear accountability.