A Notion filter belongs to one database view, not to the whole database. Open the view, select the settings menu at the top right of the database, choose Filter under View settings and pick the property to filter by. Rows that don't match stay in the database; that view stops showing them. Save for everyone decides who sees the rule: switched on, it applies to everyone in the view, and left off, it applies only to you.
For a list only you use, such as My open tasks, add a simple filter and leave Save for everyone off. For a view the whole team reads, check the rows first, then save the filter for everyone so nobody wonders where a task went. When one rule needs OR, switch to an advanced filter. When each project page should list only its own tasks, build that list once inside a database template with a self-referencing filter.
Each view keeps its own filters, sorts and groups
Notion stores these settings per view. Notion's help on views, filters, sorts and groups says each database view has its own settings, and settings applied to one view won't be applied across all other views automatically. The View settings menu holds Layout, Property visibility, Filter, Sort, Group and Sub-group, plus Copy link to view, which gives you a direct link to the view you're in.
That rule settles a common question: there's no single filter that every tab of a database inherits. Each tab is its own view, so a rule you want on four tabs has to be set on four views. I'd turn that into a design rule and build views around questions. A task database could carry My open tasks, This week and Waiting on client, each with one or two filters that answer its question. A view named for its question also tells the next person what it leaves out and why, which a busy table with filters retyped every morning never does.
The same thinking picks the layout. Choosing a view for the question covers when a table, board, calendar or dashboard fits; this guide covers the rules inside the view.
Who sees your filter: Save for everyone
Filters and sorts both come with a Save for everyone option. Notion's help says to choose it if you want the filter applied for everyone in the database view, and to leave it unselected if the filter should apply only for you. Sorts follow the same rule.
I'd build every new filter as a personal one first, check that the right rows are left, and only then save it for everyone. A shared filter changes what every person in that view sees, and a teammate who didn't set it will read a missing row as a missing task. If someone reports exactly that, find the rule hiding the task before you change the record or the view.
One tab setting is always personal. Display as on a view tab (Icon only, Text only or both) changes how your tabs look, and Notion's help says only you will see that change.
Keep the access boundary separate from all of this. A filter decides which rows a view shows; it doesn't decide who can open them. Linked views respect the access level of the original database, so settle who can open the source before you count on a view to keep a row away from a client.
Here's how far each setting reaches:
- Filter on one view: applies to that view only; other views of the same database are untouched.
- Save for everyone off: the filter applies only for you.
- Save for everyone on: everyone in the view sees the filtered result.
- Linked view on another page: its filters stay on that linked view and don't reach the original.
- Dashboard in View mode: filters and sorts are stored locally unless someone with edit permissions selects "Save for everybody."

Add a simple filter
- Open the database view you want to narrow.
- Select the settings menu at the top right of the database, then Filter under View settings.
- Choose the property you'd like to filter by, then set the rule a row has to meet.
- Decide on Save for everyone: on for a shared view, off for a personal one.
To remove a filter, open it and select ••• → Delete filter.
Most client-work views start with two filters. Notion's guide to advanced database filters points to properties like date or status for refining views, and Notion's dashboard help uses "This week" and "Status is not Done" as its example filters. A status filter drops finished work; a date filter keeps the period you're planning. If the week in your review means something specific, such as Monday to Friday or the next seven days, define the week instead of relying on its label.
Two other settings change what a filtered view shows. If sub-items are turned on, their visibility settings also affect your filtered results. And filters decide what a column calculation adds up: Notion's advanced filters guide also describes filtering out specific table rows, then hovering over the bottom of any column to calculate a sum or average, so a view filtered to one client totals only that client's hours.
For a one-off lookup, search instead of filtering. In a database with at least three pages, select the search icon at the top of the database and type. Database search looks at page titles and properties, and the database shows only matching pages while you type.
Advanced filters: AND, OR and filter groups
Use an advanced filter when a view needs OR, or a mix of AND and OR. Select Filter under View settings → Add advanced filter, choose the properties and set the AND and OR logic between them. A simple filter you've already built can move over: open Filter, click that filter, then select ••• → Add to advanced filter.
The brackets inside an advanced filter are filter groups. Notion's help says they combine AND and OR logic and can be nested up to three layers deep. That's also the answer to "group filter": a filter group is one set of rules inside an advanced filter. It isn't the grouping that splits a view into sections. It isn't a workspace member group either; those live in Settings and grant groups of people access page by page.
Take a view for work that needs attention this week: Status is In progress AND (Due is this week OR Priority is High). The top layer holds the AND, and one filter group holds the OR. That's two layers, and anyone can read it.
I'd stop at two layers. Three is the app's ceiling and two is the API's limit for compound filters, so a two-layer rule can be rebuilt in an integration without redesign. A third layer is also where people start editing a rule they can't read at a glance. When a view needs more, split it into two views with plainer names.

Sort rows and set a custom order
Select Sort under View settings and choose the property; Save for everyone works the same way as for filters. Sorts run in ascending or descending order. With several sorts, the order matters, and you change the order they're applied in by dragging each sort up or down by its ⋮⋮ handle. To drop a sort, select the X next to it.
Each property type sorts by its own logic:
- Text properties such as Name sort alphabetically.
- Number properties sort numerically.
- Select and Multi-select are where custom sort lives: click the property, then drag its options up or down to set what the sort order means.
- Rollups can only be sorted when they output a numeric value.
For a client task list I'd sort by due date first and priority second. The date answers what's next, and the priority breaks ties between tasks due the same day. Drag the Priority options into the order you want, High above Low, so the second sort matches how you'd rank the work out loud.
Group and sub-group a view
Select Group under View settings and choose the property, and the database groups its rows by that property's values. Sub-group adds a second layer inside each group; Notion's help gives the example of groups by status sub-grouped into priority. That's the answer to grouping by two columns: one group and one sub-group.
Boards start grouped. Notion's board help says a new board groups by a status property if the database has one, and otherwise by a select, person, multi-select or relation property. On a board, both layers sit in the settings menu at the top right: Group, then Sub-groups. The thomasjfrank.com walkthrough of database grouping, from a creator who sells Notion templates and courses, shows a task board grouped by Status and sub-grouped by Assignee and calls the result swimlanes.
The Group menu controls the sections themselves:
- Hide or show a group: select the eye icon next to it. On a board, ••• next to a column heading → Hide group does the same.
- Order the groups: sort them manually or by the options provided, such as alphabetical or ascending.
- Hide empty groups: drop sections with no rows.
- Color columns: board columns are colored by default; this toggle under Group turns that off.
- Column counts: the gray number beside each board column shows the number of cards by default. It can show Count values, Count unique values, Count empty or Percent not empty instead, plus Sum, Average, Median, Min, Max and Range when the property is a Number.
- Remove grouping: turns groups off for that view.
A hidden group hides its rows from that view only; the pages stay in the database. Reveal them from the settings menu → Group, which lists visible and hidden columns. For a crowded Done column, the board help recommends hiding it, and a kanban board grouped by Status with Done hidden shows that setup for client work.
Some property types group in their own way. The notion.vip grouping guide, a free segment of a paid Notion course, says Number groups take a range and increments, Date groups can run by days, months or years, and formulas that return text can group by first letter or full value. The thomasjfrank.com walkthrough lists Relative, Day, Week, Month and Year for dates and points out that a row with several Multi-select tags shows up once in each matching group. It's the same page shown in each group.
For progress, group by Status. Its options sit in groups such as To-do, In progress and Complete, which need separate handling from status options in API filters, and Status vs Select for project tracking explains when a Select fits better.
Group by relation, formula or rollup: the sources disagree
Notion's own pages don't agree on which property types can drive groups. Notion's guide to using database views says entries can be grouped by any property, while the FAQ on the board help page says grouping by a relation or formula property isn't supported. The board help also points both ways on relations: its default grouping can fall back to a relation property.
| Source | What it says |
|---|---|
| Notion's guide to using database views | Entries can be grouped by any property. |
| Notion's board help, FAQ | Grouping by a relation or formula property isn't supported. |
| Notion's board help, default grouping | Status first, then a select, person, multi-select or relation property. |
| notion.vip grouping guide | Any property except a Rollup, in any layout except Calendar. |
| thomasjfrank.com walkthrough | Formula and Relation are listed as groupable; rows grouped by a formula can't be dragged between groups. |
I'd plan boards around Status, Select, Person, Date, Checkbox, Text or Number, the types none of these sources disputes. Before you design a layout around a relation or a formula, open Group on your own view and see whether it's offered.
Filters on linked views and dashboards
A linked view puts a filtered window onto a database somewhere else, such as a client page. Type /linked, press Enter and choose the source database. Notion's help on data sources and linked databases says the views, filters, sorts and groups you create and delete there won't affect the views on the original database, while edits to the data source's title, properties or pages are reflected in the original. Which linked-view edits change the original walks through that split before you edit anything.
Every linked view respects the access level of the original database, and Notion's help tells you to make sure the person you share the page with has access to the original database. Putting a linked view on a client page doesn't give anyone access to the rows behind it.
Dashboard views are available on Business and Enterprise plans, and their filters follow their own rules:
- View mode: filters and sorts aren't saved to the dashboard by default. They're stored locally unless you select "Save for everybody" and have edit permissions.
- Global filters: select the filter icon in the dashboard, choose Filter multiple sources, then pick a property and set your criteria. A global filter reaches widgets from different data sources, but only those whose underlying views include the property you're filtering.
- Underlying views: changes to a widget's underlying view may also appear anywhere else that view is used, depending on your workspace settings.
- Permissions: dashboard views follow the same permissions as the underlying database.
Notion's dashboard help also advises filtering the data each widget loads and avoiding large, unfiltered table widgets. A dashboard holds up to 12 widgets, four per row, and I'd give each one a filtered question to answer rather than a full table to scroll.
Self-referencing filters in database templates
A self-referencing filter sits on a linked view inside a database template and points at the page that template creates. Every new project made from the template opens with a task list showing only its own tasks. Notion's release note on self-referential filters in database templates introduced it in May 2020 and names the problem it solved: before, each new entry needed its filters rebuilt by hand.
You need a relation first. The Benny Builds It guide to self-referential filters, from an ad-free, reader-supported site that earns commissions through its links, says the filter can be applied to any view of a database with at least one relation property, linking the database to itself or to another database.
- Relate the two databases, for example Projects and Tasks. The templates4notion guide to linked databases, written by a seller of Notion templates, uses a two-way relation for this.
- In Projects, click the dropdown arrow next to New at the top right of the database, then + New template. Give the template a title; whatever you title the page becomes the template's name.
- Inside the template, type /linked, press Enter and choose Tasks.
- Add a filter to that linked view on the relation property, set it to contains and pick the template you're editing. An untitled template appears as Untitled in that list, as the templates4notion guide shows.
- Create a new project from the template and open its task view. It lists only tasks related to that project, which is none until you add one.
To have new project pages start this way, set the template as the default; setting template defaults for the right views covers which views should use it. The same pattern answered a question on notionanswers.com, a community Q&A site: a project template with a self-referential filter on both linked views, tasks and notes, so each new project loads only its own items.
Don't fill the relation inside the template to get the same result. Notion's database templates help warns that a relation filled in a template makes every page created with it relate to the same existing page. If that has already happened, trace why every new task links to the same client.
Five descriptions agree on the mechanism: Notion's release note, the notion.vip announcement from a Notion training site, and the three step-by-step pages above. All five describe a linked view inside a database template filtered by the template itself, so each new page shows only its own items, and all three step-by-step pages filter on a relation that points at the template. Two community questions mark the edges, and both are rules of the feature:
- It refers to the page being created, not to a page related to it. A notionanswers.com question about a missing self-referencing option describes a notes template that can't filter by the client its note belongs to. The answer moves the linked view into the Client database template, where the client is the page being created.
- It can't compare two properties of the same row. A Reddit question about a self-referencing filter asks for a rule like ParentID = ID. A view filter compares a property with a value or a page you choose, not with another property on the same row, so that rule can't be built as a filter.

Filter by a relation or a rollup
A relation filter matches rows linked to a page you pick, which is the condition the self-referencing filter uses. Rollups work differently. Notion's relations and rollups help lists the rollup settings as the relation, the property to roll up, the calculation, the number format and the decimal places, with no step that filters the related pages. To count only open tasks or sum only unpaid invoices, build the filtered rollup Notion's rollup menu doesn't offer with filter() in a formula, then use that formula property in the view.
Filter a formula's result
To filter a formula, choose its property in the same Filter menu. The conditions follow the formula's output type: numbers get numeric comparisons, dates get date conditions, and checkbox results get checked or unchecked. The result is read-only, so a filter can't write a matching value into the formula or the properties it reads. If a new row disappears, find it in an unfiltered view and fill its inputs before checking the filtered view again. I'd do that before changing a shared filter: an unfinished row may simply not meet the rule yet.
Filters behind database automations
A database automation can run on the whole database or on one view, and that view's filter then decides which pages it touches. To create a paid-plan automation, you must be a workspace member with Full access to the database; guests can't create database automations. Select the lightning bolt icon at the top of the database → New automation. Notion's database automations help says that if any filters in that view change, the automation applies to the adjusted list of pages. Three rules follow from it:
- An automation can fail on a view that filters out relevant entries, so the view must include every page the automation should act on.
- Date calculations such as dateAdd can fail on an empty field. Notion's fix is a view filtered to items where that field is not empty, with the automation set to run only on that view.
- Automations only run if the page still matches the view when the trigger occurs. A page edited out of the filter doesn't get the action.
I'd give each automation its own view, named after the automation, with a filter that matches exactly the rows it should touch. A shared working view gets re-filtered for daily work, and every edit to its filter changes what the automation does without anyone noticing. Decide which pages are eligible before you build it; separate eligibility from the trigger event walks through that step. Database automations are available on paid plans. Free users can use existing automations in templates but can't edit them. If you need Slack notifications on Free, check whether the action is offered in your workspace; the help gives conflicting plan rules. Only the creator can edit a Slack automation. Automations also won't act on pages whose access is restricted.
Filters in the Notion API
The API uses the same filter logic through a data-source query. The current Notion API filter reference sends POST /v1/data_sources/{data_source_id}/query with Notion-Version: 2026-03-11. The older /v1/databases/{database_id}/query route belongs to the legacy 2022-06-28 API. When migrating an integration, find the data source ID, not the database ID before you port the query.
- A compound filter is an
andororkey holding an array of filter objects, nested up to two levels deep. The app allows three. propertytakes the property's name as it appears in the database, or its property ID.- Status options and groups can share a name. In a direct status filter without the beta header,
equalsmatches an option first and falls back to a group only if no option matches. For an explicit group filter, sendNotion-Beta: status-group-filters-2026-10-06and usegroup_equalsorgroup_does_not_equal. With that header,equalsaccepts option names only. Inside a rollup,equalsanddoes_not_equalmatch option names only, even without the beta header. - Date filters include
this_weekandpast_week, and conditions such ason_or_afteraccept relative values:today,tomorrow,yesterday,one_week_ago,one_week_from_now,one_month_agoandone_month_from_now. - People filters accept a user UUID or
"me"for the user associated with the token. An internal connection has no associated user:contains: "me"returns no rows anddoes_not_contain: "me"matches all rows. Use the person's UUID when the intended assignee must be explicit. - Relation filters use
containswith the related page's ID. - For array-valued rollups, use
any,everyornoneto require any, all or no related values to match. Numeric and date rollups takenumberanddateconditions instead.
Here is the earlier attention view as a request body, two levels deep. equals: "In progress" matches that status option, not every option in the In progress group. To match the whole group, use group_equals and the beta header above:
{
"filter": {
"and": [
{ "property": "Status", "status": { "equals": "In progress" } },
{ "or": [
{ "property": "Due", "date": { "this_week": {} } },
{ "property": "Priority", "select": { "equals": "High" } }
] }
]
}
}
Filter rules at a glance
Where each setting applies decides most filter problems, so here are the rules Notion documents across its help pages and API reference in one place.
| Setting | Documented rule | Notion source |
|---|---|---|
| One view's settings | Each view keeps its own filters, sorts and groups; they don't carry to other views. | Views, filters and sorts help |
| Who sees a filter or sort | Save for everyone applies it to everyone in the view; without it, it applies only to you. | Views, filters and sorts help |
| Filter groups in the app | AND and OR combined in filter groups, nested up to three layers deep. | Views, filters and sorts help |
| Compound filters in the API | and/or arrays of filter objects, nested up to two levels deep. | API filter reference |
| Linked view | Views, filters, sorts and groups stay local; edits to title, properties and pages reach the original. | Data sources and linked databases help |
| Dashboard view | Business and Enterprise. View mode filters stay local unless saved for everybody by someone with edit permissions; global filters reach only widgets whose views include the property. | Dashboards help |
| Automations on a view | Can fail on a view that filters out relevant entries; for date calculations on empty fields, run on a view filtered to not empty. | Database automations help |
| Sub-items | Sub-item visibility settings change filtered results. | Views, filters and sorts help |
| Relation in a template | A relation filled in a template applies to every page made from it; a self-referencing filter follows each new page. | Database templates help, May 2020 release note |
| Database search | Databases with at least three pages; searches titles and properties. | Views, filters and sorts help |
| Status in the API | equals matches an option first; explicit group operators need the status-group beta header. | API filter reference |
| Relative dates in the API | past_week, this_week and relative values such as today and one_week_ago. | API filter reference |
My verdict on Notion filters
Put filters on views and give each view one question to answer: My open tasks, This week, Waiting on client. Build every new filter as a personal one, check the rows, then press Save for everyone only on views the team shares. Start with simple filters, switch to an advanced filter when you need OR, and keep filter groups to two layers. Group boards by Status or Select and sub-group by Person, the types no source disputes. For project pages, put one self-referencing filter inside the database template instead of editing a filter on every new page, and give each automation its own view whose filter matches exactly the rows it should touch.
Notion applies the rule you set. Deciding which rows a client or teammate should see is still your decision, and the source database's access settings are what enforce it.
The low-risk first step: duplicate the view you use most, add one filter to the copy with Save for everyone off, and compare the two views row by row before you save it for the team.
Notion filters FAQ
Can one filter apply to every view of a database?
No. Each view keeps its own filters, sorts and groups, and settings on one view don't carry to the others. Add the rule to each view that needs it. On Business and Enterprise, a dashboard's global filter can cover several widgets at once, as long as their views include the property.
How do I filter a view to today or this week?
Add a filter on the date property and choose the period you need; Notion's dashboard help uses "This week" as its example filter. In the API, use this_week for this week or equals: "today" for today alone. on_or_after: "today" also includes future dates.
Can I group by a relation, formula or rollup?
Notion's sources disagree on relations and formulas, and the notion.vip guide excludes rollups. Open Group on your own view to see which properties it offers, and plan boards around Status, Select or Person.
What's the difference between a filter group and a group?
A filter group is a bracket of AND or OR rules inside an advanced filter. A group is a section of the view built from one property's values, and hiding it hides its rows in that view only.