> For the complete documentation index, see [llms.txt](https://help.activenow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.activenow.io/en/online-sign-ups/course-not-showing-in-sign-up-form.md).

# Course Not Showing in the Sign-Up Form

If a course isn't appearing in the registration table or the Client Panel, check two things.

## Check the number of available spots

A course with no available spots won't show in the sign-up form. Go to the course view and open the ***Participants*** tab — you'll find the number of available spots listed there.

{% hint style="info" %}
If the course is full but you still want to collect interest, you can enable a waiting list for it — full courses with a waiting list appear in the form and accept sign-ups from people who want to be considered if a spot opens up. Read more about it [here](/en/online-sign-ups/waiting-list.md).
{% endhint %}

## Check the online sign-ups setting

A course can be manually disabled from online sign-ups. Go to the ***Courses*** tab and check the ***Online sign-ups*** column for that course. If the toggle is set to ***No*** — switch it to ***Yes*** to make the course visible in the form again.

You can read more about this setting [here](/en/online-sign-ups/disabling-courses-from-online-sign-ups.md).


---

# 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://help.activenow.io/en/online-sign-ups/course-not-showing-in-sign-up-form.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.