Clearer tables
Tables now use color only for what needs your action, so the rest stays in the background. Rows take less height, with fewer icons and plainer chips. Each chip is a Primo object, such as a device, an employee, an order, an MDM control or a ticket: click it to open it. Tooltips on hover give you the information without leaving the page. Dates and times read the same everywhere, pagination stays pinned to the bottom, and a row’s actions sit in its … menu. The compact view option is gone, as you no longer need it.Update or delete up to 25 tickets at once
In Helpdesk > Tickets, check up to 25 tickets on the current page. In the bar that appears, pick Status, Priority, Assign, Add tag, Remove tag or Delete. A message says how many tickets changed and how many couldn’t. Your selection stays, so you can apply a second action. Deleting tickets also deletes their tasks and closes any linked onboarding without running its open steps. You can’t undo it. You need the Manage all tickets or Manage my tickets permission.See Act on several tickets at once.Find the SaaS that still need a provisioning rule
A SaaS without a published rule gets no account preselected at onboarding, and Primo flags nothing on it. To list them, go to SaaS > Directory and filter by Rules > Unpublished, or add the Rules column from the columns picker. A rule with pending changes counts as Published. A SaaS with a draft only, or no rule, counts as Unpublished. The CSV export follows the same filter.See Open the rule of a SaaS.Stop your HR sync from adding guests and partners
Your HR system can list people who aren’t part of your workforce, such as guests or partners. In Settings > HR System > Settings, click Company domains only. Under HRIS connections, turn it on for each connection it applies to. The toggle stays disabled until your company has at least one domain. Primo then creates no employee and no onboarding for a new person whose email addresses are all outside your company domains. People already in Primo keep syncing.See Skip people outside your company domains.Set the start date when you add a new hire by hand
While the Onboarding Agent is enabled, the Add an employee form now asks for an Onboarding date, the new hire’s start date. The field is required. If Anything else mentions another date, the one you pick wins. Open the form from Onboard in the left menu, Add on the Employees and Onboardings pages, or Create onboarding in the command menu. Then click Create onboarding: Primo AI creates the onboarding, and the agent takes it from there. You need the Manage all employees permission.See Add a new hire by hand.Paste a custom profile instead of uploading a file
Add a profile you copied as text without saving it to a file first. In a Custom file control on macOS, iOS or iPadOS, select Paste content. Paste the XML of a configuration profile or the JSON of a DDM declaration into Profile content. Once the content is valid, the cockpit shows its type and the file name it saves it under. A signed profile can’t be pasted: upload its.mobileconfig file instead. When you edit the control, Paste content opens empty, so paste the whole profile.See Custom file.Employees can install a missing Mac agent themselves
After a Mac enrolls, the Primo agent installs on its own. When it doesn’t, employees can install it themselves. Until now, only IT admins could download the agent package. On the enrollment page, they click the chevron on the macOS row, then Download .pkg under Agent package, and open the file. Installing it needs administrator rights on the Mac. The enrollment profile stays the main download. Under All installers in MDM > Settings, the package now sits under the same chevron instead of on its own row.See Employee guide & FAQ and All installers.Always allow a tool from the Primo AI chat
When Primo AI asks before it runs an action in the chat, you can now click Always allow instead of Accept. It runs the action and sets the tool to Always allow in its connector’s Chat permissions, for everyone in your company. Primo AI stops asking about that tool in the chat. Agents keep their own permissions. The button shows only if you have the Manage AI agents permission. To get the question back, set the tool to Require approval on the connector’s page.See Approve actions and Set tool permissions.Distribute your private Android apps
Deploy an internal app that isn’t on the public Google Play Store. In MDM > Software, click Add app, then Google Play, to find your Enterprise ID. Publish the app privately in the Google Play Console with that ID as the organization ID. Then enter its package name in the Add Android app window. Until the next sync, the preview shows the package name, not the app’s name, so check it: a typo makes adding the app fail. Employees install it from the managed Google Play store on their device.See Add a private app.Resend a control’s profile to a device
When a control showsERROR on a device, check the control, then resend its profile from the cockpit. Until now, it took the API, the MCP server or Primo AI. Open the device drawer and, in its MDM Controls section, click Resend profile on the control’s row. The device installs the profile at its next check-in, and an iPhone or iPad once it’s unlocked. You can’t resend a declaration, a control that isn’t delivered by a profile or isn’t assigned to this device, or a profile still being delivered.See Why a configuration fails to apply.Dictate instead of typing in Primo AI and ticket comments
Click the microphone next to the send button and speak. Your words appear in the message as you talk. While you dictate, you can’t edit or send the message: stop dictating, check the text, then send it. It works in the Primo AI chat, in the side panel and full screen, and in a ticket’s comment box. The microphone doesn’t show when your browser can’t record audio.Create the mailbox as soon as the onboarding exists
When a new hire needs their work address well before day one, create it right away. In the Provision email step, set Scheduling to On onboarding creation instead of a day relative to the start date. The time field disappears. In Automatic, the email task starts when the onboarding ticket opens, even if the onboarding has no start date yet.See Provision email.Hires who started over 7 days ago now skip onboarding by default
Onboardings for past start dates now defaults to Within 7 days, instead of Always, for every company. When your HR system adds someone whose start date passed more than 7 days before the sync, Primo creates them as an active employee. They get no onboarding. Onboardings already created stay: narrowing the window never removes one. To get an onboarding for everyone your HR system adds, as before, pick Always in Settings > HR System > Settings. Primo saves it and syncs right away.See Handle past start and leave dates.See why an HR connection is stuck, and reconnect it
When a connection under Connections in Settings > HR System needs attention, its status now says why. Reconnection needed means your HR system no longer accepts the connection’s credentials. Click Reconnect and follow the authentication steps. If someone else manages your HR system, send them the link from Copy the reconnection link in the connection’s … menu. They don’t need a Primo account. The status updates after the next sync. For Setup to finish, click Finish setup.See Manage a connection.Connect your own ThreatDown tenant
If your company already runs ThreatDown on its own Nebula tenant, connect it to Primo yourself. Go to MDM > Settings, click Add integration, then Connect on the Threatdown card. Enter your Account ID, Client ID and Client secret. Primo checks them before it saves anything, and shows the reason when a check fails. Then deploy the agent with the EDR - ThreatDown control in MDM > Controls.See Connect your ThreatDown tenant.Choose how far back HR sync opens onboardings and offboardings
Your HR system can add a hire after their start date, or report a departure after the leave date. Two settings in Settings > HR System > Settings decide what Primo does: Onboardings for past start dates and Offboardings for past leave dates. Each takes a window from Within 7 days to Within a year, plus Always for onboardings and Never for offboardings. Hires who started before the window become active employees, without an onboarding. With Never, the default, Primo only offboards employees whose leave date hasn’t passed yet.See Handle past start and leave dates.Send a setup link to whoever manages your HR system
When someone else manages your HR system, let them connect it to Primo. Go to Settings > HR System, click Connect an HRIS, then click the copy icon on your provider’s tile and send them the setup link. They don’t need a Primo account, and the link stays valid for one year. Each connection under Connections shows its last sync, its number of employees and its status.See Connect your HR system.Change the billing profile of an order
If an order went to the wrong billing profile, you can now change it until the order is invoiced. Open the order, click Change the billing profile in the Billing profile card, select another profile, then click Save. The invoice is issued to the new profile. You can’t select a profile that has no payment method able to pay an order.See Change the billing profile.Custom AI dashboards
The Dashboard page now holds AI dashboards next to Classic, the dashboard you know. Each one opens on a digest of what needs you first, then links you to the devices, tickets or apps concerned. Start with Today, or click + next to the tabs, name a dashboard and describe what it should show, for example “Security first: compliance issues, unencrypted devices and late updates.” Primo composes it from your company’s data and keeps it up to date.
Onboarding Agent
Hand each new hire’s onboarding to Primo AI. Describe your onboarding in your own words: steps, owners, timing, reminders. For every new hire, the agent opens one ticket and creates its tasks. By default, it orders within your published Equipment and Purchasing policies without waiting for approval, stock first. It emails a remote new hire to confirm their home address, and they need no Primo account. With a connected email provider, it creates the mailbox and the SaaS accounts your published provisioning rules cover. Anything else, like an order outside a policy, becomes a task for a person you named. It doesn’t configure devices.
One provisioning rule per SaaS
Each SaaS now has its own provisioning rule in plain words: who gets an account, with which groups, roles, licences, and organizational units. Primo moved your previous rules for you, and each SaaS kept the part that covered it. Open a rule from the Settings tab of the SaaS, preview its effect, then publish. Primo AI can write a first rule from the accounts already in place. Accounts that don’t match the published rule show in SaaS > Issues.See Set up provisioning rules.Pin a view on any page
Choose the view a page opens on for your whole company. Open a view on Devices, Employees, Tickets or any other page with table views, then click Pin in its view menu. The pinned view moves to the leftmost tab, and the page opens on it for everyone in your company. Each page has one pinned view. Only cockpit admins can pin a view.
Release a Mac from Apple Business before you sell or return it
Once released, a Mac no longer enrolls in Primo automatically after a wipe or a reinstall. On a Mac enrolled through zero-touch deployment, click Actions > Release from ABM, then Release. You can also check I want Primo to release this device from my ABM when you unenroll it. If Apple Business refuses the release, the Mac stays enrolled. In Apple Business, turn on Allow this MDM server to release devices for Primo. Only Apple or your reseller can add a released Mac back to Apple Business.See Release a Mac from Apple Business.Create new hires’ addresses on several email providers
You can now set several SaaS instances as email providers, such as one Google Workspace or Microsoft Entra tenant per entity. Turn it on from the Settings tab of each instance. With Provision email set to Automatic, under Create addresses automatically on, select the providers where Primo creates each new hire’s address. An admin creates the others from the onboarding. In an onboarding’s email step, Select email provider lists each provider with its domain. Each one opens on the new hire’s address there, or on a suggested one. Each provider you check needs an address before the step can continue.See Provision email and Connect several instances of the same SaaS.Get reminded when an onboarding step is due
The morning reminder email now lists onboarding steps that are coming due or overdue, so a late step reaches its assignee. A step gets reminders when it has a Due date, which you set on steps in Manual. The schedule is also shorter, for every ticket and task. An item shows up 2 days before its due date and on the due date. Once overdue, it shows up on each of the next 3 days, then stops. You can’t turn these reminders off yet.See Get reminders for due tickets and tasks and Understand onboarding settings.Test a custom agent before it runs on its own
Open a custom agent and click Dry run to try it on your real data without changing anything. Every email, ticket, comment or device action it would make is recorded instead, and the run shows What it would have done. When the result looks right, click Run now to run it for real, after you confirm. Agents that only run on events can’t be started this way.See Test an agent with Dry run or Run now.Primo AI offers an agent for the work you repeat
Ask Primo AI for something you check every week, such as the devices that stopped checking in, and it answers first. Then it offers a custom agent for the job, with its name, what it does and when it runs. Click Set it up and Primo AI drafts the agent in the chat. Nothing is created until you confirm.See What you can ask.Your workflows are now custom agents
The workflows you set up in Primo now run as custom agents in AI Agents > Agents, with the same instructions and the same schedule. Their reports are now HTML run reports instead of PDF or CSV files. Some came over disabled and wait for you to click Enable agent. Check each agent’s tools first: moved agents can use Primo’s tools without asking.See Find your former workflows.Get an email when a delivery date moves
When the estimated delivery date of a purchase moves to another day, Primo now emails the people who get your order’s shipping email. The email gives the order number, the products, who they’re assigned to, the new date and a tracking link, so you can warn the employee who’s waiting for it.See Get notified when a delivery date changes.Connect Microsoft Entra without leaving the Autopilot setup
Step 1 of the Windows Autopilot setup now connects Microsoft Entra in place, with a Connect Microsoft Entra button. Sign in with a Global Administrator account, accept the permissions Microsoft lists, and continue with step 2. You no longer go through the Entra settings in SaaS, which Autopilot doesn’t need.See Zero-touch for Windows.Start onboarding from the new hire’s panel
When Create onboarding ticket is set to Manual, you open each new hire’s onboarding ticket yourself. The panel of a new hire whose onboarding hasn’t started now opens on the Tickets tab, with a Start onboarding button that creates the ticket.See Create onboarding ticket.Custom agents
Give Primo AI a recurring job of your own, like a Monday briefing on who arrives and who leaves, or a monthly check for SaaS seats that belong to nobody. An agent runs on a schedule or when an event happens in Primo, follows your instructions, and uses only the knowledge and connectors you give it. Set each tool to Always allow, Require approval or Always refuse, then follow each run and its report in the agent’s Runs tab.