Primo Changelog

We just made a major upgrade to how device management works in Primo.

MDM policies are now Controls

MDM policies are now called Controls, with a dedicated space in Primo.
The goal is simple: make policies easier to find, easier to understand, and easier to manage at scale. We also simplified naming:

• Profiles are now Device Groups
• Installed Apps is now Software
  ‍
  

Target devices directly, without profile gymnastics

The biggest change is targeting. Instead of relying on MDM Profiles, you can now assign Controls directly to devices.

Create a Control based on the platform, configure it once, then choose where it applies:

• a device group
• specific devices
• or your entire fleet
  

This makes rollouts faster, clearer, and much easier to reason about.

One place to see every policy deployed

You now get a single view of all Controls applied across your fleet, so you can quickly answer: what is deployed, where, and to whom?

Duplicate policies with confidence

Duplicating a policy was possible before, but it is now much more obvious and frictionless. It is the fastest way to reuse a setup and adapt it for another group or exception case.

Profiles become Device Groups

We are also simplifying the structure:

• MDM Profiles are moving to Controls
• Profiles are becoming Device Groups

Device Groups are now what they should have always been: a clean way to organize your fleet, not a requirement just to deploy policies.

Installed Apps becomes Software

Installed Apps is now Software, with a clearer experience and a dedicated section.

This is the first step in bringing more of Fleet’s software management capabilities into Primo, so you can manage software with the same level of clarity as devices and policies.

Get a clear view of all the SaaS apps and work identities used across your company.

SaaS Mapping is now available. It shows every SaaS app accessed with a company email through Google Workspace. If you need more coverage, you can add the new Chrome extension. It maps all work identities used with a company email, even when users are not signing in with Google.

SaaS Mapping is enabled by default if you connected Google Workspace. You can deploy the Chrome extension through an MDM profile using the Chrome MDM Policy. LEarn more

This feature is available for all organizations with an active SaaS Management subscription.

Primo only focuses on work related SaaS usage. No personal accounts, no browsing data, and no content are collected.

Set it once, schedule the date, and Primo runs your onboardings end to end with a final review.

Define recurring settings once, including email creation, default apps, access groups. For each hire, pick the date and Primo generates a run you can review and adjust.
On the scheduled day Primo provisions accounts, creates mailboxes, applies access then records outcomes.

Equipment shipment remains manual, with automated procurement coming soon.

Keep everything in one place to cut handoffs and speed day one.