> 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/autopilot/enrollment-restriction-templates/add.md).

# Add Enrollment Restriction Template

Creates an enrollment restriction template. Templates can also be saved from an existing restriction with **Save as Template** on [Enrollment Restrictions](https://docs.cipp.app/user-documentation/endpoint/autopilot/enrollment-restrictions.md).

## Enrollment Restriction Template

| Field                                                             | Description                                                                                                                                                                        |
| ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Platform                                                          | Android, iOS/iPadOS, macOS, or Windows.                                                                                                                                            |
| Name                                                              | The name of the restriction the template creates. Deploying to a tenant that already has a restriction with this name on the same platform updates that restriction.               |
| Priority                                                          | The position a new restriction is placed at, where 1 is the highest. Leave blank to place it below each tenant's existing restrictions. Existing restrictions keep their position. |
| Description                                                       | Optional text describing the restriction.                                                                                                                                          |
| Who should this restriction apply to?                             | **Do Not Assign**, **Assign to All Users**, or **Assign to Custom Group**.                                                                                                         |
| Custom Group Names separated by comma. Wildcards (\*) are allowed | Shown for **Assign to Custom Group**. The names are looked up in each tenant the template is deployed to.                                                                          |

**Platform settings**

The platform settings are the same as when adding a restriction. Windows and iOS/iPadOS are described on [Enrollment Restrictions](https://docs.cipp.app/user-documentation/endpoint/autopilot/enrollment-restrictions.md), macOS on [Apple](https://docs.cipp.app/user-documentation/endpoint/autopilot/enrollment-restrictions/apple.md), and Android on [Android](https://docs.cipp.app/user-documentation/endpoint/autopilot/enrollment-restrictions/android.md).

***

## 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/autopilot/enrollment-restriction-templates/add.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.
