> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/ja/feature-templates/appointment-booking/edit-session-screen.md).
# セッション編集画面
Edit Session画面は、コーチが作成した予約に関連する情報を更新するために使用されます。
編集セッション画面は、データベース内のすべての情報を管理できる管理者（またはコーチ）が、予約を作成または更新したい場合に使用されます。このフォームには、予約コレクションからすべてのプロパティが含まれ、編集するために情報が取り込まれます。
コーチはこの画面から予約を削除することもできます。
⚡ **送信ボタンのアクション**
* 予約を更新
* 予約所有者をログインユーザーに設定して更新
* 「戻る」アクションへのリンク
⚡ **削除ボタンのアクション**
* 現在の予約を削除
---
# 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.adalo.com/ja/feature-templates/appointment-booking/edit-session-screen.md?ask=&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.
