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

# Field Configuration

> Configure which fields appear, their order, and display behavior for each entity type across create, edit, detail, list, and wizard view contexts.

Field Configuration is the admin page at `/settings/field-config` where administrators define how fields render for each supported entity type (`ENTITY_TYPES`) across five view contexts: `create_form`, `edit_form`, `detail_view`, `list_view`, and `wizard`.

## Overview

The page is organized around an entity selector and a view-context tab set. Once an entity and context are chosen, the field configuration table shows all configured fields and their display properties. Standard fields are distinguished from custom fields. Administrators can add individual configs, edit existing ones, or use the "Initialize Defaults" action to create a baseline set from `getDefaultFieldConfigs`.

The Layout Builder for a specific entity type is a separate route: `/settings/field-config/:entityType/layout` (see [Layout Builder](/pf/layout-builder)).

## Who it's for

Access follows your organization's role and module configuration. Access is implicitly gated by the settings section. SME should confirm intended access.

## Before you start

* Identify the entity type and view context you need to configure.
* Custom fields must be created first (see custom fields documentation) before they can be added to a field config.

## Steps

1. Navigate to **Settings → Field Config** (`/settings/field-config`).
2. Select an entity type from the dropdown.
3. Choose a view context tab (Create Form, Edit Form, Detail View, List View, or Wizard).
4. Review the existing field configurations in the table.
5. To add a configuration, click **Add** and complete the form.
6. To initialize all defaults for the current entity and context, use the **Initialize Defaults** action. Confirm before proceeding.
7. To open the full drag-and-drop layout builder, click the layout icon to navigate to `/settings/field-config/:entityType/layout`.

## Key concepts

**View context** — one of `create_form`, `edit_form`, `detail_view`, `list_view`, or `wizard`. Field configurations are scoped to a specific context so the same field can appear differently across contexts.

**Standard fields** — platform-defined fields from `STANDARD_FIELDS`. These have fixed keys and types.

**Custom fields** — org-defined fields retrieved via `useCustomFieldDefinitions`. They must exist before being added to a field config.

## Related

<Columns cols={2}>
  <Card title="Platform Foundation" icon="layer-group" href="/pf/overview">
    Platform Foundation overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index" />
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/platform.tsx
  * src/platform/field-config/pages/EntityFieldConfigPage.tsx
  * src/platform/field-config/hooks/useEntityFieldConfigs.ts
</Accordion>