> For the complete documentation index, see [llms.txt](https://flapjax.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flapjax.gitbook.io/docs/your-data/lists/list-settings.md).

# List Settings

**Settings → Lists** *(beta)*

The main [Lists page](/docs/your-data/lists/browsing-lists.md) is where you browse and curate. The Settings side is where you shape a list's **structure**: its attributes, its membership rules and the shared tag library.

Access needs the data-management settings permission. Making changes needs its manage variant.

Jump straight to a list's settings from the row menu on the Lists page, through **Settings**.

### List attributes

List attributes are fields that live **on the membership** rather than on the person or record. One person can hold different values in different lists. Typical uses: a priority, a review status, a "reason added" note.

Available attribute types: **text, integer, decimal, boolean, date, date & time, single choice (select), multiple choice (multiselect)**. Select-typed attributes can drive a [Kanban view's](/docs/your-data/lists/working-with-list-items.md#views) columns.

An attribute marked **required** needs a value every time an item joins.

> **Deleting a list attribute affects automations.** Any active automation whose list actions reference the deleted attribute gets **paused**, whether Add to List, Update List Item, Find List Items or another. That stops it running with a broken configuration. Review and update those automations before you re-activate them.

### Membership rules

A list can fill **itself**, beyond your manual curation. It holds one or more **rule configurations**, each answering three questions.

**1. What triggers it?** Every configuration takes exactly one trigger type.

* **An event**, such as a person created or updated, or a record in a given stack created or updated. Narrow it further with *Only assign when this attribute changes*.
* **A schedule**, with a frequency, time, weekday or month-day repeat and timezone. Flapjax evaluates scheduled configurations once a minute and fires them when due, apart from any incoming event.

One configuration cannot take both. Pick one.

**2. Who matches?** Conditions over the parent entity's attributes: person fields for a people list, record fields for a record list. Combine them with a **segment** if you want.

Membership rules match on the parent entity's own attributes. The list's own attributes stay out of them, since an item's list attributes exist only once it becomes a member. With no rules and no segment set, the configuration fires for every matching event.

**3. What happens on a match?**

* **Assign while matching** adds items as the rule matches, then removes them once they stop matching.
* **Remove on match** removes items as the rule matches and leaves other memberships alone.

Other behaviour worth knowing:

* On save, Flapjax **backfills** existing people and records that match the rules into the list, in the background. Large organizations may take a moment to fill in.
* Members added this way show **Added via: Rule**. **Manually added members always stay**, even with a rule set, and a scheduled removal only ever removes rule-added items.
* **Remove rules** returns the list to fully manual curation. The same background process handles the rule-added members.
* An incomplete configuration, meaning no trigger or missing trigger fields, blocks saving. Flapjax validates the whole set together.

### List tags

**Settings → List Tags** manages the shared tag library behind the Lists page. Create, rename, recolour and delete tags here. You assign tags to individual lists on the [Lists page](/docs/your-data/lists/browsing-lists.md#searching-sorting-and-tags) itself.