> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/settings/licensees.md).

# Licensees

Learn about licensees in the Marketplace Platform.

A licensee is a specific person or a department within your account that receives the license to use the product.&#x20;

Licensees are the entities that consume the software products or services procured by the buyer. In the SoftwareOne Marketplace, licensees are connected to buyers and sellers, and they are critical in establishing new agreements. Your account may contain multiple licensees, but each licensee can only be connected to one buyer and one seller at a time.

### Licensees page

The **Licensees** page allows account administrators to add new licensees. Administrators can also use this page to view, modify, enable, or disable a licensee.

To open the page, choose **Settings** > **Licensees** from the main menu.&#x20;

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2FpcVtQHWllh4SgVsUbt4H%2Fimage.png?alt=media&amp;token=da7f8652-93f0-4a4d-b42a-c941e631cfe5" alt=""><figcaption><p>Use the Licensees page to view and manage licensees.</p></figcaption></figure></div>

On the **Licensees** page, you can use the [sort and filter options](/marketplace-platform/getting-started/customize-the-data-grid.md) and [show or hide specific columns](/marketplace-platform/getting-started/customize-the-data-grid.md#managing-columns) to customize the list. You can also view a licensee's details by selecting their name, and you can manage the licensee by using the options in the **Actions** column.

### Related topics

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/otpkXfAhkweaN5iv7kl7" %}
[Licensee states](/modules-and-features/settings/licensees/licensee-states.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/naAlX4d2jnPSQdebHMMq" %}
[Create licensee](/modules-and-features/settings/licensees/create-licensees.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/W7VbN088Jd2dvKimzK8t" %}
[View licensees](/modules-and-features/settings/licensees/view-licensees.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/02beiqtRGJ7UcScCykfb" %}
[Update licensee details](/modules-and-features/settings/licensees/edit-licensees.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/CSs82J3sAlWmSQ1jXw0X" %}
[Enable or disable licensee](/modules-and-features/settings/licensees/enable-or-disable-licensees.md)
{% endcontent-ref %}


---

# 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.platform.softwareone.com/modules-and-features/settings/licensees.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.
