> 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/mosyle-business.md).

# Mosyle Business

Deploy the We360.ai MyZen macOS agent with Mosyle Business.

**PKG Upload & Deployment**

1. Log in to **Mosyle Business** (`business.mosyle.com`).
2. Navigate to **Management** (bottom navigation).
3. Select **Install App**.
4. Click **Add new profile** (top-right).
5. Choose **macOS** as the platform.
6. Select **Enterprise App** (not App Store).
7. Choose **Upload a PKG file** as the source.
8. Upload the MyZen `.pkg` file.
9. Configure:
   * **Installation type:** "Install and keep" or "Install once"
   * **Assignment:** Scope to specific users, devices, or groups.
10. Click **Save**.

**PPPC Profile Deployment**

**Option A — Built-in builder:**

1. Navigate to **Management**.
2. Select **Privacy & Security > Privacy Preferences**.
3. Click **Add new profile**.
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. Scope and **Save**.

**Option B — Custom profile upload:**

1. Navigate to **Management > Custom MDM Profiles**.
2. Upload `zs-pppc.mobileconfig`.
3. Scope and **Save**.

**Background Items**

Use the **Managed Background Items** profile under the macOS 13+ management section, or upload `zs-background-items.mobileconfig` as a custom profile.

{% hint style="warning" %}
MyZen is a custom app — use the **Enterprise App** path, not "Auto Apps." Ensure the Package Identifier matches exactly to avoid reinstallation loops.
{% 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/mosyle-business.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.