Forms
Several forms for your academy, with builder, settings, public link and embed code. Answers land in Requests.
10/10/2026 · preview feature: you see it if it is on for your academy
In Settings › Forms your academy has all the forms it needs: one for course pages, one for the open day, one to embed in your website… Every form has a builder with a live preview, its own settings and its sharing options. Answers always land in the Requests section, with the form name. Owner and Admins manage them.
The forms list
- New form (top right) asks for the name right away and, if you like, a template to start from: Blank, Contact, Course information, Event registration.
- Filter forms… searches by name; Active and Archived switch the list.
- Each row shows the name (clickable), the status (Draft, Published or Unpublished changes), the number of responses, the last update and the menu with See responses, Duplicate, Make default and Archive.
- Forms are never deleted: they are archived and restored from Archived. Requests already received stay linked.
- The default form is the one used by courses that do not choose one: it cannot be archived until you pick another one.
Below the list you still find the academy sales choices: How courses are bought and the course page button text.
Your first form
Your previous single form becomes your first form, Modulo di richiesta, already published and default: same fields (name, email, phone, message, the custom fields placed in "Request form", consent), same thank-you page, same mailbox. If you had chosen different fields for a course, that course gets its own form ("Modulo – course title"). Requests already received are linked to these forms.
The form page
At the top: ← Forms, the name, the status, the Builder, Settings and Share tabs, and on the right Publish and the … menu (Rename, See responses, Duplicate, Make default, Archive).
The draft saves by itself while you work. Your site only shows the published version: after a change the form says Unpublished changes until you press Publish again.
Builder
In the middle the preview, exactly as people filling it in will see it, with the thank-you shown after sending below it. On the right two tabs:
Fields
- Layout: Heading and Paragraph, to give the form a title and explain what happens.
- From a template: Full name, Email, Phone, Message and Privacy consent, which go into the request fields; Attributes… to pick one of the academy custom fields: the value is saved on the person too.
- Regular fields: Short text, Long text, Number, Checkbox, Single choice, Multiple choice and Date. Answers stay on the request.
A click on a tile adds the field (before the consent); you can also drag it onto the preview or into the In the form list, where you drag fields to reorder them. A click on a field of the preview opens it: label, placeholder, help text, required, the options of choice fields, move up/down and delete.
Name, email and consent are needed by every request: they cannot be removed and are always required. Without them the form cannot be published.
Design
Light or dark theme, left or centered alignment, button color (the theme one or the academy one, from Settings › Branding), button width and text, academy logo on or off.
Settings
- After sending: a thank-you message (title, text and button: See more courses, a link of your choice or none) or Redirect to an address over https. From a course page the thank-you opens on /grazie with the same text.
- Email notification for responses: the mailbox of the area (Administration or Teaching of the reply-to) and, optionally, up to 5 extra recipients. Where email templates are on, Template picks the email sent to the staff (among shared templates; Default text = the usual one).
- Confirmation email to the person: on or off, with your "What happens next". With email templates you can instead pick a shared Template with the request variables (
{{ lead.first_name }}, the course, the Attributes…). - Privacy and consent: the privacy policy address; the consent text is written in the builder, on the Privacy consent field.
- URL parameters: with Track URL parameters the form saves the page address parameters on the request (by default utm_source, utm_medium, utm_campaign, utm_content, utm_term). For every parameter key you can choose Map to attribute: the value is also copied on that custom field of the person, unless they wrote it themselves. + Add parameter adds a row, the bin removes it.
- Anti-spam: always on, without captcha (hidden field, filling time, sending limit).
- Webhook to your CRM: every response goes out as a
lead.createdevent with the form (form.id,form.name), the answers and the tracked parameters. Set the webhook up in Settings › Webhooks. - Where it is used: whether it is the default and which courses chose it.
Share
Until the form is published, a notice at the top says "This form is not published yet" and the buttons are off.
- Embed code: Script (the height adapts by itself and the page parameters reach the form) or Iframe (where scripts are not allowed), with Copy code. Paste it in your website page where you want the form.
- Share link: the public address of the form on your site domain (for example
https://youracademy.aladia.io/f/…), to copy or open. People opening it see only the form. - Courses: the courses using this form; Link a course opens a window with title search and picks it for a course, the × brings the course back to the default.
The form of a course
In the course builder, under Pricing › How it is bought, below the modes there is Request form: Workspace default or one of the published forms. It applies right away, even on published courses. The course opens the form in a dialog, or on its own page when it has many fields.
The answers
Every answer is a request in the Requests section: the Form column and filter tell which form it comes from (from See responses the table opens already filtered). In the detail you find the form, the answers to regular fields and the tracked URL parameters.