> 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/linux/json-policy-deployment-chrome.md).
# JSON Policy Deployment - Chrome
## Deploying Keeper Chrome Browser Extension via JSON Policies
### Step 1: Create a Keeper JSON policy configuration file
1. If you do not have a JSON policy file created, create your Keeper JSON policy file in your desired location (e.g., /tmp) and name it `keeperbe.json`.
**OR** create your **keeperbe.json** file via command-line
```
cd /tmp
touch keeperbe.json
```
2\. In your preferred JSON file editor or basic file editor, copy, paste and save the contents, below, into the **keeperbe.json** file or the policy file in which you currently utilize for your organization.
```
{
"ExtensionSettings": {
"bfogiafebfohielmmehodmfbbebbbpei": {
"installation_mode": "force_installed",
"update_url":
"https://clients2.google.com/service/update2/crx"
}
}
}
```
### Step 2: Setup configuration folders
{% hint style="info" %}
If you currently have configuration folders setup for the user PCs in your organization, proceed to Step 3: Deploying the Keeper JSON Policy File.
{% endhint %}
On each PC, in your organization, that you would like to apply this policy on, you’ll need at least one folder to apply this policy.
1. If it does not already exist, create the directory structure, verbatim, as follows; `/etc/opt/chrome/policies/managed`and set the proper permissions for that directory.
**OR** create your directory structure via command-line
```
sudo mkdir /etc/opt/chrome/policies/managed
sudo chmod 755 /etc/opt/chrome/policies/managed
```
{% hint style="info" %}
The creation of this directory will most likely **NOT** be in the same directory as where Chrome is installed on the target Linux devices. Ex: My Chrome installed directory is /opt/google/chrome but my managed policy directory, in which my organization manages my Chrome install, is in the /etc/opt/chrome/policies/managed directory.
{% endhint %}
### Step 3: Deploying the Keeper JSON Policy File
Use your preferred method (utility or script) to push the **keeperbe.json** policy file and Chrome to the target Linux devices in your organization.
* Push the **keeperbe.json** file to the `/etc/opt/chrome/policies/managed` directory on all target Linux devices in your network.
* Confirm that the files are in the correct directories on all the target Linux devices.
### Step 4: **Check Your Chrome Policies**
On a target client device, open Google Chrome and navigate to **chrome://policy** to see all policies that are applied.
{% hint style="info" %}
You may need to select "Reload Policies" to apply this new policy to the target Linux devices.
{% endhint %}
You may need to close and reopen Google Chrome before the new policies appear.
---
# 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/linux/json-policy-deployment-chrome.md?ask=&goal=
```
`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.