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

# Login pages

> Gate access to your form with lookup, email, or password authentication.

## What a login page does

A login page is an authentication gate placed before the form. Respondents must identify themselves before they can see or fill out any form pages. Login pages are the foundation of [edit mode](/docs/edit-mode/how-edit-mode-works) and access-controlled forms.

## Verification modes

Login pages support three verification modes. Each mode changes how the respondent authenticates and what happens next.

### Lookup

Respondents enter one or more values (email, order number, employee ID) that Filla looks up in your Airtable table. If a matching record is found, it loads into the form for editing.

**How to configure:**

1. Add a login page to your form
2. Set the verification mode to **Lookup**
3. In the sidebar, use the **multi-field picker** to select which fields the respondent enters to find their record

The field palette on a lookup login page shows layout widgets only. Fields you select in the multi-field picker are automatically added to the login page as input nodes. Removing a field from the picker removes it from the page.

<Info>
  Lookup, collaborator, linked record, and computed fields are filtered out of the login field pickers since they cannot be used as lookup identifiers.
</Info>

**Use cases:** Update forms where respondents look up their own record by email or order ID, employee self-service portals, customer data review forms.

### Email

Respondents enter their email address and verify it with a one-time code sent to their inbox (OTP). Once verified, Filla looks up the matching record by that email field.

**How to configure:**

1. Add a login page to your form
2. Set the verification mode to **Email**
3. Use the **single field picker** in the sidebar to select an email-compatible field (fields with email-like types are shown)

**How the flow works for respondents:**

1. The respondent enters their email address
2. Filla sends a 6-digit verification code to that email
3. The respondent enters the code on the form
4. If the code is valid, Filla looks up the record matching that email and loads it into the form

The field palette in email mode only shows layout widgets (sections). The login fields are managed through the field picker in the sidebar.

**Use cases:** Identity verification before form access, email-gated content or surveys.

### Password

Respondents enter a shared password that you set. No Airtable record lookup happens.

**How to configure:**

1. Add a login page to your form
2. Set the verification mode to **Password**
3. Enter a password in the sidebar. The password is stored as a hash for security.

The field palette in password mode only shows the password widget. No Airtable field pickers are available.

**Use cases:** Password-protected forms for internal use, gated access forms shared with a specific group.

## Custom login instructions

Each login page has a **Login instructions** text field where you can write custom instructions for respondents. For example: "Enter the email address you used when you registered."

When the instructions field is left blank, Filla shows default instructions based on the verification mode.

## Login page settings

| Setting                | Description                                    |
| ---------------------- | ---------------------------------------------- |
| **Title**              | The heading shown at the top of the login page |
| **Description**        | Optional text below the title                  |
| **Verification mode**  | Lookup, Email, or Password                     |
| **Login instructions** | Custom instructions for respondents            |

## Login pages and edit mode

Login pages work together with edit mode. When a respondent authenticates via lookup mode and a matching record is found, the form loads that record's data into the form fields. The respondent can then update the record and resubmit.

See [How edit mode works](/docs/edit-mode/how-edit-mode-works) and [Sharing edit links](/docs/edit-mode/sharing-edit-links) for more on this workflow.

## Common questions

<AccordionGroup>
  <Accordion title="Can I have more than one login page?">
    No. A form can have only one login page, and it must be the first page in the form.
  </Accordion>

  <Accordion title="Can I combine login with conditional pages?">
    Yes. After the login page, subsequent form pages can use display conditions as normal. The respondent authenticates first, then navigates through conditional pages.
  </Accordion>

  <Accordion title="What happens if the lookup finds no matching record?">
    The respondent sees an error message and cannot proceed. They need to enter values that match an existing record in your Airtable table.
  </Accordion>

  <Accordion title="What happens if multiple records match?">
    If more than one record matches the lookup values, Filla uses the first matching record. The respondent is not shown an error.
  </Accordion>
</AccordionGroup>