> 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/tools/template-packages.md).

# Template Package Manager

CA Templates and Policy (Intune) Templates can be grouped into a package - a shared tag that lets a single Standards Template pull in every template carrying that tag, instead of listing each template's GUID individually. The Template Package Manager is where those packages are viewed, renamed, and deleted, and where their members are managed, for both template types.

{% hint style="info" %}
A package is just a tag shared by its member templates. Deleting a package removes the tag from its members - the templates themselves are not deleted.
{% endhint %}

## Switching Template Type

Use the toggle at the top of the page to switch between Conditional Access Templates and Policy Templates. Each package list is specific to the selected type.

## Managing a Package

Each package is shown with its member count. Expand a package to:

| Action                   | Effect                                                                                                 |
| ------------------------ | ------------------------------------------------------------------------------------------------------ |
| Add an existing template | Select any template of the current type that isn't already in this package and add it.                 |
| Remove a member          | Removes the tag from that template only. The template itself is unaffected.                            |
| Rename package           | Re-tags every current member with the new name. Renaming to an existing package's name merges the two. |
| Delete package           | Removes the tag from every current member. No templates are deleted.                                   |

{% hint style="warning" %}
Renaming or deleting a package affects every one of its member templates at once.
{% endhint %}

## Adding a Template to a Package from the Template List

The "Add to package" action on the CA Templates and Policy Templates lists now offers a dropdown of existing packages, in addition to typing a new package name. Picking an existing package from the list avoids mismatches from typing the name by hand.

***

## 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/tools/template-packages.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.