> 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/mem/reusable-settings-templates/add.md).

# Add Reusable Settings Template

Creates a reusable settings template in CIPP holding a Microsoft Defender Firewall dynamic keyword address list. The template can then be deployed to tenants from [Reusable Settings](/user-documentation/endpoint/mem/reusable-settings.md) or applied through a [Standards & Drift](/user-documentation/tenant/standards.md). Templates are stored in CIPP rather than in a tenant.

## Template

| Field                          | Description                                                                                                                                                                                            |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Template / Policy Display Name | The name of the template. Required. This is also the name the reusable setting takes when it is created in a tenant, and the name CIPP matches on when deciding whether to update an existing setting. |
| Template / Policy Description  | The description recorded against the template.                                                                                                                                                         |

## Group Setting Collection (Policy)

Each row in this table is one entry in the address list. **Add row** appends another, and **Remove** deletes one.

| Field       | Description                                                                                                                                                                          |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Autoresolve | Whether the keyword is resolved to the addresses it currently points at. Set to True for a domain name that should be resolved, and False for an address or range supplied directly. |
| Keyword     | The domain, IP address or address range the entry covers. Wildcards are allowed using the `*` character, and CIPP variables can be inserted so the value differs per tenant.         |

{% hint style="info" %}
Each entry also carries an identifier, which CIPP generates automatically and does not show. Nothing needs entering for it.
{% endhint %}

***

## 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/mem/reusable-settings-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.