> 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/email/spamfilter/list-connectionfilter-templates.md).

# Connection Filter Templates

This page lists the connection filter templates saved in CIPP. Templates hold the settings that the **Deploy ConnectionFilter** form applies to a tenant, and they are created either with the **Create template based on filter** action on [Connection Filter](/user-documentation/email/spamfilter/list-connectionfilter.md) or by importing from a community repository.

## Table Details

The columns come from the saved template, so a column is empty where the template does not set that value.

| Column           | Description                                                                                                |
| ---------------- | ---------------------------------------------------------------------------------------------------------- |
| Name             | The template name, taken from the policy it was created from.                                              |
| Is Default       | Carried over from the policy the template was created from. It has no effect when the template is applied. |
| IP Allow List    | The IP addresses and ranges the template always allows through connection filtering.                       |
| IP Block List    | The IP addresses and ranges the template always blocks.                                                    |
| Enable Safe List | Whether the template turns on Microsoft's safe list of trusted senders.                                    |
| GUID             | The unique identifier CIPP assigns to the template.                                                        |

**More Info** opens a flyout with the same six fields as the table.

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Save to GitHub</td><td>Uploads the selected template to a community repository. You are asked for a <strong>Repository</strong>, listing only repositories CIPP can write to, and a <strong>Commit Message</strong>. Greyed out unless the GitHub integration is enabled.</td><td>true</td></tr><tr><td>Delete Template</td><td>Deletes the template from CIPP. Connection filter settings already applied from it in a tenant are not affected.</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/email/spamfilter/list-connectionfilter-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.