How changes save: the ticket defaults save as soon as you change them. Each step opens a modal with its own Save button. There is no global confirmation at the bottom of the page.
Ticket information
Applied to every onboarding ticket Primo opens.Onboarding tasks
The steps are scheduled from the employee’s start date and listed in the order the ticket creates them:
Provision SaaS accounts appears only when SaaS Management is enabled on your account.
Step chips
Each row shows how the next onboarding will handle the step:Controls every step shares
Click a row to open its modal:- Include this step in onboarding — off means no task is created and the row reads Skip. Confirm onboarding information is always included.
- Autonomy — Automatic (Primo runs the step) or Manual (a person does, Primo only opens the task).
- Default assignee — the admin who owns the task and answers when Primo needs a decision on this step.
- Scheduling — a day relative to the start date (from One month before to One month after, including The D-day) and a time, in 30-minute steps. In Automatic, it is when Primo runs the task. In Manual, it is the default date offered when you run the step from the ticket.
- Due date — in Manual only, how many days before the start date the task is due, from 1 to 60.
A step with no scheduling set runs one week before the start date at 09:00. When an onboarding is created after that date has passed, an automatic step runs right away.
The onboarding ticket
Every onboarding is backed by a ticket titled First Last - Onboarding. It takes its assignee, priority, and subscribers from Ticket information, its due date from the start date, the Onboarding tag, and the new hire as requester. Related items, such as equipment orders, link to it. Find it on the employee profile, Tickets tab, or in the Tickets list filtered on the Onboarding tag.Tasks on the ticket
Each included step creates one task. Tasks are grouped as Manual (waiting on a person), Scheduled (Scheduled for 28 Jun), Done, and Cancelled. A pending task that isn’t scheduled shows its due date, as Due 28 Jun. SaaS provisioning adds one task per app: Provision runs on its scheduled date, and Create account for on waits for you to create the account. Expand a per-app row to see the email, roles, licences, groups, and organization units it provisions. Work a task from its row:- Configure — opens the matching step. Completing the step marks the task done.
- Mark as done (✓) — for SaaS accounts you create yourself and your own manual tasks. Onboarding steps follow what happened in the step instead.
- ⋯ — view details, view logs, edit details, or cancel the task.
Skip a step or cancel the onboarding
- Skip a step — cancel its task from the task menu. Cancelling a task and skipping its step are the same action.
- Cancel the onboarding — available while the onboarding is still To-do. It cancels the ticket and its pending tasks; completed tasks stay for history.
Ticket status
The onboarding drives the status: To-do when created, In progress once a task is completed, Done when the last task is, and Cancelled when you cancel the onboarding.What replaced the legacy settings
The single settings form — one page of steps saved by a global Confirm button — is deprecated. Per-step configuration replaces it:MDM enrollment is not part of the new page. Invites keep following the setting saved on your account: Primo sends an enrollment invitation to new employees and resends it every 7 days until the agent is installed. For day-one setup without manual steps, combine it with zero-touch deployment: see Zero Touch for Mac or Zero Touch for Windows.
The new settings page ships with onboarding as tickets and is rolling out to accounts. If Employees > Settings still shows one long form with a Confirm button at the bottom, your organization is on the legacy page — contact your Primo representative.