Introduction to databases

Notion databases turn scattered information into structured, reusable “intelligent file cabinets,” letting teams store large sets of records and then view them in multiple ways—tables, boards, lists, timelines, calendars, and galleries—without changing the underlying data. Each database entry behaves like a page, complete with properties (such as text, numbers, dates, or people) that apply consistently across every record. That combination—structured properties plus flexible views—makes it practical to run workflows like editorial planning, sprint tracking, recruiting pipelines, or meeting-note repositories.

The walkthrough builds an editorial calendar for a marketing team to show how the pieces fit together. After choosing a database layout, the process starts with an empty database and a name, then relies on default columns like “name” and “tags.” Each row represents an editorial piece; hovering over an entry and selecting “open” reveals a full page where teams can write drafts, add sections for visuals, and store all the usual Notion content. At the top of every entry page sits “properties,” which act as the database’s shared metadata. Adding a new property—via “add property”—extends it across all entries, not just one page. For example, creating a “select” property for “status” introduces options such as idea, in progress, in review, and published, enabling consistent tracking from draft to release.

The example also shows how teams enrich records with collaboration and categorization. “Tags” can be edited for name and color, supporting multiple keywords per article. “Person” properties let editors and writers be assigned from the workspace member list, and those people receive notifications in their Notion apps when tagged. Additional property types are suggested for real-world workflows, including date fields for deadlines and publication dates, and a URL property for the final link.

Once the database grows, the key advantage becomes managing it at scale. In table views, each property maps to a column, and properties can be renamed, edited, deleted, or reordered by dragging. To keep work organized, Notion supports multiple “views” of the same database—such as grouping by status in a board, grouping by writer, showing only published items in a list, placing cards on a calendar by deadline, or using a timeline for a bird’s-eye view. Each view can be customized with its own filters, sorts, and which properties are visible, using a three-dot menu.

Finally, the transcript explains how to reuse existing database structures. Instead of creating a new database from scratch, users can insert an inline database block by typing “/” and selecting a database view. Choosing a data source creates a filtered, shareable page that reflects the original database’s structure; editing the view changes what’s shown, while editing content affects the underlying records. Inline databases can be expanded to full pages, navigated via breadcrumbs, and moved around like other Notion blocks. The result is a repeatable method for building custom databases and tailoring how teams see the same information to make faster, more informed decisions.