> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/2026.2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/2026.2/configuration/application-settings/how-to-guides/licenses.md).

# Add a License Key

## Manage Licenses

### Add a License Key

1. Navigate to the **Licenses** tab on the <i class="fa-gear">:gear:</i> **App Settings** page.
2. Click **Add License Key** in the top right corner of the page, and then paste the license key provided to you by Immuta in the dialog that appears.
3. Click **Save**, and the system will generate a unique user id (UUID) for the license, which will appear at the bottom of the page.

### Delete a License

1. Click **delete** in the **Actions** column of the license you would like to delete.
2. Click **Confirm** in the dialog that appears.

*Note: If you delete a license key, your compliance may be affected and you will need to contact your Immuta Support Professional to receive a new license key.*


---

# 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://documentation.immuta.com/2026.2/configuration/application-settings/how-to-guides/licenses.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.