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

# Global Intake Fields

> Define intake fields once in a shared library and reuse them across every flow

Global Intake Fields is a shared library of intake fields that lives under **Settings → Intake Fields**, separate from any single flow. Define a field once — Counterparty Name, Effective Date, Contract Value — and reuse it across every flow's Intake step, instead of rebuilding the same field each time.

The Fields page lists every global field with its type, configuration, and which flows currently use it, so intake forms stay consistent without manual upkeep.

## Creating a global field

Click **New intake field** to open a dialog with two tabs.

<Tabs>
  <Tab title="Manual Intake Field">
    Build a field from scratch: a name, an optional description, and a type — Text, Long Text, Date, Number, Boolean, Select, Email, User, Multi Select, File, or Multiple Files. Date and Number support additional formatting (for example, slashed or international date formats).

    Two toggles apply to any type:

    * **Mandatory** — the field must be filled in
    * **Read Only** — the field can't be edited once populated
  </Tab>

  <Tab title="Import from Intake Step">
    Surfaces every field already in use across your org's Intake steps, with its name, description, and which flow(s) use it. Select one or more to pull into the global library in a single action — the fastest way to consolidate fields that were built flow-by-flow before the global library existed.
  </Tab>
</Tabs>

## Using global fields in a flow

Once a field is in the library, it's available when configuring the Intake step of any flow — regardless of trigger source (Manual, Slack, Teams, Email, or Salesforce). Selected fields resolve the same way they always have, available downstream as `@Intake.FieldName`. Adopting global fields only changes where the field is defined, not how it's referenced elsewhere in the flow.

## Managing and archiving fields

The **Fields** tab shows every active global field; a separate **Archived** tab holds retired ones. Archiving removes a field from the picker without deleting its history — useful when a field is no longer needed but older flow versions still reference it. Use the search bar and **Used in Flow** column to check whether a field is safe to archive.