> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/endpoint/mem/list-templates.md).

# Policy Templates

This page gives you the ability to view all configured templates, in addition to viewing the raw JSON and the type of policy.

## Page Actions

<details>

<summary>Browse Policy Catalog</summary>

This flyout wizard will allow you to browse the policy catalog. Select one of your configured [Community Repositories](/user-documentation/tools/community-repos.md) and then import the desired templates.

</details>

{% @storylane/embed subdomain="app" linkValue="939rpjvy23oy" url="<https://app.storylane.io/share/939rpjvy23oy>" %}

## Table Details <a href="#listmempolicytemplates-details" id="listmempolicytemplates-details"></a>

| Field        | Description                                                                                                         |
| ------------ | ------------------------------------------------------------------------------------------------------------------- |
| Display Name | The name of the template.                                                                                           |
| Is Synced    | If the template is synced to GitHub.                                                                                |
| Package      | Information on if the policy template has been added to a package.                                                  |
| Description  | The description for the template.                                                                                   |
| Type         | The template type, for example Catalog or Device.                                                                   |
| Usage        | Includes information on if the template is used by direct addition or package tag in a standards or drift template. |

## Table Actions <a href="#listmempolicytemplates-actions" id="listmempolicytemplates-actions"></a>

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Edit Template</td><td>Opens the <a data-mention href="/pages/duA2HqIiYsWca1j5ztQN">/pages/duA2HqIiYsWca1j5ztQN</a> page</td><td>false</td></tr><tr><td>Edit Template Name and Description</td><td>Opens a modal to edit the name and description of the selected template(s)</td><td>true</td></tr><tr><td>Add to package</td><td>Opens a modal to add the selected template(s) to an Intune tag. Enter the name of the tag you want to add the template(s) to</td><td>true</td></tr><tr><td>Remove from package</td><td>Opens a modal to remove the selected template(s) from their package. </td><td>true</td></tr><tr><td>Save to GitHub</td><td>Saves the selected template(s) to your chosen GitHub repo</td><td>true</td></tr><tr><td>Delete Template</td><td>Opens a modal to confirm deletion of the selected template(s)</td><td>true</td></tr><tr><td>More Info</td><td>Opens Extended Info flyout</td><td>false</td></tr></tbody></table>

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/KelvinTegelaar/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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.cipp.app/user-documentation/endpoint/mem/list-templates.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.