> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/mac-fundamentals/settings/mac-settings/primary/forms-settings.md). # Forms Settings Build the Form templates your Daylite team uses to capture structured information, choose which record types each Form appears on, and define its fields and field types. The **Forms** settings pane is where you build the form templates your team uses to capture structured information on records — and define the fields each form collects. A form is a reusable set of fields you can fill in on a Person, Company, Opportunity, Project, and more, so the same details get captured the same way every time. It sits under **Primary** in Settings, so forms are shared across the database and used by everyone. **Key facts:** * A **Form template** defines the structure: the fields, their types, and which record types the Form applies to. * A **Form** is a record. It holds data, can be linked to other records, can have files attached, and can carry Keywords. * Form templates are shared across the database and apply to all users. * Building a form is two jobs: setting up the **template** (its name, description, and which record types it's available from) and defining its **fields** (each field's name and type). * Retire a form with its **Active** checkbox rather than removing it, to take it out of use without disturbing forms already filled in. ## How To Create a Form Template 1. Go to **Daylite > Settings > Forms**.

2. Click **+** to create a new template from scratch.

3. Alternatively, select an existing template and click **Duplicate** to start from a copy. 4. Enter the Template's **Form Name** 5. Add a **Desscription**. 6. Select which record types this Form applies to — People, Companies, Opportunities, or Projects. This determines where the Form appears. For example, a Form assigned to People only appears as an option on People records. 7. Check the **Active** checkbox to make the template available. ### The Forms List The left column lists every form template in your database and is where you add, remove, and duplicate them. {% columns %} {% column %}

{% endcolumn %} {% column %} 1. **Browse your forms.** Each row shows a form template and, beneath it, the record types it can be created from (People, Companies, Opportunities, and so on). 2. **Select a form to edit.** Click a form to load its fields in the middle column and its settings in the right panel. 3. **Add, remove, or duplicate.** Use **+** to create a new form and **−** to remove the selected one. **Duplicate** copies an existing form so you can build a variation from it. {% endcolumn %} {% endcolumns %} ### Form Settings With a form selected, the right panel shows the template's own settings. {% columns %} {% column %} 1. **Form Name.** What the form is called wherever it's offered. 2. **Description.** An optional note about what the form is for. 3. **Active.** Whether the form is available for use. Unchecking it retires the form without affecting records that already have it filled in. 4. **Create from.** The record types the form can be created on — **People**, **Companies**, **Projects**, **Opportunities**, **Groups**, **Task**, **Appointment**, **Note**, and **Email**. Tick the ones where this form should be available; the form only appears as an option on those record types. {% endcolumn %} {% column %}

{% endcolumn %} {% endcolumns %} ### Form Fields The middle column lists the fields on the selected form. With a field selected, the right panel shows that field's settings.

1. **The field list.** Each field shows its name and its type (Text, Multiple Checkboxes, Popup Options, and so on), in the order they appear on the form. 2. **Add or remove a field.** Use **+** below the field list to add a field and **−** to remove the selected one.

Before changing a field type or deleting a field, confirm that you do not need the existing data. Both actions are irreversible and affect all Form records created from the template, including historical records.

3. **Field Name** and **Description.** Name the field as it should read on the form, with an optional description. 4. **Type.** Choose how the field captures data The type decides how the field is filled in and how you can filter on it later. For more details read [Form Field Types](#form-field-types). 5. **Options -** When you select a field that has multiple options, you will enter your choices here by typing in the field and hitting return. 6. **Sort Alphabetically.** When you select a field that has multiple options, you can choose to sort alphabetically. You can also reorder by dragging and dropping. 7. **Default Value.** A value each new form will start with. ### Form Field Types Each field in a Form template has a Name, an optional Description, and a Type. Daylite supports 11 field types:

Type	Description
Text	A text box. Suitable for long-form comments or non-standard responses.
Popup Options	A pop-up menu of mutually exclusive choices, shown when clicked. You define the options in the template. Useful for single-choice standardized options.
Combo Box Options	A text field combined with a pull-down list. Choose a predefined value or type a custom one; custom values are not added to the list. Useful for single-choice standardized options with an "Other" option.
Number	Any positive or negative whole number, without decimal points. Useful when you do not want to store decimals.
Decimal Number	Any number, including decimals. Useful for values that may contain decimal points.
Currency	A number with up to two decimal places. Currency formatting follows your system settings.
Date	Month, day, and year, with a date picker.
Time	Time in 12-hour or 24-hour format, based on your system settings.
Date & Time	Date and time combined.
Checkbox	A two-state toggle: on when checked, off when empty. Useful when there are only two possible options.
Multiple Checkboxes	A set of preset values where each option can be selected independently. Useful when multiple choices may apply.

## Frequently Asked Questions **What does "Create from" control?** It sets which record types offer the form. Tick **People** and **Companies**, for example, and the form can be created on a Person or a Company but not on a Project. It doesn't change the form's fields — only where the form is available. **What field types can a form use?** Text, Popup Options, Combo Box Options, Number, Decimal Number, Currency, Date, Time, Date & Time, Checkbox, and Multiple Checkboxes, among others. Pick the type that matches the answer — a Popup or Multiple Checkboxes for set choices keeps data consistent and filterable, where free Text does not. **Should I delete a form I no longer use?** Usually not. Uncheck its **Active** state instead — that takes it out of use for new records while leaving forms already filled in untouched. **How do I build a form similar to an existing one?** Select it and click **Duplicate**, then adjust the copy. This carries over the fields so you're not rebuilding from scratch. **Do these settings affect everyone?** Yes. Forms is a Primary, database-wide setting. Changes apply to all users, and you need Administrator or Superuser access to make them. **Why cant I see a Form when I try and filter?** The form is either not applied to that record, or the Form is inactive. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.daylite.app/help/mac-fundamentals/settings/mac-settings/primary/forms-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.