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

# Jamf Now

Deploy the We360.ai MyZen macOS agent with Jamf Now, including the PKG filename caveat for Stealth.

**PKG Upload & Deployment**

1. Log in to **Jamf Now** (`your-instance.jamfnow.com`).
2. In the left sidebar, click **Apps**.
3. Click **Add an App** and select the **Upload Your App** tab.
4. Drag and drop the MyZen `.pkg` file, or click **browse** to select it.
5. Jamf Now will process the file and show a **Review Your App** dialog.
6. Verify the **App Name** (e.g., "zs") and the **Bundle ID** are correct.
7. Click **Done** to finish the upload.
8. Navigate to **Blueprints** and select the target Blueprint.
9. Go to the **Apps** section and add the uploaded app.
10. Click **Save Blueprint**.
11. Devices assigned to this Blueprint will receive the app at next check-in.

**PPPC Profile Deployment**

1. Navigate to **Blueprints** > target Blueprint.
2. Go to the **Custom Profiles** section.
3. Click **Upload** and select `zs-pppc.mobileconfig`.
4. Click **Save Blueprint**.

{% hint style="danger" %}
**Jamf Now does not have a built-in PPPC profile builder.** You must upload a pre-built `.mobileconfig` file. The profiles provided in this guide are ready to use.
{% endhint %}

{% hint style="warning" %}
**Filename renaming concern:** Jamf Now may rename the uploaded PKG to `app.pkg` during distribution. This breaks MyZen's **stealth** licensing (which is encoded in the filename). Please request a **custom stealth installer** from our team. If unavailable, request our team for **stealth config zs.json** file, which has to be placed in `/Library/Preferences/zs.json`
{% endhint %}

**Background Items**

Upload `zs-background-items.mobileconfig` via the **Custom Profiles** section (same process as PPPC).

**Verification**

1. Navigate to **Blueprints** and select the target Blueprint.
2. Check the **Devices** section — confirm the device appears and app is installed.
3. Ask the end user to **logout/login** or **restart**.
4. Verify the endpoint appears online in the **We360.ai dashboard** at `portal.we360.ai`.

**Limitations**

* Custom Apps and Custom Profiles require the **Jamf Now Plus** plan.
* No Smart Groups or conditional logic — only static Blueprint assignments.
* Limited troubleshooting and logging compared to Jamf Pro.


---

# 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/jamf-now.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.