Notion just changed how databases work

Notion’s latest database update lets a single database block contain multiple “data sources,” a structural change that’s already triggering confusion because it sounds similar to the long-requested ability to merge multiple databases into one unified view. In practice, the new capability is narrower: it lets each view inside a database block point to different internal (or external) data sources, but it does not automatically create a view that mixes rows from multiple sources into one combined table.

The update is rolling out gradually, but once enabled, users see a “new data source” option inside an existing database. Instead of creating separate database blocks—one for notes and another for tags—people can keep the overall structure inside a single database block and add additional data sources within it. A typical note-taking setup becomes: one data source for the notes themselves and another for tags. Views then attach to those sources, so switching between views can show different properties (for example, notes views might expose content fields while tags views expose tag-specific fields).

A key operational detail is permissions. Access controls are set at the database block level, not per data source. That means changing sharing settings for the database affects every data source contained within that block, including any views tied to them.

Equally important is what the feature is not. “Parent multiple data sources in a single database” does not mean “show a single table that combines records from multiple databases.” The transcript highlights that the only place Notion currently offers a true multi-source unified view is the Notion Home “My tasks” widget. For users hoping to build a single “Do today” view that pulls tasks from both a personal tasks database and a team tasks database, this update doesn’t deliver that outcome.

The change also introduces practical migration and integration concerns. Notion has released an API upgrade (referenced as “upgrading to 2025 0903”), and integrations such as Zapier, Make.com, Pipedream, n8n, and Flylighter must update to handle databases with two or more data sources. Until developers and workflow builders catch up, automations can break. The transcript notes a mitigation path: moving a data source out of a multi-source database block back into a single-source database restores compatibility for older API behavior.

Finally, the transcript spends time clarifying the underlying terminology that’s now more confusing than before. In Notion’s block model, databases are blocks, but “data sources” sit between the database block and the pages inside it. Views are another layer: they are child entities of the database block that define filters, sorting, grouping, and property visibility, and they point to a specific data source. The update effectively blurs the old distinction between “linked database blocks” (which created views pointing to external sources) and “database blocks” (which held internal sources), because a single database block can now host multiple internal data sources and also include views that link to external data sources.

Despite the structural significance, the transcript argues against retrofitting existing systems immediately. For most individual users, it doesn’t deliver a clear productivity boost, and it can add confusion for teams and risk automation breakage. The safer approach is to adopt it for new builds, while keeping older templates stable until integrations fully catch up.