Overview — Screens, Database, Layout Settings, Use Cases

Create Terms & Conditions and collect signatures for acceptance of those terms with the Agree and Sign Feature Template

The Agree & Sign feature template is the perfect addition to any business where customers need to accept Terms and Conditions before continuing use — whether it’s for renting equipment, a waiver for participation, or something else entirely. Quickly set up your Terms & Conditions signature flow with this feature template.

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.

User Screens

These screens will be interacted with by the customers or clients of your app.

📝 Terms Screen

A screen to display the various terms that a customer may need to sign to interact with your business.

✍🏾 Agree and Sign Modal Screen

Collect signatures through touchscreen or mouse to agree to conditions outlined in the terms.

⭐ Congrats Screen

Display a success state to show the customer they have taken the appropriate actions and everything is accepted.

Admin Screens

Admin Screens are accessible to users who have permission to view and interact with those screens.

👨🏾‍💻 Signatures Admin Screen

Review submitted signatures to monitor acceptance of Terms and Conditions.

Database Overview

The Agree & Sign 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 users email address.

• Password [Encrypted] — the user’s password, which is inaccessible to anyone — even administrators.

• Username [Text] — the user’s username.

• Full Name [Text] — the user’s first and last name.

• Signatures [One-to-Many Relationship] — this relational field shows that one user can be associated with many signatures and each signature can only belong to one user.

• Admin? [True/False] — this property is marked TRUE if the user is an Admin of the app, this allows them access to the Admin portions of the app.

• Profile Photo [Image] —the user’s profile picture.

📝 Terms

The Terms Collection holds all information related to the various terms and associated descriptions that you would like the users to sign for.

• Term Heading [Text] — the paragraph heading of the terms and conditions.

• Term Body [Text] — the body text of the terms that is associated with the term heading.

• Term Section [Number] — the order you would like each term to appear in the list of terms.

✍🏾 Signatures

The Signatures Collection holds all the information related to the signatures that are captured in the app.

• Date & Time [Date & Time] — the day and time the signature was submitted.

• Signed by User [Many-to-One Relationship] — this relational field shows that many signatures can belong to one user, however, each individual signature can only belong to one user.

• Signature URL [Text] — the URL associated with the image of the signature that was captured.

• Name of Signee [Text] — the first and last name of the user who signed.

Layout Settings

Each screen in the Agree & Sign 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

• Create Terms and Conditions for renting equipment for a Pickleball Club.

• Require waivers for your athletic event to be signed for participation.

• Collect signatures for business transactions, as needed.

• and many more!