> 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/users/user-states.md). # User states Learn about the different states of a user. A user is an individual with a unique login who interacts with the Marketplace Platform. A user can be in one of these states: **Invited**, **Invitation expired**, **Active**, **Blocked**, **Disabled**, or **Deleted**. The following diagram shows the transitions between these states:

The following table describes the different states:

State	Description
Invited	The user has been invited to the account.
Invitation expired	The user's invitation has expired because they didn't accept it within 7 days from the send date.
Active	The user can access the account and perform operations based on their permissions.
Blocked	The user has been restricted from accessing the account. This could be due to terms and conditions violations, security concerns, or at the administrator's discretion.
Disabled	The user has been removed from the account. They cannot perform any operation in the account.
Deleted	The user no longer exists in the system.

--- # 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/users/user-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.