> 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/customer-accounts.md).

# Customer Accounts

LicenseSpring allows customers to be grouped by account. This is useful if you license software to an organization with different departments, or multiple locations, and can be found by expanding the "Customers" tab in the left-hand navigation.

![List of Customer Accounts](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/yWDY1jJPgM0BYjg7vdKg/jzejGCFWHz8wjd1KjTvbH_image.png)

The columns in the accounts table include:

* `Name` — Account name
* `Code` — Account code
* `Number of customers` — Number of customers that belong to a specific account
* `Email` — Email address associated with the account
* `Reference` — Optional value that can be useful when searching for an account

To retrieve information on the account without moving from the summary page, click on the dropdown arrow next to the account `Name`:

![Customer Accounts Detail View](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/V8OxV4y7ACbYA4VNirUo/Zuk3ArSx1iPQr_e3gTAkj_image.png)


---

# 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/customer-accounts.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.