> 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/keeperpam/endpoint-privilege-manager/policies/policy-examples.md).
# Policy Examples
Step-by-step KEPM policy examples for common operational and security scenarios
**Audience:** IT admins who want step-by-step examples for common tasks.
This section provides practical, real-world examples to help you understand how KEPM features work together and how to apply them in common operational scenarios. Examples are designed to turn reference material into repeatable patterns you can adapt to your environment—so you can move from “what does this setting do?” to “how do I implement this safely and consistently?” with less trial and error.
Each example is self-contained and focuses on a specific outcome, showing the configuration approach, key considerations, and expected behavior. Where appropriate, examples link back to the relevant reference pages so you can dig deeper into individual settings, options, and related concepts.
---
# 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/keeperpam/endpoint-privilege-manager/policies/policy-examples.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.
