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

# Review approvals

· 3 minutes

## Review approvals

Staff leave, parent-link requests, lesson plans, and tasks wait here until you approve or reject them.

### Open the inbox

In the menu, choose .

The heading is **Approvals**. The line under it is "Review and manage pending requests from staff."

Three counts sit at the top: **Pending**, **Approved**, and **Rejected**.

The table columns are **Type**, **Requester**, **Status**, **Comments**, **Requested**, and **Actions**.

An empty inbox says **No approval requests yet**.

### Act on a request

On a pending row, choose Approve. Confirm **Approve this request?**

Choose Reject. The reason field says **Reason required...**. Choose Confirm.

A parent-link row is labelled **Parent link (WhatsApp)**. Approving it links the number. Rejecting it tells the parent. You can also handle those cards on [Link requests](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/admins/link-requests/README.md).

### What this inbox does not release

Marks are not released from this inbox. **Release marks** is a separate item under . The step-by-step marks guide is still a [placeholder](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/marks/README.md).

::: info Note Only a person at your school can approve a request for your school. Approving does not change another school's records. :::


---

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