Primo Changelog
You can now manage software directly in Primo, without switching tools. This update brings two things: a clearer view of what’s installed across your fleet, and a brand new way to keep apps up to date.
App patching
Primo now lets you enable auto-patching per app, so updates are handled automatically. From any software page, you can turn on patching to:
- keep installers up to date
- automatically roll out new versions
- use install scripts when needed
It makes it much easier to stay secure and reduce manual update work.
Install apps from Primo
You can also deploy new apps directly from Primo. We currently support Fleet Maintained Apps on macOS and Windows, with control over:
- targeting (device groups, specific devices, or all devices)
- self service availability
- install scripts
See what’s installed, at a glance
Finally, the Software section now shows what’s installed and where, with versions, filtering, and custom views to track the apps that matter most.
Coming soon: custom packages, and App Store apps for iOS, iPadOS, and Android.
Make your SaaS directory easier to navigate and act on with tags!
Tags are now available on all SaaS apps Primo discovers through SaaS Mapping and the Chrome extension. You can add and edit tags manually to group tools by team, owner, sensitivity, risk level, and more.
If you want Primo to do this for you, you can enable AI auto-tagging in Settings, SaaS tab. Primo will then review your existing and newly discovered apps and automatically apply the most relevant tags.
Once your apps are tagged, you can filter by tag, create focused views for audits or renewals, and spot security risks much faster.
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.