🏢 Lesson 6.2: Teamspaces & Wikis

Your Private section is your own. A teamspace is a shared area a whole group lives in together, and a wiki turns an ordinary page into a trusted, verifiable knowledge home. In this lesson you'll learn how teamspaces work, who can do what, and how to build a wiki — while we're honest about which pieces cost money. Solo learners: this one is genuinely optional for you, and we'll tell you exactly what's worth a look anyway.

📚 What You'll Learn

By the end of this lesson, you will be able to:

Explain how a teamspace differs from your Private section
Choose between open, closed, and private teamspaces (and know which need a paid plan)
Describe workspace roles — owner vs. member — and what admin controls require
Turn a page into a wiki, verify pages, and set page owners
Design a simple team home/hub — or decide you don't need one at all

⏱️ Estimated Time: 55 minutes

🎯 Project: Create a teamspace (or a "Shared" section if you're solo), convert a page into a wiki, and add a sub-page under it.

In This Lesson

🏠 Private vs. Shared: Teamspaces

Look at your left sidebar. You've been living in the Private section — pages only you can see. A teamspace is a second kind of area: a shared home that a group of people can open, organize, and work in together, right alongside your private pages.

Here's the analogy. Your Private section is your own office — your desk, your files, nobody else's business. A teamspace is a shared department floor: the marketing team's floor, the design team's floor. Everyone assigned to that floor sees its pages in their sidebar automatically, so the team's knowledge has one obvious home instead of being scattered across individuals' private pages.

graph TD A["🏢 Workspace"] --> B["🔒 Private
(just you)"] A --> C["👥 Teamspace: Marketing"] A --> D["👥 Teamspace: Engineering"] C --> E["📄 Campaign Plan"] C --> F["📄 Brand Wiki"] D --> G["📄 Roadmap"] D --> H["📄 Runbooks"]

The key difference from sharing a single page (last lesson): a teamspace is a durable, structured area with its own membership and settings, not just one page you handed to a friend. When someone joins the Marketing teamspace, they get everything in it and future pages too — no re-sharing each new page.

💡 Default teamspace

Every multi-person workspace has a default teamspace that all members join automatically — a natural home for company-wide, everyone-should-see-this material. Additional teamspaces let you carve out per-team or per-project areas on top of that shared baseline.

🚪 Open, Closed & Private Teamspaces

Teamspaces come in three visibility levels. Think of them as three kinds of door on that department floor.

Type	Who can see it?	Who can join?	Plan
Open	Everyone in the workspace	Anyone can join themselves	Free / any plan
Closed	Everyone can see it exists	Only members can add people	Business
Private	Only its members — hidden from others	Only members can add people	Business

An open teamspace is the transparent default — great for anything the whole organization benefits from seeing. Closed and private teamspaces add confidentiality (an HR or leadership space, say), and those tighter controls sit on the Business tier and up.

⚠️ Honesty check

The ability to create teamspaces and use open ones is broadly available, but closed and private teamspaces, along with the richer admin controls around them, are Business/Enterprise features. Plan boundaries shift over time, so confirm what your plan includes at notion.com/pricing rather than assuming. If you're on a free personal workspace, you likely won't see teamspace management at all until other members exist.

🎭 Members & Roles

Two layers of "who are you" matter in a shared workspace: your role at the workspace level, and your role within a teamspace.

Workspace roles

Workspace owner (admin) — can manage members, billing, security settings, and teamspaces across the whole workspace. The most powerful role.
Member — a normal participant who can create and edit content and join open teamspaces, but doesn't control workspace-wide settings.

The advanced admin controls — provisioning members, security policies, audit logs, and the like — are paid capabilities that grow with Business and Enterprise.

Teamspace roles

Within a teamspace, someone can be a teamspace owner (manages that space's members and settings) or a teamspace member (works in it). You can be a workspace member but a teamspace owner of the one space you run — the two layers are independent.

⚠️ Every member is usually a seat

Remember the billing reality from Lesson 6.1: members generally cost a per-seat fee on paid plans. Adding ten members means paying for ten seats. That's the honest trade — teamspaces are a team feature, and teams are what paid Notion is priced around. Guests (specific-page access) remain the free-friendly path for occasional outsiders.

📚 The Wiki Feature

A wiki is a special kind of page built for reference knowledge — the place a team's "how we do things" lives. Any page can be turned into a wiki, which unlocks a few knowledge-base powers on top of a normal page.

To create one, open a page, click the ⋯ menu, and choose Turn into wiki. The page becomes a wiki home, and its sub-pages become entries you can browse, filter, and manage as a collection. Wikis add two things a normal page doesn't have:

Owners — each wiki page can have an assigned owner responsible for keeping it accurate. Readers instantly know who to ask.
Verification — an owner can mark a page Verified, optionally with an expiration date. A little ✓ badge tells readers "this is current and trusted," and it can nudge the owner to re-verify when it goes stale.

📚 Onboarding Guide

✅ Verified 👤 Owner: Priya · expires in 90 days

📄 Day-one checklist

📄 Tools & accounts

📄 Who's who

The green Verified badge and named owner are what separate a wiki from a plain nested-page collection — readers trust it because someone is accountable for it.

✅ Home/hub patterns for a team

A great team home is usually a wiki with a clear structure: a short "start here" intro, links to the most-used pages, and sub-pages grouped by topic (Policies, How-tos, Projects, People). Pin it as the teamspace's landing page so every member arrives somewhere useful instead of a wall of pages. Keep it curated — a wiki's value is that it's trustworthy, not exhaustive.

💡 Wikis work for one person too

Even solo, "turn into wiki" is handy for your own reference material — a personal knowledge base of notes, recipes, or research where verification reminds you to keep pages current. Don't skip it just because you're a team of one.

🙋 Do You Even Need This?

Honest answer for solo learners: mostly, no. Teamspaces, roles, and closed/private spaces exist to coordinate groups. If it's just you, your Private section already does everything a teamspace would, and paying for member seats would be spending money on a problem you don't have.

Here's a quick way to tell where you stand:

graph TD A["Will other people
work in this regularly?"] -->|"No — just me"| B["🔒 Stay in Private
(maybe a 'Shared' section
for pages you send out)"] A -->|"Yes — a small group"| C["👥 Use teamspaces"] C --> D{"Need to hide a space
from other members?"} D -->|"No"| E["Open teamspace
works on most plans"] D -->|"Yes"| F["Closed / Private
needs Business+"]

🧠 Mindset

If this lesson feels like it's about someone else's world — a big company, a busy team — that's completely fine. You don't need to master this today, or maybe ever. Skim it, do the solo-friendly version of the project so the mechanics aren't a mystery, and move on with a clear conscience. Notion scales up when you need it; it never demands you grow before you're ready.

🎯 Project: Teamspace + Wiki

You'll set up a shared area and build a small wiki. There are two paths — pick the one that matches your situation. Both teach the same core moves.

🏋️ Build a shared area and a wiki

Objective: Experience creating a shared space and converting a page into a verifiable wiki with a sub-page.

Instructions (about 15 minutes):

(4 min) Team path: In the sidebar, hover over your teamspaces and click + (or Settings → Teamspaces → New teamspace). Name it (e.g. "Project X"), and leave it Open for now.
Solo path: Create a top-level page called Shared — a single home for anything you'll ever share out. This mirrors what a teamspace does, without seats.
(4 min) Inside it, create a page called Team Wiki (or My Knowledge Base). Open its ⋯ menu and choose Turn into wiki.
(3 min) Add a sub-page under the wiki — for example Getting Started. Notice it becomes a wiki entry.
(2 min) On that sub-page, set an Owner (yourself) and mark it Verified. Watch the ✓ badge appear.
(2 min) Back on the wiki home, write a one-line "start here" intro so future readers (or future-you) land somewhere useful.

💡 Hint — don't see "Turn into wiki"?

It lives in the page's ⋯ (more) menu at the top-right. If your workspace is a solo free one and options look limited, just do the solo path — a normal page + sub-pages teaches the structure, and you can revisit wikis when you're on a plan that exposes the full feature.

✅ Project Completion Checklist

You created a teamspace or a "Shared" home page
You turned a page into a wiki (or built the solo equivalent)
You added a sub-page under it
You set an owner and marked a page Verified (if available)
Your wiki home has a short "start here" intro

🎯 Quick Quiz

Question 1: What best describes the difference between your Private section and a teamspace?

Question 2: Which of these typically requires a paid (Business+) plan?

Best Practices for Teamspaces & Wikis

✅ Do's

Start with one teamspace. Don't shard a small team into ten spaces — begin with the default and grow only when a group clearly needs its own home.
Give every wiki page an owner. Accountability is what makes a wiki trustworthy.
Verify what's current, expire what changes. A verification date keeps knowledge from quietly going stale.

❌ Don'ts

Don't pay for seats you won't use. Occasional outsiders belong as guests, not members.
Don't make everything private. Open teamspaces build trust and cut duplicate questions; reserve closed/private for genuinely sensitive spaces.
Don't let the wiki sprawl. A curated, verified hub beats an exhaustive dumping ground nobody trusts.

📓 Learning Journal

Keep a learning journal — the best place is inside your own Notion. After each lesson, take a few minutes to write down:

Key concepts you learned
Techniques that clicked for you
Questions or confusion points to revisit
Ideas you want to try
Your progress and feelings about learning this

✍️ This lesson's prompt: Do you work in Notion alone or with others? If alone, what personal knowledge would benefit from being a wiki? If with a team, sketch the one teamspace and the three or four wiki pages that would help most.

📝 Lesson Summary

🎓 Key Takeaways

A teamspace is a shared area a group joins and sees automatically — distinct from your Private section.
Teamspaces come in open (broadly available), closed, and private — the latter two need Business.
Roles split into workspace owner vs. member and teamspace owner vs. member; advanced admin controls are paid, and members are usually per-seat.
A wiki turns a page into a knowledge home with owners and verification badges.
Solo users can safely skip most of this — a Private section (or a "Shared" page) is plenty.

🎉 What You've Accomplished

You now understand how Notion scales from one person to a coordinated team: shared teamspaces, clear roles, and wikis that people can actually trust. Just as importantly, you can tell the difference between features you need and features you'd only be paying for — which is the kind of judgment that keeps your Notion (and your wallet) healthy.

❓ Common Questions at This Stage

I'm just one person — did I waste time on this lesson?

Not at all. You now know what teamspaces are for, so if you ever join a team's workspace or grow your own, none of it will be a mystery. And the wiki feature (owners, verification) is quietly useful even solo, for keeping your own reference pages honest.

What's the real difference between a wiki and just nesting pages?

Mechanically they're similar — a page with sub-pages. A wiki adds owners and verification, plus a browsable home view. Those turn a pile of pages into a trusted knowledge base where readers know what's current and who's accountable.

How much does adding a teammate cost?

Members are generally billed per seat on paid plans, so each teammate you add as a member increases the bill. Exact per-seat pricing changes, so check notion.com/pricing. For occasional collaborators, remember guests (from Lesson 6.1) are the free-friendlier route.

🔭 Looking Ahead

You've built the shared spaces. Next we make them come alive with day-to-day collaboration — Comments, Mentions & Working Together: leaving inline notes, @-mentioning people and dates, your Inbox, and staying in sync. It's just as useful for reminding future-you as for nudging a teammate.

✅ Before the Next Lesson

Keep the wiki (or "Shared" page) you built — we'll comment and mention on it next
Decide whether you'll practice the next lesson solo or with a real collaborator
Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

Whether you're a team of twenty or a team of one, you now know how Notion holds shared knowledge — and how to keep it trustworthy. There's no pressure to use any of it before you need it. Build for the size you actually are. 🏢