> 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/client-management/inviting-participants-to-the-client-panel.md).

# Inviting Participants to Register

Inviting participants to register in ActiveNow gives them access to their own panel, where they can:

1. **Payments** — quick settlements via online payments.
2. **Absence reporting** — when a child can't attend a class.
3. **Making up absences** — easy and fast sign-up for available make-up slots.

## How to invite participants

Go to the *Participants* tab and select the participants you want to invite — or select all of them. Then choose *Mass action* → *Invite to ActiveNow*.

![Participants list with selected participants and Mass action dropdown showing Invite to ActiveNow option](https://2983515171-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5ksnUuhXGAx5afQd3MB%2Fuploads%2Fgit-blob-b698e1da276717d35279fd8b5c2fb7a7f424340c%2FZrzut%20ekranu%202026-05-25%20131458.png?alt=media)

The system will automatically send them an email with a registration invitation. Once they click the link in the email, they can create an account and start using the ActiveNow Client Panel.


---

# 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/client-management/inviting-participants-to-the-client-panel.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.