> 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/license-entitlements/portal/introduction.md).

# Introduction

For parties external to the software vendor, we make available a range of interfaces, including a set of portals.

LicenseSpring's portals can be configured to allow license management by an external third party.

Some common tasks that can be done via the portals include the following:

* Assign/unassign users to a license
* Transfer a license from one device to another
* Look up licenses from an order and dispatch them across the organization
* Issue new licenses for an existing order without the intervention of the software vendor
* Activate or deactivate licenses for computers that do not have access to the internet
* Reset licenses

### Available Portals

LicenseSpring currently maintains 3 portals (not including the Vendor platform):

{% hint style="info" %}
All of our portals, including the API, can be white-labeled to a vendor's subdomain. For more details, please contact us directly.
{% endhint %}

#### User Portal

URL: [**users.licensespring.com**](https://users.licensespring.com/)

License managers can log in to this portal and manage licenses for all of the orders they have been assigned to, according to the permissions they have been given.

#### Offline Activation Portal

URL: [**offline.licensespring.com**](https://offline.licensespring.com/)

End users can activate and deactivate their licenses using the offline activation method via this portal.

#### Air-Gapped Activation Portal

URL: [**airgap.licensespring.com**](https://airgap.licensespring.com/)

End users can activate and deactivate their licenses that are air-gapped using this portal.


---

# 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/license-entitlements/portal/introduction.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.