---
title: "Creating a Scheduler Registration Form"
slug: "creating-a-scheduler-registration-form"
updated: 2026-04-10T19:09:43Z
published: 2026-04-10T19:09:43Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a Scheduler Registration Form

After a [Scheduler template](/v1/docs/creating-a-scheduler-template) has been created, we can associate a form for registrants to fill out.

Each session associated with the template uses this same form: update the registration form and it updates for all associated availability slots.

On the management page for your Scheduler template, select **Edit Form**.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Edit form.png)

In the Edit Form page, add form fields as needed to collect required information for the session.

## Form scope

A Scheduler registration form’s **scope** determines who can register, how the form can be accessed, and which fields are required on the form as a result.

To modify the form’s scope, select **Edit Properties**.

### Person- or dataset-scoped

If you set the scope of the interview registration form to **Person** or **Dataset**, you need to determine if the form should be accessible to anyone, or only to people with an existing login.

#### Require a login

If you decide the form should require a login, select **Require secure link/login**.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Person scoped form - require login.png)

If you require login, you **don’t need to include matching fields**like `First Name`, `Last Name`, `Email Address`, and `Birthdate` on the registration form.

#### Allow public access

If you decide the registration form should be publicly accessible, remember to **include registration form fields that Slate can use to create a new record**or match to an existing record, for example: `First Name`, `Last Name`, `Email Address`, and `Birthdate` for person records.

### Application-scoped

By contrast, **Application-scoped**Scheduler template forms always require registrants to sign in before they can access the form, so you **don’t need to include matching fields**like `First Name`, `Last Name`, `Email Address`, or `Birthdate` on the registration form.

## Including Scheduler slots as related events

If events include the use of related events, consider adding Scheduler slots as a **related event.**

From the form palette, select **Related Events Selector.**

there is no need to customize the registration form for the Scheduler template or make a unique Event Landing Page since registration will occur through the main event template.

📖 **Further reading:**[Related Events Selector](/docs/related-events#create-the-master-template)

## Form-User merge fields

Consider using Form-User merge fields within the registration form communications. For example, if the user is pre-assigned, an “Upon Registration communication” to registrants can come directly from the host of the appointment or interview.

If users are assigned at a later date, an “Hours before deadline” communication to registrants can contain this information. Also, consider making a separate reminder communication to users that includes a link to the report form `{{Form-Report-Link}}`.

## Next up: Connecting external calendars to Slate

With a template and a form in hand, pave the way for establishing availability by having your appointment facilitators add their calendars to Slate.

> [!NOTE]
> ➡️ [Connecting External Calendars to Slate](/v1/docs/slate-external-ical-integration)