> 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/edit-licensees.md).

# Update licensee details

Update an existing licensee.

Account administrators can update general information for a licensee, including the name, description, and address details. The buyer or seller entities for the licensee cannot be updated.

### Update licensee details

To update details for an existing licensee:

1. Go to **Settings** > **Licensees**.
2. Find the licensee you want to edit. &#x20;
3. Select the actions icon (**•••**), then choose **Edit**. Alternatively, select the licensee name. When the licensee details page opens, select **Edit**.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/SP10iSr3FWMu9Od8FHHN/image.png" alt=""><figcaption><p>Select <strong>Edit</strong> to update licensee details.</p></figcaption></figure></div>

4. In the **Edit Licensee** flow, make changes as needed, then save your changes:
   1. **General** – Update the following details:
      1. **Logo** – Upload the licensee's logo in the JPG or PNG format. The maximum file size is 5 MB. You can upload an image by selecting **Select file** or by dragging the image into the field.
      2. **Licensee name** – Update the licensee name.
      3. **External reference** – Add or update the reference number associated with the licensee. You can also remove the number if provided during licensee creation.&#x20;
      4. **Licensee description** – Add or update the licensee description.
   2. **Address information** – Adjust the address as necessary. You can update the existing address or use the same address as that of the buyer.&#x20;


---

# 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/edit-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.
