> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/integrations/jamf.md).
# Jamf
The Jamf integration connects Boza to your **Jamf Pro** instance so you can deploy the Boza browser extension across your managed Mac fleet — and so Boza can resolve which user each device belongs to, enabling automatic, silent extension login.
{% hint style="info" %}
This page covers connecting the Jamf integration. For the complete extension rollout — configuration profiles, computer groups, and Safari setup — follow the [Jamf deployment guide](/docs/browser-extension/deployment/jamf.md).
{% endhint %}
## What the Integration Does
* **Deploys the browser extension** to selected Jamf computer groups, covering Chrome, Firefox, and Safari.
* **Monitors installation status** per device, so you can see the rollout progress.
* **Resolves device-to-user identity** from Jamf inventory, so the extension can log each user in automatically.
## Setup
### 1. Create an API client in Jamf Pro
1. In Jamf Pro, go to **Settings > API Roles and Clients**.
2. Create a new **API client** with the **Read Computers** permission.
3. Copy the **Client ID** and **Client Secret**.
### 2. Connect in Boza
1. Open **Integrations** from the main navigation.
2. Select **Jamf** to open its configuration panel.
3. Enter:
* **Jamf Pro Server URL** — e.g. `https://yourcompany.jamfcloud.com`
* **Client ID**
* **Client Secret**
4. Click **Test Connection**, then **Save Configuration**.
Once saved, you can sync device status, push the extension, and monitor installations from the same panel.
{% hint style="warning" %}
Connect **LDAP/AD in Jamf Pro** before deploying. Boza relies on it to resolve each device's user email (the `$EMAIL` value). Without it, deployed profiles can't log users in automatically.
{% endhint %}
## Prerequisites
* A Jamf Pro instance with an API client (Read Computers).
* LDAP/AD connected in Jamf Pro for automatic email resolution.
* Administrator permissions in Boza.
## Next Step
Continue with the full [Jamf deployment guide](/docs/browser-extension/deployment/jamf.md) to push the extension to your computer groups.
## Need Help?
If you have questions or run into issues, contact us at ****.
---
# 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://boza.gitbook.io/docs/integrations/jamf.md?ask=&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.
