> 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/working-with-list-items.md).

# Working with List Items

Open any list to work with its members. **Views** drive what you see inside.

### Views

A list displays its members through saved views, and every list needs at least one. Flapjax prompts you to create one on first open. Two view types exist:

* **Table** puts members in rows, with the columns you choose.
* **Kanban** puts members on cards, grouped into columns by one of the list's *select* attributes. A "Status" attribute, for instance, becomes the board's columns.

Save as many views per list as you like and switch between them.

### Adding members

Three ways in.

1. **From inside the list.** The **Add items** button opens a picker: people for a people list, records from the bound stack for a record list. You can set list-attribute values that apply to everything you add.
2. **From the People or Stacks pages.** Select rows in the grid, or use select-all with your current filters, then choose the **Lists** bulk action. Pick a target list, and Flapjax offers only lists matching the entities you selected. Choose add **or** remove. With select-all, membership follows your active filter rules rather than an explicit row list, and rows you deselected stay out of the operation.
3. **From an automation.** The **Add to List** action enrols the person or record a run is processing. The full action set appears below.

Every member shows **how it arrived**: *Manual*, *Rule* through the list's [membership rules](/docs/your-data/lists/list-settings.md#membership-rules), or *Automation*.

### Removing members

Select members inside the list and use the action bar's **Remove from list**. The People and Stacks grid bulk action does the same with its *remove* operation, and an automation's **Remove from List** action covers the automated route.

Removal ends membership and nothing more. The person or record survives.

### List attributes on items

A list defining [list attributes](/docs/your-data/lists/list-settings.md#list-attributes) gives every member its own values for them. Click a row to open the item panel and edit those values. Editing needs the lists manage permission.

**Set attribute value** in the action bar sets one attribute across many members at once. Pick the attribute, enter the value, then choose **Apply to selected**. It works with both ways of selecting:

* **Explicit selection** updates the rows you chose.
* **Select-all** updates every member matching your current filters, minus any rows you deselected. Flapjax honours those deselections server-side, so "select all except these three" means exactly that.

Setting a value **merges** it into each member, leaving attributes you did not pick alone. A member someone else deleted mid-run gets skipped rather than failing the whole action. Each updated member fires the same *List item updated* trigger a single manual edit fires.

Large select-all updates report progress as they go and finish with a toast. You can navigate away as they run.

### Filtering, sorting and search

* The **filter sidebar** narrows members by the parent entity's own attributes, meaning person or record fields, *and* by the list's attributes.
* **Sorting** covers the added and updated dates, how and by whom an item was added, and the list's own attributes. Sorting by the parent entity's attributes is not available yet.
* Text search across members is not available yet. Use filters to narrow instead.

### Bulk actions on people lists

A people-parented list gets the full People bulk toolkit in its action bar. Assign and remove labels, send an email or SMS, enrol in a sequence, and the rest, applied to the members you select.

### Exporting

**Export CSV** downloads the list's members, respecting your current filters and sort.

### Lists and automations

Lists are first-class in the automation builder.

* **Triggers.** *Item added to list*, *Item removed from list* and *List item updated* each start an automation. Trigger rules can match on which list, and on how the item arrived.
* **Actions.** *Add to List*, *Remove from List*, *Update List Item*, *Get List Item* and *Find List Items* let flows curate lists and read membership data mid-run.

Changes made elsewhere appear in an open list live, with no refresh.