> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/enterprise-guide/deploying-keeper-to-end-users/keeper-fill/mac/plist-policy-deployment-chrome.md).
# Chrome Policy Deployment via .plist
Deploying the Keeper Browser Extension to Chrome via .plist Policy
### Create a Keeper plist policy configuration file
If you do not have a policy file created, create your Keeper .plist policy file in your desired location (e.g., /tmp) and name it `com.google.Chrome.plist`. To open Terminal, select Go from the macOS menu bar, then select Utilities > Terminal.
Copy and paste the contents below into your Terminal, and press Return. This will create your .plist file within the /tmp directory and display that the file is there.
{% tabs %}
{% tab title="Mac Terminal" %}
```
cd /tmp
touch com.google.Chrome.plist
ls -la
```
{% endtab %}
{% endtabs %}
In your preferred file editor or basic file editor, copy, paste and save the contents, below, into the **com.google.Chrome.plist** file.
{% code lineNumbers="true" %}
```
ExtensionSettingsbfogiafebfohielmmehodmfbbebbbpeiinstallation_modeforce_installedupdate_urlhttps://clients2.google.com/service/update2/crxExtensionPoliciesPasswordManagerEnabledAutofillCreditCardEnabledAutofillAddressEnabled
```
{% endcode %}
### Deploying your PLIST Policy
There are multiple tools to deploy your PLIST policy. In the next set on instructions, we will walk through deploying your PLIST policy file via Jamf Pro, AirWatch and Microsoft Intune.
---
# 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://newdocs.keeper.io/en/enterprise-guide/deploying-keeper-to-end-users/keeper-fill/mac/plist-policy-deployment-chrome.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.
%20Policy%20Deployment.jpg?alt=media&token=e86568ab-a3ad-457d-8941-addd385449c5)