> 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/licensee-states.md). # Licensee states Learn about the different states of licensees. A licensee is a specific person or a department within your account that receives the license to use the product. A licensee can be in one of these states: **New**, **Active**, **Enabled**, **Disabled**, or **Deleted**. The following diagram shows the transitions between these states:

The state transition diagram of a licensee.

The following table describes the different states:

State	Definition
New	This is the initial status and it's assigned when you are creating a new licensee .
Active	The licensee is currently active, and you can use it when creating new agreements and ordering products.
Enabled	The licensee has been set up in the system, but it can't be used for transactions.
Disabled	The licensee has been disabled and can no longer be used.
Deleted	The licensee has been deleted.

--- # 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/licensee-states.md?ask=&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.