> 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/feature-templates/appointment-booking/edit-session-screen.md).
# Edit Session Screen
The Edit Session screen is used update the information related to an appointment that is created by a coach.
The Edit Session Screen is where all the information in the database can be controlled by the Admin (or coach) that would like to create or update an appointment. This form contains all the properties from the Appointments Collection and pulls the information in to be edited.
The coach is also able to delete the appointment from this screen, as well.
⚡ **Submit Button Actions**
* Update Appointment
* Update AppointmentOwner set to Logged in User
* Link Action “Back”
⚡ **Delete Button Actions**
* Delete Current Appointment
---
# 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/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.
