> 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/classes-admin-dashboard/admin-create-clinic-and-admin-edit-clinic-screen.md).
# Admin Create Clinic & Admin Edit Clinic Screen
The two screens to create & edit classes that are available from the admin side of an app are called the Admin Create Clinic Screen and the Admin Edit Clinic Screen.
Both the ‘Admin Create Clinic’ Screen and the ‘Admin Edit Clinic’ Screen are for administrators to either create classes or to edit classes that have already been created.
These screens allow users to manage data in the app without logging into Adalo. This is perfect for businesses who have several employees, but not all employees need access to the Adalo Builder.
## The Components
### **Form Component**
The predominate component on these two screens in the form component. The form component pulls the input fields from the Collection that it references.
On these two screens, the data collection is the ‘Classes’ collection.
For each form, you have the option to:
Additionally, you can control which fields are present to create or update:
⚡ **Form Actions**
Each form has a Create or Update Action on the Submit button and a Link Action to the previous screen.
### **Icon Component**
Each screen has an icon component to exit the screen without creating a new class or editing information.
⚡ **Icon Action**
A Link Action to the previous page.
---
# 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/classes-admin-dashboard/admin-create-clinic-and-admin-edit-clinic-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.
