15 Notion Core Concepts! | Blocks, Pages, Databases & More

Notion’s core building blocks—workspaces, pages, blocks, and databases—fit together into a simple hierarchy: everything lives in a Workspace, that Workspace is organized with Teamspaces, content is arranged as Pages (including sub-pages), and every Page is made of movable Blocks. Once that structure clicks, the rest of Notion’s features—views, properties, sharing, and integrations—start behaving like tools for organizing structured information rather than a confusing pile of menus.

A Workspace is the “digital headquarters” where all Notion content lives: pages, databases, and files. It also anchors the operational details—settings/customizations, member management and permissions, and billing/subscription information. Multiple Workspaces can exist side by side for different purposes (for example, personal versus work), and they remain separate, each with its own members, content, and configuration.

Inside a Workspace sits a Teamspace, which functions as a team-focused subdivision. Teamspaces can’t exist without a Workspace, and they’re used to organize access and permissions more cleanly—such as separating marketing and development within the same company Workspace.

Navigation and discovery happen largely through the sidebar, which shows the page structure and lets users drill into pages, add new pages, and access areas like inbox, home, Notion AI, search, templates, settings, and trash. From there, the fundamental unit of content is the Page. A Page is a blank canvas that can hold anything—from simple habit trackers to more structured content.

Pages can nest: using slash commands (like “/page”), users can create sub-pages under a parent page, building hierarchies. But the real flexibility comes from Blocks. Inside each Page, Blocks are the individual components—text, tables, images, and more—each with its own handle (the six-dot grip) for moving, duplicating, linking, and converting into other block types. This block-based approach is what makes Notion feel different from traditional word processors: content is modular and rearrangeable.

Databases add structure. A database can be inserted inline or as its own page, and it acts like a container where every item shares the same schema. Add a property like “date,” and future entries inherit that structure even if the value is empty. Databases also support multiple database views—table, board, timeline, calendar, list, gallery, chart—so the same underlying dataset can be displayed and interacted with in different ways. Views can be added as tabs, and each view can apply sorting and filtering.

Databases can also be reused across a workspace through inline databases and linked view databases. Linked views let the same dataset appear in multiple locations; adding a new page in one place updates it everywhere.

Within databases, properties define the data model. Beyond basic fields like text, number, select, multi-select, email, phone, and formulas, two advanced property types matter for building relationships: Relation and Rollup. A Relation connects one database to another so items can reference related records (for example, ingredients linked to a “chicken” entry). A Rollup—available only when a relation exists—aggregates information from the related records, such as counting how many ingredients are associated with a dish.

Finally, Notion’s collaboration and connectivity layer includes page sharing controls (share by email with access rights, or publish to the web) and “Connections” for integrations like Slack, managed through Notion settings. The takeaway is that once Workspace → Teamspace → Page/Sub-page → Blocks → Database → Views/Properties is understood, Notion’s features become consistent parts of one system rather than separate concepts.