Creating teamspaces for your organization

Notion Teamspaces are designed to tame complex permissions by letting organizations organize work into customizable “channels” with clear rules for who can join and who can see what. The core decision is how each Teamspace is set up—open, closed, or private—because that choice determines both membership behavior and page visibility. Open Teamspaces let anyone join and view pages inside; closed Teamspaces are visible but require an invitation to join and block page viewing; private Teamspaces hide even the Teamspace’s existence, limiting visibility to members only. These settings directly shape day-to-day navigation and reduce the risk of people stumbling into the wrong information.

Creating a Teamspace starts in the sidebar: click the plus button next to “Teamspaces” (or go to “All Teamspaces” and select “New Teamspace”). Each Teamspace needs a name, description, and icon, followed by permission settings (open, closed, or private). After creation, the workflow shifts to provisioning: add members by typing their email or name, and decide whether they are members or Teamspace owners. Owners carry higher responsibility—able to adjust settings and security—while members get lower access, typically limited to contributing within the boundaries set for that Teamspace.

A key operational lever is the “default Teamspace” setting. Organizations can toggle on a default Teamspace so everyone in the workspace is automatically included, but the guidance is conservative: most teams should use only one default Teamspace, and even large organizations should avoid more than three to prevent sidebar clutter.

For structure, Teamspaces work best when they follow a consistent page hierarchy. Each Teamspace should include a home page plus top-level pages for sub-teams, along with important database views or knowledge-based pages. Everything else should be nested as subpages under those top-level sections. This approach improves transparency and reduces the ongoing management burden on Teamspace owners.

The transcript also emphasizes when to deviate from the default recommendation that Teamspaces be open. Closed Teamspaces fit situations where content visibility needs tighter control—such as limiting what managers can view. Private Teamspaces are suited to sensitive or semi-anonymous work, with HR using private spaces for collecting employee feedback and accounting using them for compensation and benefits discussions.

Three implementation patterns illustrate the trade-offs. One model creates a Teamspace per department with minimal admin control, maximizing org-wide visibility but increasing the chance of messy, disorganized content. Another organizes by projects, using a general documents/knowledge base Teamspace with project-based subpages for members; this personalizes the sidebar but reduces visibility into projects outside a person’s assignment—often a better fit for project-driven organizations. A cautionary example shows Teamspaces created haphazardly (multiple overlapping spaces and missing spaces), which quickly confuses users because it becomes unclear where information lives and too many competing options appear. The takeaway is that there may not be a single “right” architecture, but thoughtful permission choices and a disciplined page structure are what keep Teamspaces scalable and usable as teams grow.