> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/deploying-keeper-to-end-users/keeper-fill/mac/plist-policy-deployment-chrome/jamf-pro-r-policy-deployment-chrome.md).

# Jamf Pro Policy Deployment - Chrome

<figure><img src="/files/5Ac677ofztKNwgxKPlwz" alt=""><figcaption></figcaption></figure>

## Deploying Google Chrome PLIST (.plist) Policy using Jamf Pro

This is a general overview of how to deploy Google Chrome's .plist configuration profile, to computers within your organization, using Jamf Pro.

### **Upload Created PLIST File**

Upload the manually created Google Chrome PLIST file that defines the properties for the preference domain you specify in Jamf Pro.

1. Log in to Jamf Pro.
2. Click **Computers** at the top of the page.
3. Click **Configuration Profiles**.
4. Click **New**.
5. Use the General payload to configure basic settings, including the level at which to apply the profile and the distribution method.
6. Click the Application & Custom Settings payload, and then click **Upload**.
7. Click **Add.**
8. Enter **com.google.Chrome** in the **Preference Domain** field.
9. To upload the custom PLIST file choose **Upload File**, enter the preference domain for which you want to set properties. Click **Upload PLIST File**, and then choose the com.google.Chrome.plist file previously created.

{% hint style="info" %}
**Note:** If the PLIST file contains formatting errors, follow the [PLIST (.plist) Policy Deployment](/enterprise-guide/deploying-keeper-to-end-users/keeper-fill/mac/plist-policy-deployment-chrome.md) instructions to remediate the issue.
{% endhint %}

10\. Click the **Scope** tab, and then configure the scope of the configuration profile.\
11\. Click **Save**.

<figure><img src="/files/OPDMhAYKdv9D4K9lKcVi" alt=""><figcaption><p>Jamf Pro Configuration Profile</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/enterprise-guide/deploying-keeper-to-end-users/keeper-fill/mac/plist-policy-deployment-chrome/jamf-pro-r-policy-deployment-chrome.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.