Complete Guide to Notion Layouts?! | The Best New Feature!

Notion’s new database “layouts” feature lets users redesign how database properties and content appear on every page—turning a cluttered template into a structured, purpose-built dashboard. The biggest practical shift is that layouts are configured at the database level: once a layout is customized, it becomes the default look for every page inside that database, so teams and personal workflows can stay consistent without reformatting each entry.

Accessing the feature starts with a database. Inside a database page, users can open layout settings via “Customize layout” (for example, after creating or inserting an inline database). From there, the layout controls are organized around page-level presentation and property placement. In “Page settings,” users can switch comment density between inline comments and minimal comments, toggle page discussions on or off, and—one of the more notable changes—turn off property icons entirely. That last option matters because it reduces visual noise and makes dense templates easier to scan.

The layout builder also supports “pinning” up to four properties so key fields sit directly under the page title. In a personal finance example, pinning the date demonstrates how critical metadata can remain visible while other properties move lower in the page hierarchy. Beyond pinning, the builder introduces “property groups” (the container that holds properties in the layout). While the main group itself can’t be deleted, properties can be shown or hidden, and users can reorganize what appears where.

A major new capability is sectioning. Users can add sections to cluster related properties—such as keeping budget-related formulas together while surfacing “Key info” fields like budget graph, expenses due, expenses paid, and income. The layout can also treat single properties as standalone blocks, with size options (large or small). This helps long property names display fully and allows prominent visuals—like a budget graph—to appear bigger than in older, more constrained layouts. Notes and files/media benefit particularly from this approach, since they can be given dedicated space rather than squeezed into a small header area.

Relations require extra attention. Relations can appear as a “relations group” in the new layout system, but returning to the older “minimal” relation view takes additional steps: converting between section and relations group, then toggling each relation’s display mode (e.g., showing as minimal when desired). Finally, the “add to panel” option provides a decluttering mechanism by moving selected property groups or individual properties into a sidebar-style panel. The result is a cleaner main page while still keeping less-used details accessible.

Best practices emphasized include using the sidebar/panel for what shouldn’t be immediately visible, pinning high-value fields (like tags) at the top, grouping files and media so images render larger, and sectioning or hiding formula-heavy properties so users understand what’s important at a glance versus what’s informational background.