> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/docs-site/help/admins/onboarding.md).

# Onboarding paths

· 20 minutes

## Set up the school

After an invite, you choose the Wizard or Toshi. Both cover the same steps: school details, classes, subjects, teachers, students, terms, fees, WhatsApp, and plan.

### Choose a path

The choice page heading is **How would you like to set up** your school.

Choose Set up step by step. This opens the Wizard. Use it when you already have the class list and the fee structure.

Guided chat stays off on this path. The panel can say **Coming soon** and **Meet Toshi**. That is expected.

Choose Set up by chatting with Toshi. Toshi, KlassApp's assistant, asks one question at a time and saves each answer. Guided setup does not need an AI key, and it does not turn the free-form assistant on.

You land on the dashboard with Toshi open. The checklist title is **Completing Setup**.

You can change paths later. The dashboard banner is **Finish school setup**. **Set up manually** is always there. **Set up with Toshi** appears only while guided setup is on.

A school that signed up without an invite does not see this choice page. Use the same banner.

### Wizard steps

Choose Continue → after each step. On the review step choose Confirm & finish. **Teachers** and **Students** also offer Skip for now.

Steps every school sees, in order:

1. **School name**
2. **Approximate school size** — **Up to 500**, **Up to 1,000**, or **More than 1,000**
3. **Country**
4. **Board / Curriculum**
5. **Academic year**
6. **Structure & Class Teachers**
7. **Subjects**
8. **Teachers** (optional)
9. **Students** (optional)
10. **Academic terms** — three terms are filled in. Change the names and dates to match your school.
11. **Fee structures**
12. **WhatsApp verification**
13. **Plan selection**
14. Review, then Confirm & finish

A few extra steps appear only when your country or curriculum needs them: **School category**, **EMIS / Ministry code**, and **UNEB centre number**. If you do not see them, they do not apply. You can leave the exam centre number blank.

On **Teachers** and **Students** you can choose **Upload file**, **Paste names (one per line)**, **Add from paste**, or add one person. Students also have **Download template**.

When setup is done the screen says your school **is ready**. Choose Go to dashboard.

A line on some steps says **Prefer the full admin form?** and **Open** that step. That link is the same data, on the full admin page.

### After setup

In the menu, open . You can edit:

* **School details**
* **Academic years and terms**
* **Data exports**

**Settings** is only on the school admin menu. A head teacher does not see it.

### Add people next

[Add students](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/add-students/README.md) from . Parents then use [WhatsApp](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/parents/whatsapp/README.md). Link requests land on [Link requests](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/admins/link-requests/README.md).

::: info Note There is no in-app page to book a setup call. Email <community@klassapp.xyz> if you want a person to walk through setup with you. :::


---

# 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://klassdocs.gitbook.io/klassapp-documentation/docs-site/help/admins/onboarding.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.