> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/versions-and-proofs/notice-versions.md).

# Notice versions

{% hint style="success" %}
**Access Type**: Notice Versions - Viewer
{% endhint %}

When a consent notice is published or republished, a unique version of the notice is created and stored by Didomi. This enables your organization to view a change log of public facing updates for any particular consent notice.

Your organization's consent notice versions are available by clicking **Versions & Proofs** on the left-hand panel and ensuring the **Notice Versions** tab is selected on the subsequent page.&#x20;

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FHq9d6kEKCtYyTM6S9j9z%2FScreenshot_2026-02-26_at_10_54_12%E2%80%AFAM.jpg?alt=media&amp;token=96a878f2-308d-4329-8381-d36ca293c4cb" alt="" width="563"><figcaption></figcaption></figure>

For every consent notice included in the table, Didomi provides the following information:

{% hint style="info" %}
Additionally, use the available filters to locate a specific consent notice. [Click here](https://docs.didomi.io/versions-and-proofs/notice-versions/notice-version-filters.md) to learn more.
{% endhint %}

<table><thead><tr><th width="238">Field</th><th>Description</th></tr></thead><tbody><tr><td>Notice</td><td>Name and ID of the published notice</td></tr><tr><td>Version ID</td><td>Unique version ID assigned to a particular published/republished consent notice</td></tr><tr><td>Type</td><td>Platform selected for the consent notice when it was created</td></tr><tr><td>Publish Date</td><td>Date the version of the consent notice was published</td></tr><tr><td>Target</td><td>List of domains where the notice is embedded. Only available when a consent notice is loaded based on notice ID</td></tr><tr><td>User</td><td>User in your organization that published the version of the consent notice</td></tr><tr><td>Version Notes</td><td>View any notes that were included when the version of the consent notice was published</td></tr><tr><td><a href="https://docs.didomi.io/versions-and-proofs/notice-versions/download-notice-version.md">Download</a></td><td>Download the JSON configuration of the consent notice version</td></tr><tr><td><a href="https://docs.didomi.io/versions-and-proofs/notice-versions/preview-notice-version.md">Preview</a></td><td>View the UI of the consent notice version</td></tr></tbody></table>


---

# 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.didomi.io/versions-and-proofs/notice-versions.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.
