> ## 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.

# Child forms

> Let respondents create or edit linked records through an embedded form without leaving the main form.

## What child forms are

A child form is a full Filla form scoped to a linked table. It opens inside the main form as a nearly fullscreen modal when a respondent wants to create a new linked record or edit an existing one.

Child forms let respondents manage related records without navigating away. For example, on a project intake form, a respondent could create a new client record on the spot and immediately link it, all within a single form session.

## Setting up child forms

Child forms are configured on the linked record field. Open the field settings and look for the **Create linked records** and **Edit linked records** sections.

### For creating new records

<Steps>
  <Step title="Enable creating">
    Toggle **Enable creating** on in the linked record field settings.
  </Step>

  <Step title="Open the child form editor">
    Click **Form to open for creating**. A full form editor opens, scoped to the linked table.
  </Step>

  <Step title="Start from the generated starter form">
    If no child form exists yet, Filla creates one automatically with the linked table's primary field already added. You can use it as-is or expand it with more fields and pages.
  </Step>

  <Step title="Build the child form">
    Add fields to the child form the same way you would a regular form. Configure labels, required fields, and validation.
  </Step>

  <Step title="Save and close">
    Save the child form. It is now embedded in the parent form.
  </Step>
</Steps>

### For editing existing records

<Steps>
  <Step title="Enable editing">
    Toggle **Enable editing** on in the linked record field settings.
  </Step>

  <Step title="Open the child form editor">
    Click **Form to open for editing**. A form editor opens for the linked table.
  </Step>

  <Step title="Use the generated starter form if needed">
    If you have not configured an edit child form yet, Filla starts you with a minimal child form that already contains the linked table's primary field.
  </Step>

  <Step title="Build the edit form">
    Add the fields you want respondents to be able to edit on the linked record.
  </Step>
</Steps>

## Theme inheritance

Child forms automatically inherit the parent form's theme — colors, font, button style, and card background. There is no separate theme configuration for child forms. When you change the parent form's appearance, all child forms update to match.

This ensures a consistent visual experience when respondents move between the main form and child forms.

<Info>
  Child forms do not display the parent form's header image. The child form modal has its own header with a themed close button.
</Info>

## Child form capabilities

Child forms support the same features as any other Filla form:

* All field types
* Widgets (text blocks, sections, signatures, location capture)
* Multi-page layouts
* Conditional visibility on fields
* Custom submit button label (configurable in the child form's settings sidebar)

Child forms do not support their own on-submit automations or thank you page redirects. They are modal overlays within the parent form flow.

## Nested child forms

Child forms can contain their own linked record fields with child forms, allowing multi-level nesting. Instead of opening stacked modals, Filla uses a **breadcrumb navigation bar** at the top of the child form modal. Each level shows the linked record field name in the breadcrumb trail, so respondents always know where they are and can navigate back to any level.

For example, a project form might link to a client form, which itself links to a contacts form. The respondent sees a breadcrumb like: **Client** > **Contact** and can click any breadcrumb to go back.

## Disabling record search

Enable **Hide record search** to remove the search input from the linked record picker entirely. Respondents can no longer browse or search existing Airtable records from that field.

This setting is separate from child-form creation. You can disable search and still allow creation, or disable search without enabling creation if the field should only show prefilled or session-created links.

Use this when the linked table is entirely managed through the form and you don't want respondents browsing existing records.

## Session-scoped record visibility

Enable **Only show records created in this form submission** to limit the picker to records created during the current session. If a respondent creates a new record through the child form, that record immediately appears in the picker, but records from previous submissions are not shown.

This is useful in multi-step flows where one field creates a set of records that a later field links back to.

## Common questions

<AccordionGroup>
  <Accordion title="Can a child form have its own child forms?">
    Yes. Child forms can nest to multiple levels. Filla replaces stacked modals with a breadcrumb navigation bar so respondents can move between levels without losing context.
  </Accordion>

  <Accordion title="Is the child form's data saved before the main form is submitted?">
    Yes. When a respondent creates a record through a child form, that record is saved to Airtable immediately. If the respondent abandons the main form without submitting, the linked record still exists in Airtable.
  </Accordion>

  <Accordion title="Can I use the same child form for both create and edit?">
    You can configure separate child forms for creating and editing. They don't have to be the same. The edit form might show more fields than the create form.
  </Accordion>
</AccordionGroup>