> 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/program/enrollments/enrollment-states.md). # Enrollment states Learn about the different states of an enrollment. Enrollment is the process of registering for a program. An enrollment can be in one of these states: **New**, **Processing**, **Querying**, **Complete**, or **Failed**. The following diagram shows the transitions between these states:

The state transition diagram of an enrollment.

The following table describes the different states:

State	Definition
New	This is the initial status for newly created enrollments in the platform.
Processing	The enrollment has been submitted, and it's undergoing approval processing.
Querying	The vendor requires more information to process your enrollment.
Complete	The vendor has approved your enrollment and activated your certificate.
Failed	The vendor has rejected your enrollment request.

--- # 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/program/enrollments/enrollment-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.