> 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によるChromeポリシーの展開
plistポリシーによるChrome向けKeeperFillの展開
### Keeper plistポリシー構成ファイルの作成
ポリシーファイルをまだ作成していない場合は、macOSのメニューバーから **\[移動]** > **\[ユーティリティ]** > **\[ターミナル]** の順に選択してターミナルを開き、`/tmp` など任意の場所に `com.google.Chrome.plist` という名前でKeeper plistポリシーファイルを作成します。
以下の内容をコピーしてターミナルに貼り付け、Enter/Returnを押します。`/tmp` ディレクトリにplistファイルが作成され、一覧に表示されます。
{% tabs %}
{% tab title="Mac Terminal" %}
```
cd /tmp
touch com.google.Chrome.plist
ls -la
```
{% endtab %}
{% endtabs %}
.jpg?alt=media)
任意のファイルエディタで以下の内容をコピーし、`com.google.Chrome.plist` ファイルに貼り付けてから保存します。
{% code lineNumbers="true" %}
```
ExtensionSettingsbfogiafebfohielmmehodmfbbebbbpeiinstallation_modeforce_installedupdate_urlhttps://clients2.google.com/service/update2/crxExtensionPoliciesPasswordManagerEnabledAutofillCreditCardEnabledAutofillAddressEnabled
```
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.keeper.io/enterprise-guide/jp/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)