> 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/developer-resources/rest-api/accounts-api/account/state-diagram.md). # State diagram The Marketplace Platform provides three distinct user interfaces, namely the Client Portal, Vendor Portal, and Operations Portal. This topic describes how the account object transitions through different lifecycle states within the platform. {% hint style="info" %} The diagrams show different transitions depending on whether the account is a Client/Partner or a Vendor, but the underlying statuses are the same. {% endhint %} ### Client account The following diagram shows how a client account moves between states like enable, activate, and disable.

The state transition diagram of a client account.

### Vendor account The following diagram shows how a vendor account progresses between states.

The state transition diagram of a vendor account.

State	Definition
New	This is the default state of a newly created account. This state is not visible on the interface.
Enabled	The account has been created, but it has not been fully set up yet in the system. While the account can be used for transactions, these transactions will not be completed.
Active	The account is fully operational in the Marketplace.
Disabled	The account is not available for transactions, and users cannot sign in or switch to this account.

--- # 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/developer-resources/rest-api/accounts-api/account/state-diagram.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.