> 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/reports/clients-signed-out-of-courses-report.md).

# Participants Signed Out of Courses

The *Clients signed out of courses* report lets you monitor the scale of drop-outs — how many participants left their courses before the end date and when it happened.

## How to generate the report

1. Go to *Reports → Clients → Clients signed out of courses*.
2. Select the date range.
3. Click *Generate a report*.

![Clients signed out of courses report with date range selection](https://2983515171-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5ksnUuhXGAx5afQd3MB%2Fuploads%2Fgit-blob-63549641947f2c96a6343733738cc23d38bad3d2%2FZrzut%20ekranu%202026-05-26%20124516.png?alt=media)

For each participant the report shows:

* name,
* the course they were signed out of,
* sign-out date,
* course end date,
* instructor.

![](https://2983515171-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5ksnUuhXGAx5afQd3MB%2Fuploads%2Fgit-blob-3a5bcc84961dfb1dfc62729c22e51e5f6c34f63a%2FActiveNow_Raporty%20GoogleChrome2021%2003%2025at3.18.08PM%201024x96.png?alt=media)


---

# 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/reports/clients-signed-out-of-courses-report.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.