> 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/edit.md).

# Edit Reusable Setting

Opens a reusable setting from the selected tenant so its name, description and configuration can be changed. The setting is loaded from the tenant it belongs to, which is carried through from the row the page was opened from, so the correct tenant is used even when the list was showing All Tenants.

## Setting Details

| Field        | Description                                   |
| ------------ | --------------------------------------------- |
| Display Name | The name of the reusable setting. Required.   |
| Description  | The description recorded against the setting. |
| Raw JSON     | The setting's configuration. Required.        |

The configuration is rendered below the fields so it can be read without working through the JSON.

{% hint style="warning" %}
Configuration policies that reference this setting take its new value as soon as it is saved. A reusable setting exists precisely so that one change reaches every policy using it, so check how many policies reference it before changing the configuration.
{% 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/edit.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.