MDM profile types at a glance
AI Protect never integrates with your MDM’s API — the console generates profiles, and a human pushes them through whatever MDM you already run. That is deliberate: we never hold a credential that could push trust anchors or software to your whole fleet. The cost is that you deliver the files; this section is the map.
| Profile | Scope | What it carries | Contains credentials? | Where in the console |
|---|---|---|---|---|
| Enrollment profile | One per employee | Enrollment settings + that person’s single-use token | Yes — never deploy fleet-wide | Employees → Export MDM profiles |
| Proxy profile | Device group | The interception on-switch, proxy settings, folder-sensor grants, browser-extension force-install | No | Proxy profile page |
| Safari DDM declaration | Device group (DDM channel) | Pins the Safari extension always-on | No | Proxy profile page (separate export) |
| CA certificate profile | One per device | That device’s interception CA public certificate | No (public certificate only) | Devices → row action MDM profile |
| Cowork profile | Device group | Anthropic Cowork folder constraints + update freeze | No | Cowork controls page |
Delivery rules that apply to all of them
Section titled “Delivery rules that apply to all of them”- Device scope, not user scope. A user-scoped profile is readable by the person being monitored, and some of these carry credentials or trust settings. The two failure modes that look like “nothing happened” — user scope, and a wrong code requirement in your MDM — are worth checking first whenever a profile seems to have no effect.
.mobileconfigvs DDM. Everything above ships as a standard.mobileconfigexcept the Safari declaration, which uses declarative device management — a different MDM channel. A profile-only MDM applies DDM declarations silently not at all; verify your MDM supports DDM before relying on it. It also requires a supervised Mac on macOS 15 or later.- Per-employee and per-device profiles are not interchangeable. An enrollment profile carries one person’s single-use token; a CA certificate profile carries one machine’s certificate. Assign each file to exactly its subject.