Notion at Work: Crafting an Intelligent Workspace

An “intelligent workspace” in Notion can be built by separating storage from access: centralize work into master databases, then create a home base that routes people to the right views. The payoff is a system that keeps information tidy through structured relationships, while still staying flexible as new projects, resources, and Notion features evolve.

The approach starts with centralizing information using PARA—an organizational method associated with Thiago Forte. PARA divides knowledge into four buckets: Projects (initiatives with outcomes and deadlines), Resources (reference materials used during projects), Areas (ongoing categories like Marketing or Accounting, often including client work), and Archives (completed or inactive items). In the demonstration workspace, a single top-level “data” page holds four master databases: Areas, Projects, Tasks, and Resources. Each database includes key properties that make the system workable at scale: Areas uses a select property to distinguish “internal” versus “client”; Projects includes a status select, a person property for the project manager, and an end date; Tasks includes a person property for the task owner, a date property for deadlines (without an end date), and a checkbox for completion; Resources stores files and media.

The real engine is Notion’s relational linking between those databases. Areas link to Projects via a relation property, creating a reciprocal “area” relation inside Projects. Projects link to Tasks the same way, producing a “project” relation inside Tasks. Resources link back to Areas, so resources can be filtered and surfaced by the relevant area. With those links in place, the system can use rollups and formulas—such as calculating project progress as a percentage of completed tasks and estimating days remaining for projects that are in progress or planned.

After the master databases are connected, the workspace becomes useful by populating them and then generating templates. Opening an Area page shows a snapshot: an overview, a table of contents, a projects board (a linked database filtered to only projects tied to that area, grouped by status), and a resources list (also a linked, filtered view). The same pattern repeats for Projects: a project page includes documents and, most importantly, a task list that’s a linked database filtered to tasks belonging to that project. Templates make duplication fast—copying the area and project page structures so new areas and projects automatically get the right layout.

The second prong creates access. A separate top-level “home base” page acts as the team’s navigation layer. It begins as a simple bullet list of what people need most often—typically Areas and Resources, with Projects reached through Areas and Tasks reached through Projects. Those items are converted into categorized columns with links. Some links jump directly to area or resource page blocks; others open new pages that host filtered linked databases—such as a staff directory gallery filtered to a specific team, a sales pipeline board grouped by pipeline stage, and tables for clients and vendors. The home base can also pull in recent newsletter posts via a linked database stored as a resource.

In short: master databases provide structure and automation through relations, while the home base provides intuitive entry points. Together, they create a workspace that’s both clean enough to manage and flexible enough to grow.