24 New Notion Database Features — Applied to Notion Life OS / PPV

Notion’s latest database upgrades aim to make large systems faster to use and easier to design—especially for people building “life OS” workflows where tasks, projects, and relationships must stay tightly connected. The biggest practical win is performance: large databases load and respond about 2.5× faster, reducing friction when working inside complex dashboards, boards, and linked views.

Beyond speed, the updates focus on day-to-day usability and smarter automation. Small interface improvements include spreadsheet-style fill: users can drag a handle to copy values down a column (with Command D / Ctrl D for bulk fill). Side peek—the quick panel that opens when selecting an entry—can now be resized, and the chosen width becomes the default for that database. Notion also adds faster navigation out of side peek (via Escape), plus more control over whether entries open in side peek, center peek, or full page.

The most workflow-relevant change is a more automated way to map “today, tomorrow, and the next week” without manual tagging. In the PPV life operating system example, tasks carry a “due date” that represents when work is intended to happen (not just when something is completed). By grouping a board view by due date, tasks automatically roll into the correct columns as dates advance—eliminating the older approach where users had to assign “Monday/Tuesday/Wednesday” selectors by hand. Filters and sorting then tighten the view: only active, not-done items appear; results sort primarily by priority and secondarily by due date so timed items (like 1pm vs 2pm) order correctly.

For people overwhelmed by “7 days” clumps, the workflow shifts from broad buckets to a day-by-day window. Adjusting the board’s relative due-date range and filtering out items without due dates creates a cleaner calendar-like board that supports rapid scheduling and rescheduling.

Board views also gain editing convenience: properties visible on a board card can be changed directly in-place, so updating priority or dates no longer requires opening each page. That matters when managing pipelines like content production, where many fields must be adjusted frequently.

A major structural upgrade is the new “status” property type. It replaces the older “single select” pattern for pipeline stages by letting teams convert existing selector properties into status properties while preserving settings. Status properties introduce higher-level groupings (for example, “Not started,” “In progress,” and “Complete” categories) that make boards easier to scan and more intuitive for collaborators. Users can also choose whether to display a checkbox-style completion indicator, though the guidance favors advancing items through stages rather than relying on checkboxes midstream.

Notion also adds native progress bars and rings for numeric properties, including rollups—removing earlier limitations that forced workarounds like mirrored formulas. On the relational side, connection pickers become cleaner and more informative, and relational properties can be displayed as a page section to reduce clutter. Additional refinements include hover-to-reveal truncated titles, more flexible wrapping per cell, and a new “export current view” option that exports only filtered rows instead of the entire database.

Finally, collaboration and reuse get better: databases can be locked so teammates can interact with data without breaking layout, filters, or view type. For new builds, linked databases can now pull in existing layouts, views, and filters as a head start rather than starting from scratch. Taken together, these changes make Notion databases more responsive, more automatable, and more maintainable for complex systems.