> 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-reference.md).
# Policy Reference
**Audience:** IT admins authoring and maintaining Keeper EPM policies day to day.
This section is your technical reference for the building blocks that make up a KEPM policy. It covers certificate-based publisher matching (CertificationCheck), approval duration configuration, the policy JSON and extension schema, path variables and protected paths, and wildcard syntax. Use these pages when you need exact field definitions, supported values, syntax rules, or behavior notes for any of these elements—and when you want to understand how each one is evaluated "under the hood."
Policy reference content is intentionally precise. It's the right place to start when you're hand-editing policy JSON, writing a path or wildcard expression, tuning how long approvals stay valid, restricting a rule to a signed publisher, or diagnosing why a path didn't match as expected. When the Policies guides introduce these concepts in context, the Policy Reference provides the authoritative detail behind them.
---
# 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-reference.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.
