> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/jentis-dcp-elements/account-settings/container-administration/edit-a-container.md).
# Edit a Container
{% hint style="warning" %}
It is only possible to edit your container once the DNS A Record and HTML Code are verified.
{% endhint %}
You can easily edit your container’s configuration by going to your **Containers** menu and click on **Edit**:
You are able to change the following fields:
**Basic Settings:**
* **Container name** – A descriptive name for your container.
* *Optional field:* **Consentbar (CMP)** – Select from the list of supported consent bars.
{% hint style="warning" %}
Once the container is created, you can not change the **website domain**.
{% endhint %}
**Advanced Settings (Optional):**
* **Preview URL** – Set a custom URL instead of the website domain for the container configuration preview session. If this field is left empty, the **website domain** configured on the basic settings will be used.
* **Main Domain Cookie** — This feature allows you to configure whether first-party identifiers (e.g., JENTIS User-ID) are implemented at your website’s main domain or subdomain level in your containers. This enables the identification of users across the main domain and its subdomains. For more information, read.
Once you change any of these fields, click **Save** and **Publish** your container again.
---
# 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.jentis.com/jentis-dcp-elements/account-settings/container-administration/edit-a-container.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.
