When you group rows in a Notion database, the default behavior often creates nested subgroups under a primary group. This can clutter your view and make it harder to scan information quickly. The feature that causes this is the ability to add multiple grouping layers in a database view. This article explains how to group database rows using only a single grouping layer, avoiding unwanted subgroups entirely.
Notion database views let you organize rows by a property such as Status, Date, or Select. By default, you can add a second grouping layer that creates subgroups. Many users find this unnecessary for simple sorting tasks. This guide shows you how to set up a single group and prevent any subgroup from appearing.
You will learn the exact steps to configure a grouped view in Notion with one level only. You will also understand why subgroups appear and how to remove them permanently from your view. By the end, you can keep your database clean and focused on the primary grouping you need.
Key Takeaways: Single-Level Grouping in Notion Databases
- View menu > Group by > Select property: Adds one grouping layer to your database. Do not click “Add group” to avoid a second layer.
- Group menu > Remove group: Deletes any existing subgroup. Click the three-dot menu on a group header and choose “Remove group” to collapse to one level.
- View layout > Table or Board: Single-level grouping works in any database view type. Board view groups by default but can be limited to one property.
What Database Grouping Does in Notion
Grouping in a Notion database view sorts rows into sections based on the value of a selected property. For example, you can group a task database by Status to see To Do, In Progress, and Done sections. Each section contains all rows that share that property value. This is a single-level group.
A subgroup, or second grouping layer, appears when you add another property to the group. For instance, you might group by Status first and then by Priority. This creates nested sections within each Status group. Notion allows up to three grouping layers in some views. The subgroup is optional and can be removed.
The key to avoiding subgroups is to stop at the first grouping layer. Do not click the “Add group” option that appears after you set the initial group. If you already have a subgroup, you can delete it using the group menu. The database will then show only the primary group.
Grouping does not change the underlying database data. It only changes how rows are displayed in the current view. You can switch between grouped and ungrouped views without affecting your original data. This makes grouping a safe way to reorganize information temporarily.
Steps to Group Database Rows With One Layer Only
These steps work for any Notion database view: table, board, list, calendar, or gallery. The process is the same across all layouts. Follow the instructions exactly to avoid creating a subgroup.
- Open the database view you want to group
Navigate to the page containing your database. Click anywhere in the database to select it. The database toolbar appears at the top of the view. - Click the view name in the toolbar
The view name is usually “Table view” or “Board view” by default. A dropdown menu opens with options to edit the view. - Select “Group by” from the menu
In the dropdown, find the “Group by” option. It is located under the view layout settings. Click it to open a list of database properties. - Choose a property to group by
Select any property from the list, such as Status, Date, or Select. The database immediately rearranges rows into groups based on that property. Only one group appears. Do not click “Add group” after this step. - Verify that no subgroup exists
Look at the group headers. Each header shows the property name and value. If you see a second property name next to the first, a subgroup is active. Proceed to the next section to remove it.
After step 4, your database shows rows grouped by the selected property only. No subgroups appear. If you need to change the grouping property, repeat steps 2 through 4 and select a different property. The previous group is replaced automatically.
If Notion Still Shows a Subgroup After Grouping
Sometimes a subgroup appears because the view was previously configured with multiple grouping layers. This can happen if you or another collaborator added a second group in the past. The subgroup persists even after you change the primary group. You must remove it manually.
“I see two property names in the group header”
This means a second grouping layer is active. To remove it, hover over any group header. A three-dot menu icon appears on the right side of the header. Click it and select “Remove group” from the menu. The subgroup disappears immediately. Only the primary group remains.
“The Remove group option is grayed out”
This happens when only one group exists. If the option is grayed, you already have a single-layer group. No action is needed. If you still see two properties, the second one might be part of the view layout rather than a group. Check the view settings to confirm.
“I accidentally added a subgroup and cannot undo”
Use the undo shortcut Ctrl+Z on Windows or Command+Z on Mac immediately after adding the subgroup. This reverts to the previous single-layer group. If you closed the view or performed other actions, use the “Remove group” method described above instead.
Grouping in Board View Without Subgroups
Board view in Notion automatically groups rows by a property. By default, it uses the Status property. To change the group property without adding a subgroup, follow the same steps as for table view. Click the view name, select “Group by”, and pick a property. Board view does not support multiple grouping layers in the same way as table view, but you can still add a subgroup by clicking “Add group” in the board settings. Avoid this option.
If you see nested columns within a board group, those are not subgroups. They are separate board columns created by the property values. For example, if you group by Status and have three status values, you see three columns. This is normal single-layer grouping. No additional action is required.
Single Group vs Multiple Groups: Which to Use
| Item | Single Group (One Layer) | Multiple Groups (Subgroups) |
|---|---|---|
| Number of grouping properties | One | Two or three |
| Visual structure | Flat sections | Nested sections |
| Best use case | Simple sorting by one attribute | Complex filtering by multiple attributes |
| Performance impact | Low | Moderate |
| Ease of scanning | High | Lower due to nested layout |
For most daily tasks, a single group is sufficient. Use multiple groups only when you need to analyze data by two properties simultaneously, such as grouping tasks by Status and then by Priority. If you do not need this level of detail, stick with one group to keep the view clean.
Common Mistakes When Grouping Rows
Users often create subgroups unintentionally. The most common mistake is clicking “Add group” after setting the first group. Notion places this option directly below the group property selector. It is easy to click by accident. Always check that you have selected only one property before closing the view settings.
Another mistake is confusing group headers with property labels. In table view, column headers show property names. Group headers appear as separate sections with a colored background. If you see two property names in the group header, a subgroup exists. If you see one property name, you have a single group.
A limitation of single-layer grouping is that you cannot sort rows within a group independently. All rows in a group follow the same sort order set for the view. To sort rows differently per group, you must use a subgroup or a separate view. Consider this when planning your database layout.
If you share a database view with collaborators, they can add subgroups without your knowledge. Check the view settings periodically if you notice unexpected nesting. You can also duplicate the view and lock it to prevent changes. To lock a view, go to the view menu and toggle “Lock view”. This prevents anyone from modifying the grouping or layout.
You now know how to group database rows in Notion without creating a subgroup. Use the “Group by” option in the view menu and stop after selecting one property. If a subgroup appears, remove it using the three-dot menu on the group header. For a more advanced setup, try creating multiple saved views with different single-group configurations. You can switch between them quickly using the view dropdown in the toolbar.