Overview — Screens, Database, Layout Settings, Use Cases
Add an admin portal to your app with functionality to create and edit classes, as well as a dashboard view to monitor transactions.
The Classes Admin feature template is a great addition to any app where employees will need to manage data, such as classes. An administrative feature to an app is perfect for companies who do not want to expose all data within Adalo to their employees and instead want to control the creation & updates related to data.
Screens Overview
📚 Instructions Screen
Quickly get an overview of the template with quick tips, a help doc, and associated templates that may be of interest. This screen may be deleted at anytime.
Admin Screens
Admin Screens are accessible to users who have permission to view and interact with those screens.
👩🏾💻 Admin Manage Clinics Screen
Review available clinics or classes offered from this screen with options to add, edit, or delete each offering.
🏦 Admin Transactions Screen
Review and monitor all transactions in a dashboard view with associated table of data.
⚒️ Admin Create Clinic Screen
Add a clinic to the roster or class offerings. This is where an Admin will create new classes to offer in the app.
🔄 Admin Edit Clinic Screen
Update an existing clinic or class through the Admin Edit Clinic Screen.
Database Overview
The Browse Classes Feature Template comes with a database that contains sample data. Each Adalo database contains Collections and each collection comes with the associated Properties. Any necessary relationship between the collections is set up, as well.
Important Note About the Database:
If you delete a Collection or Property from the Feature Template, this could impact the functionality of your app.
If you add a Collection or Property to your Feature Template, this will not impact the functionality of your app.
Below is an outline of the included Collections and their Properties. The Collection name is bolded and includes a description. The Properties include their name, property type (in brackets), and a description.
Basic Collections & Properties:
👥 Users
The Users Collection automatically comes with every Adalo app. This collection will hold all the information related to anyone who uses the app. This information is initially collected from a user when they sign up to use your app.
Email [Text] — the user’s email address.
Password [Encrypted] — the user’s password which is not visible to anyone, including Admins.
Username [Text] — a user’s username, set by the user.
Full Name [Text] — the user’s first and last name, collected during sign up.
Transactions [One-to-Many Relationship] — the transactions associated with a user. These are collected if you have a payment feature inside your app.
Profile Photo [Image] — a user’s profile photo. This is not automatically collected during sign up, but can be via the sign-up form.
Admin? [True/False] — this is a boolean property to denote whether or not someone is an admin in your app.
💳 Transactions
This collection contains all the information related to purchases made in your app. There are no actions inside this feature template that create data for this collection — however, the sample data populates the “Admin Transactions” screen.
Name [Text] — a Unique Identifier for the Transaction. In this case, the user’s name & the class name they purchased.
Status [Text] — the Transactions status, such as “Success,” to denote a successful payment.
Purchased Class [Many-to-One Relationship] — a relational field where many transactions can belong to one class, however, one transaction cannot have many classes.
Purchased by User [Many-to-One Relationship] — a relational field where many transactions belong to one user, however, one transaction cannot belong to many users.
Cost [Number] — the payment cost for the class and its associated fees.
🧱 Categories
The Categories Collection holds information about each of the various categories the classes belong to.
Name [Text] — this refers to the name of the Category.
Short Description [Text] — a brief, one-line description of the Category.
Long Description [Text] — a longer description of the Category that can be used on the details screen.
Classes [One-to-Many Relationship] — One Category can belong to Many Classes, however, each Class only belongs to one Category.
🧑🏾🏫 Classes
The Classes Collection is all the information about each class that a customer or client might care about.
Name [Text] — the title of the class.
Primary Image [Image] — an image related to the class used in promotions.
Category [Many-to-One Relationship] — Many Classes can have One Category, however, each Class only belongs to One Category.
Short Description [Text] — a brief description of the Class.
Long Description [Text] — a long description of the Class that can be used for the details screen.
Starting Time [Date & Time] — the date and time that the Class begins.
Ending Time [Date & Time] — the date and time that the Class ends.
Total Time [Number] — the total amount of time the Class takes.
Location [Text] — the address for where the Class takes place.
Price [Number] — the amount it costs to participate in the Class.
Total Possible Spots [Number] — how many spots are open for clients or customers before a class is full.
Available Spots Remaining [Number] — the number of spots left once people have begun signing up.
Publicly Available? [True/False] — whether or not the class is available to be viewed by users. TRUE means that it is available.
Layout Settings
Each screen in the Browse Classes Feature Template is created using responsive design. The screens will look good on any device or tablet.
Most screens have been designed with Custom Layouts. If you add a new component to a screen, you might notice that the other screen sizes are impacted.
Layout Overview
To view or edit the layout for different screen sizes — click the Screen title to reveal the dropdown.
The default view for this template is Desktop. When you change the screen size for one screen in the Builder, it does not change the screen size of the rest of the screens on the canvas.
Hidden Components
In each view, there may be components that do not appear on Desktop, but are visible on Mobile. These are grayed out in the lefthand panel & denoted with an icon.
Another way to view which device components are visible on is the Layout Tab here:
Custom Layout
Some components come with custom layouts based on screen size. To view those settings, check the Layout Tab & scroll to the Custom Layout Settings.
Example Use Cases
Manage property listings for a Rental Property association.
Create new class listings for a Fitness business or club.
Edit class and workshop offerings for a recreation center.
and many more!
Last updated
