> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/events/class-registration.md).

# What Learners see on the Class Registration Portal Page

On the Classes Search page in the Portal, users will see various statuses. The flowchart below illustrates the different statuses visible to users:

On the Classes Search page in the Portal, users will see various statuses. The flowchart below illustrates the different statuses visible to users:

<figure><img src="https://1098692194-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEiUUMcDHYlET5DiA1xJY%2Fuploads%2FuDeMQmWnHHqqQ4vR1bqc%2FClass%20Statuses%20(Portal).jpg?alt=media&amp;token=dd9fb369-0d4d-4dad-bc81-05752d2efea6" alt="Class Statuses (Portal)"><figcaption></figcaption></figure>

During the **Class Registration** process, there are 5 steps the user will move through to complete their registration:

1. Update your account information (*Accounts panel*)
2. Select Employer (*Employer panel*)
3. Choose Payment option - Seat selection (*Class Registration panel*)
4. Enter Payment info (*Payment panel*)
5. Confirm (*Confirm Details & Payment panel*)

In the **Accounts** and **Employer** panels, there are Organization specific settings and fields that can be turned on/off. These settings can **only** be turned on/off by an **Shift iQ administrator**.

Shift iQ Administrator Note: See Confluence for the different settings for the Class Registration page.


---

# 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.shiftiq.com/help/events/class-registration.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.
