> 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/versions-and-preview/versions.md).

# Versions

Tag Management configuration orchestrates all data streams using tags, variables, and triggers to solve data needs.

Each JENTIS DCP configuration of your settings comes packed as a version. So you can edit and change your settings in a new version and have that separated into different packages from what is published to productive or staging systems.

Here you can find more details on the JENTIS account and container structure, including the environments of containers: [JENTIS Account & Container Structure](/core-concepts/jentis-account-and-container-structure.md)

A list of all your versions can be found in the Publish section. Each configuration version can be in one of three states:

1. **Current edit** (this one contains all the changes you did recently, but has not been published)
2. **Published** to live, stage or both
3. **Legacy** (these can not be edited anymore, but you can publish those to rollback a published version)

You can also inspect a log of all changes in a version.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jentis.com/jentis-dcp-elements/versions-and-preview/versions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.