> 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

Lists the Intune policy templates saved in CIPP, which are the templates the **Deploy Policy** button on the policy pages draws from. Templates can be imported from a community repository, captured from an existing tenant, or created by saving a policy from one of the policy list pages. Filter buttons narrow the list to Synced Templates or Custom Templates.

## Action Buttons

<details>

<summary>Create New Template</summary>

Opens [New Endpoint Manager Template](/user-documentation/endpoint/mem/list-templates/add.md), where you build a Settings Catalog template from scratch by searching for the settings you want.

</details>

<details>

<summary>Browse Catalog</summary>

Opens a drawer for adding templates to CIPP, with two sources to choose between.

**Community Catalog** is the template catalogue described in [Catalog](/user-documentation/tools/community-repos.md), narrowed to Intune templates. Templates can be previewed and imported the same way as on that page.

**From a Tenant** captures an existing policy from one of your tenants as a template. Select a tenant, then search its policies by name or description and import the one you want.

</details>

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

## Filters

| Filter           | Shows                                                      |
| ---------------- | ---------------------------------------------------------- |
| Synced Templates | Templates that are still linked to a community repository. |
| Custom Templates | Templates that are not linked to a community repository.   |

## Table Details

| Column       | Description                                                                                                                                                                     |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Display Name | The name of the template.                                                                                                                                                       |
| Is Synced    | Whether the template came from a community repository and is still linked to it. A template that has been edited or cloned is no longer linked and shows as not synced.         |
| Synced From  | The repository the template was imported from, shown as owner and repository name. Empty for templates created or cloned in CIPP.                                               |
| Package      | The package the template has been tagged with, where one has been assigned. Packages let a standards template pull in a set of templates by tag rather than by naming each one. |
| Description  | The description recorded against the template.                                                                                                                                  |
| Type         | The template type, for example Catalog, Device, Admin, AppProtection or deviceCompliancePolicies. This determines how the policy is written when deployed.                      |
| Usage        | The standards templates that use this template, and whether each one references it directly or picks it up through its package tag.                                             |

{% hint style="info" %}
Selecting a row opens a flyout listing the standards templates the template is used in, each linking through to that template, followed by the template's own configuration. This is worth checking before deleting a template, since a template in use by a standard will stop that standard applying.
{% endhint %}

{% hint style="info" %}
Packages are viewed, renamed and deleted from [Template Package Manager](/user-documentation/tools/template-packages.md).
{% endhint %}

## Table Actions

<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 template for editing in <a data-mention href="/user-documentation/endpoint/mem/list-templates/edit.md">Edit Template</a>. Only offered for templates that are not synced to a community repository.</td><td>false</td></tr><tr><td>Validate Template</td><td>Checks the template for problems that would stop it deploying, and lists every problem found. Nothing is saved or deployed. Optionally pick a tenant to also check the template's replacement variables and whether the tenant offers each setting.</td><td>true</td></tr><tr><td>Edit Template Name and Description</td><td>Changes the template's name and description. Applying this disconnects the template from the community repository it came from, so it will no longer receive updates.</td><td>true</td></tr><tr><td>Clone Template</td><td>Creates a copy of the template in CIPP. The copy is not linked to a community repository, so it can be edited freely.</td><td>true</td></tr><tr><td>Add to package</td><td>Tags the template with a package name, so that standards templates referencing that package pick it up. Pick an existing package from the dropdown, or type a new package name.</td><td>true</td></tr><tr><td>Remove from package</td><td>Removes the package tag from the template.</td><td>true</td></tr><tr><td>Save to GitHub</td><td>Uploads the template to one of your GitHub repositories, prompting for the repository and a commit message. Only repositories you have write access to are offered. Hidden unless the GitHub integration is enabled.</td><td>true</td></tr><tr><td>Delete Template</td><td>Deletes the template from CIPP. Policies already deployed from it are unaffected.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cipp.app/user-documentation/endpoint/mem/list-templates.md?ask=<question>&goal=<user_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.