> 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/tenant/gsa/security-profiles/templates.md).

# Security Profile Templates

This page lists your Global Secure Access security profile templates. A security profile groups filtering policies, each with its own priority, and is applied to users by a Conditional Access policy. The template links filtering policy templates, so changing a filtering policy template changes every security profile that uses it.

A security profile filters nothing on its own: a Conditional Access policy has to use it. Deploying needs a Microsoft Entra Internet Access licence (included in Microsoft Entra Suite) in each tenant.

## Action Buttons

{% content-ref url="/pages/YtXuYfT3TVnGHc9wbQsl" %}
[Add or Edit Security Profile Template](https://docs.cipp.app/user-documentation/tenant/gsa/security-profiles/template.md)
{% endcontent-ref %}

## Table Details

| Column      | Description                                                                       |
| ----------- | --------------------------------------------------------------------------------- |
| Name        | The template name. It is also the security profile name in each tenant.           |
| Priority    | The order the profile is processed in, from 100 to 64999. Lower numbers go first. |
| State       | Whether the profile is enabled or disabled.                                       |
| Description | The description saved with the template.                                          |

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Deploy Template</td><td>Opens the Deploy Security Profile drawer. Choose one or more tenants (or All Tenants) and select <strong>Deploy</strong>. Each tenant gets the security profile and its filtering policies created or updated to match the template, and the results list what changed in each tenant. A tenant is left unchanged when it has no Microsoft Entra Internet Access licence, or when the template clashes with something already there (for example another profile using the same priority, or two profiles with the template's name).</td><td>false</td></tr><tr><td>Edit Template</td><td>Opens <a data-mention href="https://docs.cipp.app/user-documentation/tenant/gsa/security-profiles/template.md">Add or Edit Security Profile Template</a> for editing.</td><td>false</td></tr><tr><td>Save to GitHub</td><td>Saves the template to a community repository you can write to, together with the filtering policy templates it links. Importing it from the repository brings those too. Shown when the GitHub integration is enabled.</td><td>false</td></tr><tr><td>Delete Template</td><td>Deletes the template from CIPP. It is refused while a Conditional Access template still uses it, and the message names those templates. Profiles already deployed to tenants are not removed.</td><td>false</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full template.</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/tenant/gsa/security-profiles/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.
