> 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

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**

<figure><img src="/files/zhryarkODhNk6yWiCaqA" alt="" width="350"><figcaption></figcaption></figure>

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:

<figure><img src="/files/sAtj9GdSJ5I3L7IgEXCe" alt="" width="347"><figcaption></figcaption></figure>

Additionally, you can control which fields are present to create or update:

<figure><img src="/files/5eVyZmBhD5jvHCu1bhck" alt="" width="351"><figcaption></figcaption></figure>

⚡ **Form Actions**

Each form has a Create or Update Action on the Submit button and a Link Action to the previous screen.

### **Icon Component**

<figure><img src="/files/rzAn8NETKzMNHmGsu9hg" alt=""><figcaption></figcaption></figure>

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.adalo.com/feature-templates/classes-admin-dashboard/admin-create-clinic-and-admin-edit-clinic-screen.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
