> 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/security/safelinks/safelinks-template.md).

# Safe Links Templates

Safe Links policy templates are saved Safe Links configurations held in CIPP rather than in a tenant, so a policy and rule pair you have settled on can be deployed to any number of customers without rebuilding it each time. Templates get here in two ways: capture one from a live policy with **Create template based on policy** on the Safe Links Policies page, or build one from scratch here. From this page you can also publish a template to a GitHub repository to share it.

## Action Buttons

{% content-ref url="/pages/dHEr3XAVBTY1UwYRsq2j" %}
[Create Safe Links Template](/user-documentation/security/safelinks/safelinks-template/create.md)
{% endcontent-ref %}

{% content-ref url="/pages/sRwSKh3RZDPB4TKLXTGQ" %}
[Deploy Safe Links Template](/user-documentation/security/safelinks/safelinks-template/add.md)
{% endcontent-ref %}

## Table Details

| Column               | Description                                                                                            |
| -------------------- | ------------------------------------------------------------------------------------------------------ |
| Template Name        | The name given to the template.                                                                        |
| Template Description | The description for the template.                                                                      |
| GUID                 | CIPP's identifier for the template. Quote it when raising a support request about a specific 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>Edit Template</td><td>Opens the <a data-mention href="/user-documentation/security/safelinks/safelinks-template/edit.md">Edit Safe Links Template</a> page for the selected template.</td><td>false</td></tr><tr><td>Save to GitHub</td><td>Publishes the selected template to a repository you have write access to, prompting for the repository and a commit message. Greyed out unless the GitHub integration is enabled.</td><td>true</td></tr><tr><td>Delete Template</td><td>Removes the selected 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/security/safelinks/safelinks-template.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.