> 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.md).
# macOS
Deploying KeeperFill to macOS devices using device management platforms
## MDM Deployment for macOS
Follow these steps to deploy KeeperFill to all Mac devices in your organization using your preferred device management platform.
To set up KeeperFill on Mac, you create configuration files in MCX Property List (.plist) format. When you deploy the configuration files to the device using your preferred mobile device management (MDM) tool, the settings are applied.
{% hint style="info" %}
These procedures are a general guide and assume that you have already deployed the Chrome browser within your organization.
{% endhint %}
## Overview of steps
1. Use your preferred editor to create the Keeper .plist policy file.
2. Set up KeeperFill browser extensions.
3. Push the configuration files to all macOS devices in your organization using your preferred mobile device management (MDM) tool.
---
# 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.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.
