> 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.md).

# KlassApp Community

**Educationists' tools connected by intelligence.**

KlassApp is a multi-tenant school management platform, built first for the hardest real-world constraints — limited bandwidth, everyday phones — which is what makes it work anywhere schools need it.

* **Schools** run academics, fees, attendance, exams, and staff workflows in one web product.
* **Toshi** — KlassApp's AI agent — helps finish setup and keep work moving in the dashboard.
* **Parents** get answers on **WhatsApp** (Meta Cloud API) without installing another school app.

Live product: [klassapp.xyz](https://klassapp.xyz) · Demo access: <community@klassapp.xyz>

***

## This content has moved

This community documentation is now published on **GitBook** with real-time sync from this repository:

**→** [**KlassApp Documentation on GitBook**](https://klassdocs.gitbook.io/klassapp-documentation/)

The GitBook site is kept in sync via GitHub Sync — changes to these files in the repo automatically appear on GitBook, and edits in GitBook's editor create commits back to the repo.

***

## What's here (legacy Docsify copy)

| Page                                                                             | For                                                 |
| -------------------------------------------------------------------------------- | --------------------------------------------------- |
| [For schools](/klassapp-documentation/docs/community/for-schools.md)             | Admins and staff — what the product does today      |
| [School onboarding](/klassapp-documentation/docs/community/school-onboarding.md) | Getting a school live (wizard + Toshi)              |
| [Book onboarding](/klassapp-documentation/docs/community/book-onboarding.md)     | Request help from the KlassApp team                 |
| [For parents](/klassapp-documentation/docs/community/for-parents.md)             | WhatsApp menus parents can use once linked          |
| [Ecosystem](/klassapp-documentation/docs/community/ecosystem.md)                 | Product model: WhatsApp live; Drive/Slack in the UI |
| [Roadmap](/klassapp-documentation/docs/roadmap.md)                               | Honest public direction (canonical)                 |
| [FAQ](/klassapp-documentation/docs/community/faq.md)                             | Common questions                                    |

Direction and backlog live in [`docs/roadmap.md`](/klassapp-documentation/docs/roadmap.md) — not restated here.

***

## Plans (shipped)

| Plan         | Price                   | Notes                          |
| ------------ | ----------------------- | ------------------------------ |
| **Freemium** | Free                    | Entry tier for getting started |
| **Growth**   | **$35** / billing cycle | Standard paid tier             |
| **Premium**  | Custom                  | Contact sales                  |

Amounts match the live `plans` seed (`PlansTableSeeder`).

***

*Open source (MIT). Production SaaS on Laravel Cloud.*


---

# 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.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.