> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/install-cortex-xsoar/troubleshoot-your-installation/upload-your-license-to-the-textual-ui.md).

# Upload your license to the textual UI

There may be issues related to your Cortex XSOAR deployment in which your tenant is not available, and you need to provide your license for a support session with support or engineering to troubleshoot and resolve the issues. You may also need your license to perform an upgrade. You can copy your license details into the textual UI for support or engineering to access.

1. From the textual UI menu in your VM, select **Upload License**.

   ![opp-upload-license.png](/files/kYKmR5mSRuqM7qz69qnX)
2. Open the license JSON file you downloaded from Cortex Gateway and copy the content into the **License JSON** field in the textual UI.
3. Click **Apply**.

   The license details are now available for support or engineering to access.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/install-cortex-xsoar/troubleshoot-your-installation/upload-your-license-to-the-textual-ui.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.