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

# September

> Product updates from September 2026

<Update label="September 29, 2026" tags={["Device Management"]}>
  ## Enroll iPhones and iPads with a QR code

  Employees enroll an iPhone or iPad by scanning a QR code and signing in with their work account, and the device is assigned to them. Turn on **Require IdP authentication** in **MDM > Settings** first, or the devices enroll without an owner.

  See [Employee enrollment](/mdm/rollout/invite-employees#enroll-iphones-and-ipads).
</Update>

<Update label="September 25, 2026" tags={["Helpdesk", "AI"]}>
  ## Helpdesk Agent

  Add Primo AI to a ticket and it works the request your employee raised by email, from Slack, from Microsoft Teams or from their employee space, replying in the same thread. It handles the common requests: where's my order, access to a SaaS, a forgotten email password, a hardware renewal. Ordering a device or provisioning a SaaS seat waits for approval from the employee's manager, or the ticket's assignee when there's no manager. When it can't help, it leaves an internal note with what it checked and creates a task for your team on the same ticket.

  Letting Primo AI pick up every ticket your employees raise is rolling out to accounts. See [Helpdesk Agent](/tickets/helpdesk-agent).
</Update>

<Update label="September 22, 2026" tags={["Onboarding", "AI"]}>
  ## Every onboarding gets its own ticket

  Each onboarding now opens one ticket with a task per included step: information, mailbox, SaaS accounts and equipment. Each task has an owner, so you can see who still has to act. Set a step to **Automatic** and Primo runs it for you. It creates the mailbox when a new address is needed, provisions your connected SaaS and gives owners of manually tracked SaaS a task.

  Automating onboardings requires a connected HR system. See [The onboarding ticket](/employees/onboarding-settings#the-onboarding-ticket) and [Automate your onboardings](/employees/automate-onboardings).

  ## Equipment Agent

  Publish your **Equipment policy** and **Purchasing policy**, written in plain language, then set the **Purchase equipment** step to **Automatic**. Primo AI runs that step on each onboarding. It checks your stock first, then the catalog, emails the new hire one proposal, and asks the step owner to approve before anything is ordered or assigned. Your policies set the rest: who signs off, where it ships, which billing profile pays and when equipment work starts.

  The **Automatic** option is rolling out to accounts. See [Equipment Agent](/employees/purchase-equipment-at-onboarding).
</Update>

<Update label="September 18, 2026" tags={["Device Management", "AI"]}>
  ## MDM Remediation Agent

  For the compliance statuses you set to **Create Issue and Ticket** (FileVault or BitLocker off, an OS update past its deadline, the EDR agent not running), each drifting device gets a ticket that Primo AI works. It re-applies the fix, checks on the device that it worked, and the ticket closes once the device reports compliant. When only your team can go further, an offline device for example, it hands the ticket back with its diagnosis. If the employee has to act, a restart for example, Primo AI tells them once, in their language. It never locks, wipes, retires or unenrolls a device on its own: your policy has to explicitly allow it, and an admin has to ask in an internal note. Every action it takes on a device is recorded in the audit logs.

  Turn it on by publishing your **AI Remediation** policy in **Compliance > Compliance issue settings**. See [MDM Remediation Agent](/mdm/compliance/ai-remediation).

  ## Enter your Windows zero-touch values yourself

  Paste your **Entra Tenant ID**, **Entra application (client) ID** and **Domain** into the cockpit yourself instead of sending them to support. If you set up Windows zero-touch before, a banner reminds you: until the three values are saved, Windows zero-touch isn't fully operational. Only the domain verification code still goes through support.

  See [Zero-touch for Windows](/mdm/zero-touch/zero-touch-windows).
</Update>

<Update label="September 17, 2026" tags={["Platform", "AI", "Device Management"]}>
  ## Custom fields that fill themselves

  Write a one-sentence instruction on a custom field, like "Return the cost center matching the owner's team", turn on **Enable AI auto-fill**, and Primo AI fills it on each new record the field applies to. Run it once on existing records to fill the gaps. Each value shows whether it came from AI or was typed by hand. Values are written once: when your data changes, run **Refresh values with AI** with **Replace values that already exist** on, which also overwrites values typed by hand.

  Custom fields are in beta and rolling out to accounts. See [Custom fields](/mdm/custom-fields#fill-fields-automatically-with-ai).

  ## Fewer compliance issues that don't need you

  Exempt unassigned and in-stock devices, so the spare laptops in your cupboard stop raising issues and tickets. You can also set a grace period of 1, 3, 7, 14, 21 or 30 days for statuses that are still being applied, like a configuration on its way to the device. Real violations, such as an unencrypted disk, still raise their issue as configured.

  See [Configure compliance issue settings](/mdm/compliance/issue-settings).
</Update>

<Update label="September 14, 2026" tags={["Platform"]}>
  ## A new look, with dark mode

  Primo has a new theme across the app, with clearer type and contrast. Pick **System**, **Light** or **Dark** from your menu; System follows your computer's setting.
</Update>


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