Notion Training: Advanced

Notion databases turn scattered notes into structured work systems by treating every entry as its own page with customizable “properties” and multiple ways to view the same data. The core workflow starts from scratch: create a database (e.g., a table), name it, add an icon, then fill it with entries where each row becomes a page. At the top of each entry, properties act like fields—due dates, owners, customer attributes, priorities, timelines—so teams can store information in a consistent, searchable format rather than free-form text.

Once properties are set, the database becomes far more usable through views. A single database can be displayed as a table, board, calendar, list, or gallery, letting teams switch between perspectives without re-filtering every time. For example, a roadmap-style engineering database can be shown as a board grouped by status, then filtered so only “tasks” appear. Another view can sort by priority (P1 through P5) so the most urgent work sits at the top. Views also support “property visibility” controls, so users can hide clutter by showing only the fields that matter for a given workflow—like a calendar view limited to “epics,” or a list view showing items assigned to a specific person.

To reduce repetitive setup, Notion supports database templates. Templates let users define a repeatable page structure—such as a “bug report” format with required headings and a pre-filled “type” property—so new entries start with the same background information every time. Editing, duplicating, or deleting templates happens from the template menu, and the template can be reused across different kinds of recurring work like meeting notes or design specs.

The next leap is connecting databases so information flows automatically. Using a relation property, one database can link to another—for instance, an “items” database can relate to a “customers” database so each item shows which customers bought it, and each customer shows which items they purchased. Notion also supports roll-ups, which compute aggregated values from related records. With a roll-up property, a “customer order total” can sum item prices pulled from the related items database, giving totals without manual calculation.

Finally, linked databases provide a way to reuse a shared source while tailoring what each team sees. A linked database is an excerpt that can be filtered, sorted, and viewed differently from the original, without changing the original’s structure. Edits made in the linked view still update the master database, making it ideal for shared resources like company-wide meeting notes or team task trackers—where engineering can maintain a focused view without duplicating data.

Taken together, databases, views, templates, relations, roll-ups, and linked databases form a toolkit for building systems that stay organized across projects, people, and teams—while minimizing repetitive work and keeping information synchronized.