> 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/jp/deploying-keeper-to-end-users/keeper-fill/mac/plist-policy-deployment-chrome.md).

# PLIST (.plist) ポリシーの展開

<figure><img src="/files/Jml1x13Sf8WWdDGi0324" alt=""><figcaption></figcaption></figure>

## PLISTポリシーを利用したKeeper Chromeブラウザ拡張機能の展開

### Keeper plistポリシー構成ファイルの作成

ポリシーファイルをまだ作成していない場合は、macOSデスクトップのメニューバーから **\[移動]** > **\[ユーティリティ]** > **\[ターミナル]** の順に選択してターミナルを開き、`/tmp` など任意の場所に**com.google.Chrome.plist**という名前でKeeper plistポリシーファイルを作成します。

![macOSターミナルユーティリティ](/files/pYDcTUjz8CYXJWQCZ3aV)

以下の内容をコピーしてターミナルに貼り付け、Enter/Returnを押します。`/tmp` ディレクトリにplistファイルが作成され、一覧に表示されます。

{% tabs %}
{% tab title="Mac Terminal" %}

```
cd /tmp
touch com.google.Chrome.plist
ls -la
```

{% endtab %}
{% endtabs %}

![plistファイルの作成](/files/oI1rsqddhOH3oMy6vDP0)

任意のファイルエディタで以下の内容をコピーし、**com.google.Chrome.plist**ファイルに貼り付けてから保存します。

{% code lineNumbers="true" %}

```
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
	<dict>
		<key>ExtensionSettings</key>
		<dict>
			<key>bfogiafebfohielmmehodmfbbebbbpei</key>
			<dict>
				<key>installation_mode</key>
				<string>force_installed</string>
				<key>update_url</key>
				<string>https://clients2.google.com/service/update2/crx</string>
			</dict>
		</dict>
                <key>ExtensionPolicies</key>
		<!-- Chrome policies should be outside of ExtensionSettings -->
		<key>PasswordManagerEnabled</key>
		<false/>
		<key>AutofillCreditCardEnabled</key>
		<false/>
		<key>AutofillAddressEnabled</key>
		<false/>
	</dict>
</plist>
```

{% endcode %}

### PLISTポリシーの展開

PLISTポリシーの展開には、複数のツールを利用できます。以下のページでは、Jamf Pro、AirWatch、Microsoft Intuneを使ったPLISTポリシーファイルの展開手順を取り扱います。


---

# 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/jp/deploying-keeper-to-end-users/keeper-fill/mac/plist-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.