> 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/community/school-onboarding.md).

# School onboarding

Get a school from empty tenant to usable operations using what’s **shipped**: the web **onboarding wizard** and **Toshi** in the dashboard.

Live product: [klassapp.xyz](https://klassapp.xyz) · Help: <community@klassapp.xyz> · [Book a session](/klassapp-documentation/docs/community/book-onboarding.md)

***

## Paths

| Path                  | When to use                                                       |
| --------------------- | ----------------------------------------------------------------- |
| **Self-serve wizard** | You have an admin account and can enter school structure yourself |
| **Toshi-assisted**    | Same wizard goals, conversational help in the dashboard panel     |
| **Booked session**    | You want KlassApp staff to walk through with you                  |

Guided Toshi / wizard flows work **without** enabling free-form LLM chat. Free-form chat is a separate, gated capability — see [`docs/roadmap.md`](/klassapp-documentation/docs/roadmap.md).

***

## Typical setup order

1. **School + academic year** — name, logo optional, current year
2. **Terms** — any number/names; the product model is configurable (sensible defaults are the intended UX direction; schools can edit)
3. **Classes / streams** — sections are the real class identity (`section_id`), not grading bands alone
4. **Teachers** — create accounts; optional **class-teacher invite by email** (Phase 1 shipped)
5. **Students + parent links** — roster import or manual; parent WhatsApp linking via requests/approvals
6. **Fees** — structures and amounts for the year/term
7. **Plan** — Freemium, Growth (**$35** / cycle), or Premium (custom)

Exact wizard step names can evolve; this is the operational order that matches how schools go live today.

***

## After go-live

* Mark attendance and publish results as usual
* Parents message WhatsApp once linked
* Use Toshi for known flows; keep humans in the loop on sensitive actions

Ongoing product direction (invites Phase 2, WhatsApp OAuth linking, etc.): [`docs/roadmap.md`](/klassapp-documentation/docs/roadmap.md).

***

## Plans (reminder)

| Plan     | Price           |
| -------- | --------------- |
| Freemium | Free            |
| Growth   | **$35** / cycle |
| Premium  | Custom          |

***

## Need a walkthrough?

[Book onboarding](/klassapp-documentation/docs/community/book-onboarding.md) or email <community@klassapp.xyz>.


---

# 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/community/school-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.