> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/release-notes/15-sep-2026-release.md).

# 15 Sep 2026 Release

List Filtering now supports nested **and** / **or** / **not** groups and extra value types (clock, current row, and URL parameter). Navigation can **Reuse** the same screen on a second tab and **Detach** that tab when it needs its own copy.

{% hint style="info" %}
Earlier updates For Sync Health and published form save state, see the [14 Sep 2026 Release](https://docs.notionapps.com/release-notes/14-sep-2026-release).
{% endhint %}

***

### What’s new at a glance

| Capability            | What you can do                                                                                                                                   | Learn more                                                                                                                           |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Nested filter groups  | Combine conditions with **and**, **or**, and **not**, up to 3 levels                                                                              | [Filter lists with groups and dynamic values](https://docs.notionapps.com/how-to-guides/filter-lists-with-groups-and-dynamic-values) |
| Dynamic filter values | Compare a list property to the logged-in user, a user property, the current row, Today / Now / Start of week / Start of month, or a URL parameter | Same how-to                                                                                                                          |
| URL parameter lists   | Share `?store=north` so a published list shows only matching rows. Missing param shows no rows for that condition                                 | Same how-to                                                                                                                          |
| Reuse / Detach        | Put one screen in navigation twice; Detach when that tab must diverge                                                                             | [Reuse a Screen in Navigation](https://docs.notionapps.com/how-to-guides/reuse-a-screen-in-navigation)                               |

```
A missing URL parameter does not show every row.
Reuse keeps two tabs in sync. Detach makes a real copy.
Duplicate Screen is still the full independent copy.
```

{% hint style="success" %}
Start here Open a List → **Filtering** → **+ Add Filtering**. Change a value from **Fixed value** to **Today** or **URL parameter**. Add a group if you need parentheses. Publish, then open the live link with and without the query.
{% endhint %}

***

### Features

#### 1. Nested AND / OR / NOT groups

**+ Add group** and **+ Add condition** build a filter tree. Each group uses **and**, **or**, or **not**. Nesting stops at 3 levels.

Use this when a flat list of conditions is not enough — for example “North and Open, or assigned to me and not Archived.”

#### 2. Extra filter value types

On each condition, pick the value type:

| Value type                                                   | Resolves to                                           |
| ------------------------------------------------------------ | ----------------------------------------------------- |
| **Fixed value**                                              | The value you pick                                    |
| **Logged-in user**                                           | The signed-in Users row                               |
| **Logged-in user property**                                  | A property on that user (Pro+, per-list allow switch) |
| **Current row** / **Current row property**                   | The parent record on a related list                   |
| **Today** / **Now** / **Start of week** / **Start of month** | Clock tokens in the app timezone                      |
| **URL parameter**                                            | A query key on the published page                     |

**Start of week** is Monday 00:00 (ISO week). If a user property or URL parameter is missing, that condition matches **no rows** (it does not show everything).

#### 3. URL parameter list filters

Map a condition to **URL parameter** and a **Parameter name** such as `store`. After you Publish:

* `/assets?store=north` shows matching rows
* `/assets` (no param) shows none for that condition

Reserved keys you cannot use as the parameter name: `cache_bust`, `sim_user_id`, `debug`, `live`.

This is separate from [Prefill Create Forms from a URL](https://docs.notionapps.com/how-to-guides/prefill-create-forms-from-a-url), which fills Add-form fields.

#### 4. Reuse screen and Detach

On a screen that is already in navigation, **Reuse screen** adds another tab that still points at the same screen. A banner lists the other tab names.

**Detach** appears when the screen has more than one nav entry. It clones this tab’s screen (and its secondary screens) so you can edit filters on that copy only.

**Duplicate Screen** is unchanged: it always creates a full independent copy.

***

### What makers need to change

| Goal                                     | Extra work                                                          |
| ---------------------------------------- | ------------------------------------------------------------------- |
| Keep existing fixed filters              | None                                                                |
| Personalize a list by user / clock / URL | Open Filtering, pick the value type, Publish                        |
| Share a store-specific list link         | Add a URL parameter condition; tell people to include `?name=value` |
| Second tab, same screen                  | **Reuse screen**, then rearrange in Edit Navigation                 |
| Second tab, different filters            | Reuse, then **Detach**                                              |

***

### Related

* [Filtering, Sorting, or Grouping Items](https://docs.notionapps.com/screens-and-components/customize-a-screen/filtering-sorting-items)
* [Filter lists with groups and dynamic values](https://docs.notionapps.com/how-to-guides/filter-lists-with-groups-and-dynamic-values)
* [Filter List Screens by Logged-in User Properties](https://docs.notionapps.com/how-to-guides/filter-list-screens-by-logged-in-user-properties)
* [Reuse a Screen in Navigation](https://docs.notionapps.com/how-to-guides/reuse-a-screen-in-navigation)
* [Prefill Create Forms from a URL](https://docs.notionapps.com/how-to-guides/prefill-create-forms-from-a-url)
* [📢 Release Notes](https://docs.notionapps.com/release-notes)
* [16 Sep 2026 Release](https://docs.notionapps.com/release-notes/16-sep-2026-release)
* [14 Sep 2026 Release](https://docs.notionapps.com/release-notes/14-sep-2026-release)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/release-notes/15-sep-2026-release.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
