> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/asset-management/licenses.md).
# Licenses
We understand licenses for assets are an important part of your IT Asset Management. We want to help you keep all your documents and information together and keep your team informed.
#### Drop Down License Information View
* Next to the name of your license is an arrow. Click on the arrow to view information about your license, who is assigned to the license, and the activity history.
#### Edit and Delete
* Under the Actions column, you can edit, the paper and pencil, or delete, the trashcan, your license. Users must have apropriate permissions to utilize these functions.
#### Change Column View
* Using our table view, each user can individually customize their table headings and hide or view whichever columns they want to view. By clicking the table view button and highlighting the column titles they want seen, and unhighlighting the titles they want hidden.
You can customize your table view to whatever works best for you.
---
# 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.adminremix.com/asset-management/licenses.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.
