Skip to main content
Prerequisite: Automating onboardings requires your HR system to be connected so that Primo can detect upcoming arrivals and their start dates. See Set up HR Sync.
Once configured, onboardings are triggered automatically based on contract start dates. Each step below corresponds to a configuration step in Settings > Onboardings.

Step 1 — Employee information

Configure how employee profiles are created in Primo. Processing options:
  • Manually — employee profiles are created manually by an admin.
  • Automatically process ✦ Recommended — Primo automatically creates employee profiles from their HR data as soon as they appear in the sync.

Step 2 — Email address

This step requires Google Workspace or Microsoft Entra to be connected, and the email provider toggle to be turned on. See Connect your email provider.
Configure how work email addresses are created for new employees.

Email creation

Choose whether Primo should create the work email address:
  • Create with Primo — Primo creates the email address in your connected provider (Google Workspace or Entra). If an email with the same address already exists, Primo will not create a duplicate.
  • Do not create — email creation is handled outside of Primo.

Password delivery

Choose who receives the employee’s initial password:
  • Send to manager — the manager defined on the employee profile receives the password.
  • Send to an admin — a designated Primo administrator receives the password.
  • Send to employee — the new employee receives the password directly.

Scheduling

Choose how many days before the onboarding date email addresses should be created. Default: one week before at 07:00.

Processing options

  • Manually — email accounts are created manually by an admin.
  • Automatically process ✦ Recommended — Primo automatically creates email accounts for employees with upcoming onboarding dates based on the schedule above.
  • Automatically skip — email creation is skipped entirely for all onboardings.

Step 3 — SaaS provisioning

Configure how SaaS application access is granted at onboarding.

Scheduling

Choose how many days before the onboarding date accounts should be provisioned. Default: one day before at 18:00.

AI suggestions

When enabled, Primo uses AI to suggest the right SaaS applications, groups, roles, and licences for each new employee based on their role, team, and manager.

Processing options

  • Manually — SaaS provisioning is handled manually by an admin.
  • Automatically process ✦ Recommended — Primo automatically provisions onboarding employees in connected SaaS applications based on the schedule and rules above.
  • Automatically skip — SaaS provisioning is skipped entirely for all onboardings.

Step 4 — Equipment

Configure when equipment is ordered for, or assigned to, new employees.
Coming soon: Automatic equipment ordering is on the roadmap. Today, equipment assignment must be handled manually or skipped.
Processing options:
  • Manually — equipment is assigned manually by an admin.
  • Automatically skip — the equipment step is skipped entirely for all onboardings.

Step 5 — MDM enrollment

Configure whether employees are automatically enrolled in MDM at onboarding. Enroll employees in MDM invites — when enabled, Primo automatically sends an MDM enrollment invitation to new employees on their onboarding date. Primo will resend the invitation every 7 days until the agent is installed.
For zero-friction day-one setup, combine MDM enrollment with Zero Touch Deployment — devices arrive pre-enrolled and ready to use. See Zero Touch for Mac or Zero Touch for Windows.

Step 6 — Custom AI agents

Coming soon — Build custom AI agents that run at onboarding — automatically send a welcome Slack message, create a Notion onboarding page, open a Jira ticket, or trigger any workflow in your stack.