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

# Kandji

Deploy the We360.ai MyZen macOS agent with Kandji.

**PKG Upload & Deployment**

1. Log in to **Kandji** (`your-tenant.kandji.io`).
2. Navigate to **Library**.
3. Click **Add New** and select **Custom App**.
4. Upload the MyZen `.pkg` file.
5. Configure:
   * **Install Type:** "Install once per device" or "Continuously enforce"
   * **Audit Script (optional):**

     ```bash
     #!/bin/bash
     if [ -d "/usr/local/zs/zs.app" ]; then
       exit 0  # Installed
     else
       exit 1  # Not installed, trigger reinstall
     fi
     ```
6. Click **Save**.
7. Navigate to **Blueprints** and add the Custom App to the target Blueprint.

**PPPC Profile Deployment**

**Option A — Native PPPC builder:**

1. Navigate to **Library**.
2. Click **Add New** and select **Privacy Preferences**.
3. 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).
4. Toggle Accessibility to **Allow**.
5. Click **Save** and add to target Blueprint.

**Option B — Custom profile upload:**

1. Navigate to **Library > Add New > Custom Profile**.
2. Upload `zs-pppc.mobileconfig`.
3. Add to target Blueprint.

**Background Items**

Use the dedicated **Managed Background Items** library item. Kandji provides a UI to configure rules by label, bundle ID, or team ID. Add Team ID `5KPT5U8WVR`.

{% hint style="info" %}
Kandji's "Continuously enforce" mode will reinstall the app if the audit script fails — useful for ensuring the agent stays installed. Kandji 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/kandji.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.