Get AI summaries of any video or article — Sign up free
10 New Notion Features You Need to Know About! thumbnail

10 New Notion Features You Need to Know About!

Thomas Frank Explains·
6 min read

Based on Thomas Frank Explains's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Notion’s multi-column feature now supports direct creation (/col, /columns) and conversion of existing blocks into columns, including nested columns without sub-page/toggle hacks.

Briefing

Notion’s latest wave of updates targets day-to-day workflow speed: smarter multi-column building, faster database page previews, and more “native” UI features for collaboration and presentation. The biggest practical shift is in how pages and database items open—side peek lets users inspect a database page in a sliding drawer while still interacting with the underlying page—paired with per-view controls that decide whether pages open as side peek, center peek, or full page.

On the layout front, Notion upgrades multi-column layouts so they’re no longer limited to clunky workarounds. Users can create columns directly with slash commands like /col (with options for two through five columns), or convert existing blocks into columns via the “Turn Into” menu. Nested columns are now straightforward: instead of building sub-pages and toggles, users can create columns inside existing columns using the same conversion and block-creation tools, including multiple layers of nesting. There’s also a practical constraint: selecting more than five blocks doesn’t create more than three column “tracks,” with child blocks nested under their parent blocks—useful to know for indented lists, numbered lists, and bullet lists.

The column update extends into other block types too. Multi-column layouts can be created inside toggles, synced blocks, and template blocks, but there’s a key behavior difference when moving existing multi-column content into those containers: dragging won’t preserve the multi-column structure, while cutting and pasting does. That distinction matters for anyone refactoring templates or reorganizing existing pages.

Database navigation gets a major quality-of-life boost with side peek. Compared with center peek’s dimmed overlay, side peek slides out a drawer showing the page content while keeping the rest of the workspace usable. The setting is configurable per database view through the view’s three-dot menu under Layout → “Open pages in,” with defaults varying by view type (galleries and calendars default to center peek; list, board, timeline, and table default to side peek). Users can also override the mode per open action, and adjust the drawer width—roughly from about 25% to two-thirds of the screen. List view is highlighted as the smoothest pairing because it avoids horizontal scroll issues.

Beyond layout and navigation, the update adds several smaller but meaningful features: database templates can be set as defaults so new database entries automatically receive template content and property values (with options for all views vs a single view, and with filters still taking precedence over template-defined values). Relations gain a “limitation” option for one-to-many setups, restricting a relation to a single related page and swapping the previous selection when changed. The relations picker also becomes more informative by letting users choose which properties of the related pages appear in the picker.

Collaboration and UI polish round out the list: comment reactions add Slack-style emoji reactions; comments can be linked anywhere with preview or mention-style insertion; the icon picker now offers a dedicated Icons set with multiple color options for consistent workspace branding; media blocks in columns can be aligned left or right; and native progress bars appear for number and numeric formula properties (with options to display as bars or rings, divide by a chosen number, and quirks around formula output type and rollups).

Cornell Notes

Notion’s update set focuses on faster building and smoother database workflows. Multi-column layouts now support direct creation (/col, /columns), conversion of existing blocks into columns, and true nested columns without sub-page/toggle hacks. Side peek is the headline database improvement: pages open in a sliding drawer while users keep interacting with the underlying page, and the open mode can be set per database view (side peek, center peek, or full page). Templates can be set as defaults for new database entries, and relations gain both a picker upgrade (show related properties) and a limitation option for one-to-many scenarios. Native progress bars round out the changes for numeric properties and numeric formulas.

How do the new multi-column tools change what’s possible compared with older workarounds?

Users can create columns directly with slash commands such as /col (supporting two through five columns) or convert existing blocks using the block menu → “Turn Into” → “Columns.” Nested columns are now built directly inside existing columns: instead of creating sub-pages and toggles, users can create columns under a column and drag/drop as needed, or select multiple blocks and use the “Turn Into” conversion. Multi-column layouts also work inside toggles, synced blocks, and template blocks, but preserving an existing multi-column layout requires cutting and pasting rather than dragging.

What’s the practical limitation when turning large selections into columns?

When selecting more than five blocks, Notion doesn’t create more than three column “tracks.” Instead, it produces three columns with child blocks nested under their parent blocks. This matters for indented lists, numbered lists, and bullet lists, where the nesting behavior determines how the content will distribute across columns.

What exactly is side peek, and how is it configured?

Side peek opens a database page in a sliding drawer while keeping the page underneath interactive. The open behavior is configurable per database view via the view’s three-dot menu → Layout → “Open pages in,” with options for Side peek, Center peek, and Full page. Defaults differ by view type: galleries and calendars default to center peek, while list, board, timeline, and table default to side peek. Users can also override the mode when opening a page, and adjust the drawer width (roughly from ~25% to ~two-thirds of the screen).

How do default templates work for new database entries, and what wins when there’s a conflict?

A template can be set as a default from the template picker (blue arrow → template menu → “Set as default”). The default can apply to all views in the database or only the current view. If a template sets property values that conflict with filters or view-specific settings, the view’s filters take precedence—so a template might set status to “To do,” but a view filter can still force status to “Doing” so the new entry appears in that view.

How does relation limitation support one-to-many workflows?

In the relation property settings, Notion can limit the relation to a single page (e.g., “one page as the limit”). When a task is related to a project under this constraint, choosing a different project replaces the previous relation rather than adding another. The example setup is tasks → projects: tasks can be restricted to one project, while the reverse relation on the project side can remain unlimited so a project can still have multiple related tasks.

What are the key constraints for native progress bars?

Native progress bars appear for number properties and formula properties that output numbers. In formula properties, the “Show as” option (number, bar, ring) appears only when the formula outputs a number; switching the formula to output text removes the option, though switching back to numeric output restores the prior progress bar choice. Rollups don’t currently show progress bars directly, so the workaround is to copy rollup output into a numeric formula (e.g., using prop("Rollup")). Progress bars can also break when switching to percent formatting, so the transcript suggests dividing to produce a percent-like numeric value while keeping the property in a compatible numeric format.

Review Questions

  1. When converting existing content into nested columns, what operation preserves the multi-column structure—dragging or cutting/pasting?
  2. In side peek, where is the “Open pages in” setting found, and how do defaults differ between list views and gallery/calendar views?
  3. For native progress bars, what must a formula output for the “Show as” bar/ring options to appear, and why might rollups fail without a formula workaround?

Key Points

  1. 1

    Notion’s multi-column feature now supports direct creation (/col, /columns) and conversion of existing blocks into columns, including nested columns without sub-page/toggle hacks.

  2. 2

    Nested columns can be layered multiple levels deep, but selecting large block sets can cap the layout to three column tracks with nested child blocks.

  3. 3

    Side peek opens database pages in a sliding drawer while keeping the underlying page interactive, and the open mode can be set per database view (side peek, center peek, full page).

  4. 4

    Default templates can be applied automatically to new database entries, with view filters overriding any conflicting template-defined property values.

  5. 5

    Relations now support a limitation setting to enforce one-to-many patterns by restricting a relation to a single related page.

  6. 6

    The relations picker can display selected properties from the related database, giving more context when choosing related pages.

  7. 7

    Native progress bars work for number properties and numeric formulas (not rollups directly), with additional quirks around formula output type and percent formatting.

Highlights

Side peek replaces the old “dimmed overlay” feel by sliding a drawer that still lets users interact with the underlying page.
Multi-column layouts can be nested directly now—no more toggle/sub-page gymnastics to get columns inside columns.
Default templates let new database entries automatically inherit template content and property values, but view filters still override conflicts.
Relation limitations enable true one-to-many behavior by restricting a relation to a single related page and swapping selections.

Topics

Mentioned