> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/guest/ja/xue-xiao.md).

# 学校

- [学校向け Guest タイプ](https://help.verkada.com/guest/ja/xue-xiao/school-guest-types.md): 最新の生徒および保護者情報を使用する Guest タイプをカスタマイズ
- [生徒リストを管理](https://help.verkada.com/guest/ja/xue-xiao/manage-student-lists.md): Workplace で生徒と関連する保護者のリストを直接確認
- [ClassLink を Verkada Guest と統合](https://help.verkada.com/guest/ja/xue-xiao/integrate-classlink-with-verkada-guest.md): 生徒管理のために ClassLink Roster Server を Verkada Guest に接続
- [Clever を Verkada Guest と統合](https://help.verkada.com/guest/ja/xue-xiao/integrate-clever-with-verkada-guest.md): Verkada Guest と Clever のシームレスに統合を設定
- [Verkada Guest を PowerSchool に接続](https://help.verkada.com/guest/ja/xue-xiao/connect-verkada-guest-to-powerschool.md): 最新の生徒および保護者情報を取得し、Guest で遅刻を追跡


---

# 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.verkada.com/guest/ja/xue-xiao.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.