> 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/coach-admin-screen.md).
# Coach Admin Screen
The Coach Admin Screen allows coaches to create appointments, view open appointments, & review booked appointments for optimal scheduling management.
The Coach Admin Screen can only be accessed via the ‘Coach Portal’ button on the ‘Coaches’ Screen. That button can only be seen if a user is marked TRUE in the Admin? property in the Users Collection.
This feature template is known as a two-sided app. In other words, there is a side for Admins to control information and there is a side for users to interact with that information.
This screen is the first screen on the Admin side of the app.
## The Components
### **Open Slots Group**
The Open Slots group displays a list of appointments that are related to the Logged In User where Booked = FALSE and the Date & Time is after the current time.
Each list item can be opened and edited by clicking on the item.
⚡ **List Actions**
* Link Action to the ‘Edit Session’ Screen
⚡ **Button Actions**
* Create Appointment
* Link Action to the ‘Edit Session’ Screen
### Booked Slots Group
The Booked Slots Group shows a list of appointments that have been booked & the date & time are at some point in the future.
Each list item can be opened and edited by clicking on the item.
⚡ **List Actions**
* Link Action to the ‘Edit Session’ Screen
---
# 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/coach-admin-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.
