> 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/~/changes/362/modules-and-features/settings/licensees/create-licensees.md).

# Create Licensee

Create a new licensee and map them to buyers and sellers.

In the SoftwareOne Marketplace, a licensee must be selected when you are creating a new agreement or ordering products. 

Account administrators can create new licensees and map those licensees to the buyers and sellers within the account.

### Creating a new licensee

{% hint style="info" %}
Before creating a licensee, ensure that your account contains buyers and sellers. Also, make sure that you have the licensee's first and last name and email address.
{% endhint %}

To create a new licensee:

1. Navigate to the **Licensees** page. Then, select **Add**. 
2. In the **Add licensee** wizard, complete the following steps:
   1. **General** - Provide the following details, then select **Next**:
      * **Logo** - (Optional) Add a logo representing the licensee. You can upload an image by clicking **Select file** or by dragging the image into the field.
      * **Licensee name** - (Required) Provide the licensee's name. This can be your company name, department name, or username. 
      * **Resale licensee** - (Optional) Select this checkbox if you are SoftwareOne's partner who is transacting through the partner program. Otherwise, leave it clear.
      * **External reference** - (Optional) Provide a reference number or identifier for the licensee.
      * **Licensee description** - (Optional) Add a description for the licensee.
   2. **Buyers** - Choose the buyer for your transactions. You can link a licensee to one buyer only. When done, select **Next**.
   3. **Sellers** - Choose the SoftwareOne entity that will facilitate transactions and select **Next**.
   4. **Contact person** - Choose a contact person for this licensee and select **Next**. The following options are available:
      1. **None (leave unassigned)** - Select this to leave the contact person unassigned.
      2. **Select an account user** - Select this to choose an existing user. When you select this option, all active users that exist in your account are displayed. If your account contains several users, use the **Search** option to find the user easily.
      3. **Add contact details manually** - Select to add the contact person's details manually. You'll need to provide the person's first name, last name, email address, and optional contact information.
   5. **Address** - Choose the licensee's address. You can use the same address as that of the buyer or provide a new address by selecting **Create a new licensee address**. 
   6. **Overview** - Review the details and select **Add** to create the new licensee.
   7. **Summary** - Select **View details** to open the details page of the licensee. Otherwise, select **Close**.


---

# 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/~/changes/362/modules-and-features/settings/licensees/create-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.