Notion Basics: Building a team workspace

TL;DR

Keep all company work in a shared workspace when possible to simplify cross-functional collaboration and content sharing.

Briefing Cornell Notes

Briefing

A Notion workspace can be built into a living “team long-term memory” system by combining pages, blocks, and databases—without forcing teams into rigid templates. The core takeaway is that Notion’s building blocks let teams start with a simple wiki, then progressively turn static text into structured, searchable information (including database-backed views like calendars and boards) that multiple people can use and update.

The session begins with a workspace tour of the default team workspace and how Notion organizes work. Workspaces are accessed from the top-left workspace switcher, and account-level settings (like display name, avatar, and language) apply across all workspaces, while workspace-level settings affect only the current workspace. Members and admins are managed from the settings area; admins can make high-impact changes such as billing and security, so the guidance is to keep the admin group small. Collaboration is emphasized early, including adding co-workers directly into the workspace.

From there, the focus shifts to pages and the sidebar. Everything in Notion lives on a page, and pages are grouped in sidebar sections such as Public/Workspace, Shared, Private, and Favorites. Sidebar items often represent top-level pages, while additional content sits inside them as sub-pages. For quick access, frequently used pages can be favorited so they appear in the Favorites section. Navigation is intentionally kept manageable: the recommendation is to keep the sidebar minimal and rely on sub-pages for deeper structure.

After the tour, the session builds a business wiki from scratch using blocks. The “wiki” is defined as a central repository for policies, goals, employee information, engineering practices, and anything a new hire needs. The demo starts with bullet points and value statements, then uses Notion’s formatting shortcuts (like bold) and interactive elements such as toggles to hide or reveal details. A key concept is that every piece of content—text, toggles, lists, and more—is a block. Notion includes more than 500 block types, and the session frames them as “lego blocks” for software: mix and match to create tailored workflows.

Blocks can be inserted with slash commands (or the plus button) and converted using the six-dot menu (“turn into”). The demo shows turning mission and values into headings and converting bullet lists into pages, making the wiki feel more like a website. It also demonstrates media blocks (like images from Unsplash) and layout controls such as dragging blocks into columns and adding icons.

The most practical upgrade comes with databases. A “meeting notes” table is created as a database where each row represents a meeting and each column is a typed property (text, tags, date, people). Because it’s a database, the same underlying data can be displayed in multiple views: table, board, timeline, calendar, list, and gallery. The calendar view is used to show meetings on dates, and view properties can be adjusted via a properties menu. The session reinforces a best practice: keep related information in one database so views, filters, and sorting stay consistent.

By the end, the workflow expands beyond basic editing into collaboration and customization features: permissions via locking and sharing, database views that don’t affect others, filtering by person (e.g., meetings where “meeting attendees contains me”), and synced blocks for updating the same content across multiple pages from one source. Templates and Notion’s help resources are offered as shortcuts for teams that want ready-made structures like CRM setups or other workflows.

Cornell Notes

Notion’s team workspace becomes useful when content is organized into pages, built from blocks, and—when needed—structured into databases. The session starts with workspace basics (switching workspaces, managing members/admins, and using sidebar sections like Private and Favorites) and then builds a business wiki as a “team long-term memory.” Blocks are treated as the fundamental unit: text, toggles, headings, images, and more can be inserted with slash commands and converted via “turn into.” The meeting notes database shows how typed columns (text, tags, date, people) power multiple views such as table and calendar, enabling teams to manage the same data in different ways. Synced blocks and templates round out the workflow by reducing repetitive updates and speeding up setup.

How does Notion’s page and sidebar structure help teams organize a workspace over time?

Notion content is organized into pages, and pages appear in the sidebar under sections like Workspace/Public, Shared, Private, and Favorites. Sidebar entries usually represent top-level pages; additional content inside them is handled as sub-pages. For frequently accessed items (like an active project plan), favoriting moves that page into the Favorites section so it stays easy to find. The guidance is to keep the sidebar minimal because nested sub-pages provide the depth without clutter.

What are “blocks,” and why does converting blocks matter for building a wiki?

A block is the basic unit of construction on a Notion page—when the cursor hovers over elements, the interface shows a six-dot handle for each block. Text, bullet lists, toggles, headings, and even media are all blocks. Converting blocks (via the six-dot menu and “turn into”) lets teams transform a static document into a more structured site-like layout—for example, turning mission/value statements into headings or converting bullet lists into pages.

How do databases in Notion differ from a spreadsheet, and what does “typed” data enable?

Databases look familiar like tables, but each column has a specific property type. In the meeting notes example, rows represent meetings, while columns include types like text (meeting name), tags (team/group), date (meeting date), and people (meeting attendees). Because each column has a defined type, Notion prompts the right kind of input (calendar picker for dates, people selection for attendees), which makes the data consistent and usable for multiple views.

Why can one database support many views (calendar, board, list), and how does that help teams?

A single database stores the underlying data, and views are different ways to display and interact with that same dataset. The session demonstrates switching from a table view to a calendar view, where meetings appear on specific dates. It also notes that adding properties to a view (via a three-dot menu) changes what’s shown without rebuilding the dataset. This reduces the need to connect separate tools or duplicate information across places.

What collaboration and permission controls were highlighted for pages and shared work?

Pages can be locked so others can’t edit them, and pages can be placed in the Private section so only the creator can see and edit them. Sharing uses a share button to grant access to specific people in the workspace; shared pages then appear in the appropriate sidebar section for those who received access. For admins, the session recommends keeping the number of admins small because admins can change billing and security settings.

How do synced blocks reduce repetitive updates across a workspace?

Synced blocks let one block’s content stay consistent across multiple locations. The demo copies a block link (for example, the mission statement) and pastes it elsewhere as a synced block. When the mission text is edited in one place, the change propagates to every synced instance—useful for repeated management information like mission, values, or other frequently referenced details.

Review Questions

When should a team use sub-pages versus favoriting a page in the sidebar?
In the meeting notes database example, what property types were used for meeting date and meeting attendees, and why does typing matter?
How do synced blocks differ from simply copying and pasting text into multiple pages?

Key Points

1
Keep all company work in a shared workspace when possible to simplify cross-functional collaboration and content sharing.
2
Use sidebar sections (Workspace/Public, Shared, Private, Favorites) and sub-pages to organize depth without cluttering navigation.
3
Treat blocks as the fundamental unit of content; use slash commands to insert them and the six-dot menu to convert them into headings, pages, and other structures.
4
Use databases for structured, typed information so the same dataset can power multiple views like table and calendar.
5
When building workflows, prefer keeping related items in one database so filters, sorting, and views stay consistent without reconnecting data across tools.
6
Apply page-level controls like locking and sharing to manage editing permissions and protect key documents.
7
Use synced blocks for repeated content (e.g., mission/values) so updates happen once and propagate everywhere.

Highlights

Notion’s “blocks” make every element editable and convertible, letting a simple document evolve into a structured wiki or site-like layout.

A meeting notes database demonstrates how typed columns (text, tags, date, people) enable consistent data entry and multiple views from the same underlying records.

Calendar, board, list, and gallery views are different lenses on one database—so teams can manage the same information in the format they need.

Synced blocks prevent copy/paste drift by linking one block’s content across multiple pages for centralized updates.

Topics

Workspace Setup
Pages and Sidebar
Blocks
Databases and Views
Synced Blocks

Mentioned

Zoe Ludwig