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

# Configure list filters

> Add a People name filter that supports partial-name lookups, then check it in the live list.

Use this guide to add a **Name** filter to **Directory → People** so users can
find a person from part of their name. You need access to your company's
configuration editor and a Person field with the reference `name`. If your AI
Insurance team manages configuration for you, ask them to add the filter using
this example.

See [List filters](/app/features/list-filters) for how to choose the filters
your team needs during onboarding.

## Add the filter to your draft

<Steps>
  <Step title="Open List Filters">
    Open **Admin → Configuration → List Filters**. Select **Edit** to work
    on the configuration draft.
  </Step>

  <Step title="Check the People filters">
    If a Name filter already exists on People, select its **Edit list filter**
    action. Check that it offers **Contains** under **Operators**.

    If the filter is missing, select **Add List Filter**.
  </Step>

  <Step title="Define the name filter">
    For a new filter, enter these values:

    | Setting | Value |
    | - | - |
    | **List** | **People (person)** |
    | **Filter name** | `Name` |
    | **Key** | `name` |
    | **Expression** | `name` |
    | **Result type** | `String` |
    | **Cardinality** | `Single` |
    | **Operators** | **Contains (contains)** |

    The **Expression** reads the person's configured `name` field.
    **Filter name** is the label users see. **Key** identifies this filter
    within the People list and must be unique there. If another filter already
    uses the key `name`, choose a different key for the new filter.

    Select the conditions you want to offer under **Operators**. For partial
    name lookups, include **Contains**.
  </Step>

  <Step title="Add or save the filter">
    Select **Add list filter**, or **Save list filter** when editing an
    existing definition. The change is now in your configuration draft.
    Adding the row does not make the filter available on the live list yet.
  </Step>
</Steps>

## Review and apply the configuration

1. Select **Ship**. The app validates the configuration and previews the changes.
2. Review the whole draft, including any changes beyond this filter.
3. If validation reports an error, close the dialog and correct the draft.
4. When the draft is valid and the changes are ready, confirm **Ship**.
5. After the app confirms **Configuration shipped**, select **Done**.

## Check the lookup

1. Open **Directory → People** and select **Add Filters**.
2. Choose **Name**, then **Contains**.
3. Enter part of the name of a person already in your company's Directory.
4. Select **Apply** and confirm that the expected person appears.

If Name is missing, check that you added the filter to **People** in the
correct company's configuration and shipped the draft. If Name is present
but **Contains** is missing, edit its **Operators** and ship that change.

## Configure another list

For Exposures, Quotes, Policies, or another entity list, choose that list and
the value users need to match. For a single text field, use its configured
reference in **Expression**, rather than its display label. Keep **String**,
**Single**, and **Contains** for a partial-text lookup.

For example, if your Exposures configuration has a text field referenced as
`exposureName`, use that expression for an **Insured Name** filter. The People
`name` expression does not refer to that Exposure field.

An address needs a text expression for a partial-address lookup. If the list
has a single Address or AddressV2 field referenced as `address`, use
`ADDRESS_SEARCH_TEXT(address)`. Set **Result type** to **String**,
**Cardinality** to **Single**, and include **Contains** under **Operators**.

Check the selected list's actual field references before copying an expression.
Other filters, such as dates or dropdown choices, need the appropriate result
type and conditions for the value they produce.

Teams that manage configuration through the API use the `listFilters`
section. See the [Configuration API](/api-reference/configuration/overview)
for how to export, validate, and apply configuration changes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.