When you work with a Notion database that contains dozens or hundreds of entries, sorting by a single column often does not give you the precise order you need. You might want to sort tasks by priority first, then by due date, or sort projects by status and then by assignee. Notion allows you to apply multiple sort rules to any database view, creating a layered order that reflects your real workflow. This article explains how to add, arrange, and remove sort rules in a Notion database view so you can organize entries exactly the way you want.
Key Takeaways: Sorting by Multiple Properties in Notion
- Database view menu > Sort > Add a sort: Opens the sort panel where you can pick the first property and direction.
- Sort panel > Add another sort: Lets you stack a second, third, or fourth rule to refine the order further.
- Drag handles next to each sort rule: Reorder the priority of rules so the most important property runs first.
How Notion Database Sorting Works
A Notion database view — table, board, list, calendar, or gallery — can display entries in a custom order that is separate from the order in the original database. Each view stores its own sort settings. When you add a sort rule, Notion reorders the visible entries based on the property you choose. You can sort by text (alphabetical), number (ascending or descending), date (earliest or latest), select options (based on the order you defined in the property settings), and other property types. The sort applies only to the current view, so other views of the same database remain unaffected.
Multiple sort rules work like a tiebreaker system. The first rule arranges all entries. If two entries have the same value for the first rule, Notion applies the second rule to decide their relative order. This layered approach lets you create fine-grained sorting, such as grouping all tasks by category first and then ordering each category by due date. You can add up to five sort rules in a single view.
Before you start, confirm that your database has at least two properties that you want to use for sorting. Typical combinations include Status then Due Date, Priority then Assignee, or Category then Created Time. If a property is empty for some entries, those entries will appear at the bottom or top depending on the sort direction and property type.
Steps to Add Multiple Sort Rules to a Database View
The process is identical across all database view types in Notion. The following steps assume you are using a table view, but the same menu applies to board, list, calendar, and gallery views.
- Open the view menu
In the top-right corner of your database, click the view name — it is usually labeled Table view, Board view, or a custom name you gave it. A dropdown menu opens with view options. - Click Sort
From the dropdown, select Sort. A sort panel appears on the right side of the window. If no sort rules exist yet, you will see a button labeled Add a sort. - Add the first sort rule
Click Add a sort. A new row appears with two dropdown menus: one for the property name and one for the sort direction. Choose the property you want to sort by first. Then select Ascending or Descending. For text properties, ascending is A to Z and descending is Z to A. For dates, ascending is earliest first and descending is latest first. - Add a second sort rule
Below the first rule, click Add another sort. A second row appears. Pick the property that will serve as the tiebreaker. For example, if the first rule is Priority descending, set the second rule to Due Date ascending. Entries with the same priority will then be ordered by due date. - Reorder the sort rules if needed
Each sort rule has a drag handle (six dots) on its left side. Click and drag a rule up or down to change its priority. The rule at the top is applied first. If you want the due date to take precedence over priority, move the date rule above the priority rule. - Remove or edit a sort rule
To change a property or direction, use the dropdowns in the rule row. To remove a rule, click the three dots on the right side of the rule row and select Remove. The view updates immediately after each change. - Close the sort panel
Click anywhere outside the sort panel or press Escape on your keyboard. The database view now displays entries in the order defined by your combined sort rules.
Things to Avoid When Sorting by Multiple Properties
Sort rules conflict with manual drag-and-drop reordering
If you manually drag a row to a new position in a table view, Notion automatically adds a sort rule based on the default None order. This can override your custom sort rules. To avoid confusion, either use only manual reordering or only sort rules — do not mix both in the same view.
Empty property values cause unexpected placement
When a property is empty for some entries, those entries are sorted to the top (ascending) or bottom (descending) depending on the property type. For example, if you sort by Due Date ascending, entries with no date appear first. If you sort descending, entries with no date appear last. To prevent this, ensure all entries have a value for the properties you sort by, or use a filter to exclude empty entries.
Select properties sort by manual order, not alphabetically
Notion sorts select and multi-select properties based on the order you defined in the property settings, not alphabetically. If you want alphabetical sorting, use a text property instead. You can change the option order in the property settings by dragging options up or down.
Sort rules do not transfer to copied or duplicated views
When you duplicate a view or copy a database, the sort rules are not carried over. You must reapply the sort rules in the new view. This also applies when you duplicate the entire database page.
Too many sort rules can slow down large databases
Notion applies all sort rules to every entry in the view. For databases with more than 10,000 entries, adding four or five sort rules may cause a noticeable delay when loading the view. Limit sort rules to two or three for large databases to keep performance responsive.
Notion Sort Rules: Single vs Multiple Properties Compared
| Feature | Single Sort Rule | Multiple Sort Rules |
|---|---|---|
| Number of properties | 1 | 2 to 5 |
| Tiebreaker behavior | No tiebreaker — order of entries with same value is undefined | Second rule resolves ties from the first rule |
| Use case | Simple lists like alphabetical names or chronological dates | Complex views like tasks sorted by priority then due date |
| Performance impact | Minimal | Slight increase on very large databases |
| View duplication | Lost when duplicating | Lost when duplicating |
After setting up your sort rules, you can combine them with filters to show only specific entries in the desired order. For example, filter by Status equals In Progress and sort by Priority descending then Due Date ascending. This gives you a focused, ordered view of active tasks. To save your sort configuration for reuse, duplicate the view and rename it — the sort rules will be lost, but you can reapply them quickly using the sort panel. For advanced users, consider creating a template database with preconfigured sort rules and duplicate it for each new project.