> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-self-hosted/operations/upgrades/apply-configuration-changes.md).
# Apply configuration changes
Change a configuration value on an existing CARTO Self-Hosted deployment and re-deploy, without changing the release version
Use this procedure to change a configuration value — a domain, database endpoint, storage bucket, SSO setting, AI key, and so on — on an existing deployment. This is an *apply changes* (reconfigure) operation: it re-deploys your installation with the new settings **without** moving to a new release version. To move to a newer version instead, see [Updates](/carto-self-hosted/operations/upgrades/updates.md).
{% hint style="info" %}
For how configuration is structured and stored in each method, see [How Configuration Works](/carto-self-hosted/concepts/configuration-management.md). For recommendations on tracking and securing it, see [Manage configuration as code](/carto-self-hosted/best-practices/operations/operations-best-practices.md#manage-configuration-as-code).
{% endhint %}
{% tabs %}
{% tab title="Kots" %} 
Configuration changes are made in the [Admin Console](/carto-self-hosted/operations/licensing-and-admin/kots-admin-console.md).
1. Log in to the **Admin Console**.
2. Open the **Config** tab.
3. Edit the settings you need to change.
4. Click **Save config**.
5. Wait for the **Preflight checks** to complete.
6. Click the **Deploy** button to apply the new configuration.
7. Monitor progress in the **Details** section until all services are healthy.
{% hint style="info" %}
The previous configuration stays available in the **Version history** tab, where you can review the diff between versions or redeploy an earlier one if needed.
{% endhint %}
{% endtab %}
{% tab title="Helm" %} 
Configuration changes are made in your `customizations.yaml` file. You do **not** need to update the chart or download a new customer package — that is only required for a [version update](/carto-self-hosted/operations/upgrades/updates.md).
1\) Edit `customizations.yaml` with your change. For available overrides, see [Advanced customizations](/carto-self-hosted/reference/advanced-helm-customizations.md).
2\) (Recommended) Run the [preflight checks](/carto-self-hosted/deployment/kubernetes-helm.md) to validate the change before applying it.
3\) Apply the change with `helm upgrade`, passing all three files:
```
helm upgrade \
carto \
carto/carto \
-f carto-values.yaml \
-f carto-secrets.yaml \
-f customizations.yaml
```
4\) Commit the updated `customizations.yaml` to version control.
{% endtab %}
{% endtabs %}
## Verify the change
After applying, confirm the deployment is healthy:
* [ ] All pods are in `Running` or `Completed` state
* [ ] The CARTO application is reachable and you can log in
* [ ] The setting you changed is reflected in the platform
---
# 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.carto.com/carto-self-hosted/operations/upgrades/apply-configuration-changes.md?ask=&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.