> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getprimo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand onboarding settings

> A tour of the Onboarding tab in Employees > Settings: the ticket defaults applied to every onboarding, the steps each onboarding runs, and the controls every step shares.

Onboarding settings decide how Primo handles every new hire: when the onboarding ticket opens, who owns it, and which steps run on it. Go to **Employees > Settings** and open the **Onboarding** tab.

The page has two sections: **Ticket information**, applied to every onboarding ticket, and **Onboarding tasks**, the steps that run on it. To configure each step, see [Automate your onboardings](/employees/automate-onboardings).

<Info>
  **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.
</Info>

## Ticket information

Applied to every onboarding ticket Primo opens.

| Setting | What it does |
| - | - |
| **Create onboarding ticket** | Decides how and when the ticket opens. Every onboarding starts with this ticket, so the step is always on. See [Automate your onboardings](/employees/automate-onboardings). |
| **Default Assignee** | Owns the ticket, unless a rule reassigns it. |
| **Add Primo AI as agent** | Adds Primo AI as an agent on every onboarding ticket. It assists the owner: tracks progress, gives hints, and sends reminders. It never owns the ticket. |
| **Default priority** | The priority the ticket starts with: **Low**, **Medium**, or **High**. |
| **Default subscribers** | Admins who follow every update without being assigned. |

## Onboarding tasks

The steps are scheduled from the employee's start date and listed in the order the ticket creates them:

| Step | What it does |
| - | - |
| **Confirm onboarding information** | Checks what the HR system sent, asks for what is missing, and gets the professional address confirmed |
| **Provision email** | Creates the professional email on your identity provider and delivers the credentials to the recipient you chose |
| **Provision SaaS accounts** | Provisions connected SaaS automatically, and gives the owners of manually tracked SaaS a task |
| **Purchase equipment** | Proposes a device from the Equipment policy, agrees it with the new hire, and orders it |

**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:

| Chip | Meaning |
| - | - |
| **Automatic** | Primo runs the step on its scheduled date. |
| **Manual** | A person runs the step. Primo only opens the task. |
| **Primo AI** | Primo AI runs the step end to end. Shown on **Purchase equipment**. |
| **Skip** | The step is excluded, or it can't run yet. No task is created. |

### 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.

<Note>
  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.
</Note>

## 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 SaaS: **Provision {app}** runs on its scheduled date, and **Create account for {employee} on {app}** waits for you to create the account. Expand a per-SaaS 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.

## Related articles

* [Automate your onboardings](/employees/automate-onboardings)
* [Set up HR Sync](/employees/set-up-hr-sync)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.