> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/macos-mdm/simplemdm.md).

# SimpleMDM

Deploy the We360.ai MyZen macOS agent with SimpleMDM.

**PKG Upload & Deployment**

1. Log in to **SimpleMDM** (`a.simplemdm.com`).
2. Navigate to **Apps** in the left sidebar.
3. Click **Add App** and choose **Custom App** (Enterprise App).
4. Upload the MyZen `.pkg` file.
5. Configure:
   * **Name:** e.g., "MyZenV2"
   * **Deploy automatically:** Toggle on if desired.
6. Click **Save**.
7. Navigate to **Device Groups** and assign the app.

**PPPC Profile Deployment**

**Option A — Native PPPC builder:**

1. Navigate to **Profiles** in the left sidebar.
2. Click **Create Profile**.
3. Select **Privacy Preferences** payload.
4. Configure with the identifiers and code requirements in [App & Team Identifiers](/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/macos-mdm/macos-mdm.md#app-and-team-identifiers).
5. Click **Save** and assign to a Device Group.

**Option B — Custom profile upload:**

1. Navigate to **Profiles > Create Profile > Custom**.
2. Upload `zs-pppc.mobileconfig`.
3. Assign to a Device Group.

**Background Items**

Use **Profiles > Create Profile > Managed Background Items**, or upload `zs-background-items.mobileconfig` as a custom profile.

{% hint style="info" %}
SimpleMDM preserves the original PKG filename. No Smart Groups — only static Device Group assignments.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/macos-mdm/simplemdm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.