> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/vendor-platform/license-managers.md).

# License Managers

**License Managers**: This is a user role responsible for managing licenses for a group or organization. They have access to the [**End User Portal**](/license-entitlements/portal/end-user-portal.md), where they can perform actions based on the **permissions that have been enabled** for them.

This view gives you an overview over license managers you have created for your account.

![License Managers View](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/MVEHlJeTpcvVAgPmkUP2/WwV0DVHu1R3Enz1de3QR1_image.png)

You can set up a default permission set for any license manager created in the future and you can inspect license manager details (e.g., their permission set, orders, licenses, user groups and some reporting).

Resources

* **License Manager Guide**\
  A comprehensive walkthrough of the end-user portal. It covers all key roles, core concepts, and actions, including managing licenses, devices, orders, users, and more. You'll also find sections on permissions, floating licenses, API integrations, and detailed workflows.\
  [License Manager Guide](/license-entitlements/portal/end-user-portal/license-manager-guide.md)
* **The License Manager**\
  This page details the role of a License Manager within the platform. It explains how to assign a user as a License Manager, the permissions they can have (such as issuing licenses, managing users, and resetting devices), and how to add them to existing orders.\
  [The License Manager](/license-entitlements/portal/end-user-portal/the-license-manager.md)


---

# 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.licensespring.com/vendor-platform/license-managers.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.