Update Deta on Macs your IT team manages
Allow Deta's updater once in your device management, and standard accounts get updates with no prompts.
Updated
How updates work on a managed Mac
When an administrator installs Deta, a standard account can't replace the app. Deta then installs updates with its own background updater, which macOS has to allow once.
| Mac | What people see |
|---|---|
| IT allowed Deta's updater | No prompts. Restart to update appears when an update is ready, and quitting Deta installs it too. |
| Not allowed, administrator account | Deta asks to turn it on in System Settings → General → Login Items & Extensions, once. |
| Not allowed, standard account | No prompts. Updates wait for IT. Check for Updates… offers to open System Settings, where an administrator can turn Deta on. |
Allow Deta's updater
In your device management (Jamf Pro, Kandji, Intune, Mosyle or another MDM), add a Managed Login Items payload, also called Service Management, with one rule:
| Setting | Value |
|---|---|
| Rule type | Team Identifier |
| Value | XPH6SX6VJ9 |
Scope it to the Macs that run Deta. macOS accepts this payload only from MDM, not from a profile installed by hand. Deta's updater is the only background item Deta signs with this team.
The next time Deta finds an update, it registers its updater and macOS allows it with no prompt.
Update a Mac now
Push the latest Deta from deta.studio/download through your MDM, or sign in as an administrator and install it. Older versions of Deta ask for an administrator's password on every update; the latest one doesn't.