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

# Addigy

Deploy the We360.ai MyZen macOS agent with Addigy.

**PKG Upload & Deployment**

1. Log in to **Addigy** (`app.addigy.com`).
2. Navigate to **Catalog > Software**.
3. Click **New** to create a new software item.
4. Upload the MyZen `.pkg` file.
5. Addigy auto-generates an `_install.sh` script. Review it — typically no changes are needed.
6. Optionally configure a **Condition** to control when the install runs (e.g., only if the app is not already installed).
7. Click **Save**.
8. Navigate to **Policies** and select the target Policy.
9. Add the software item to the Policy's **Catalog**.
10. Devices in that Policy will receive the software.

**PPPC Profile Deployment**

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

1. Navigate to **Catalog > MDM Profiles**.
2. Click **New** to create a new profile.
3. Select **Privacy Preferences Policy Control** payload.
4. Configure the fields as described 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 add to target Policy.

**Option B — Upload custom profile:**

1. Navigate to **Catalog > MDM Profiles > Custom Profile**.
2. Upload `zs-pppc.mobileconfig`.
3. Add to target Policy.

**Background Items**

Navigate to **Catalog > MDM Profiles** and use the **Service Management - Managed Background Items** payload, or upload `zs-background-items.mobileconfig` as a custom profile.

{% hint style="info" %}
Addigy uses an agent-based architecture for software installs and MDM for profiles. Profile deployment may be slightly slower than software deployment. Addigy preserves the original PKG filename.
{% 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/addigy.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.