When a company has five or more departments—technical, legal, accounting, marketing, and management—structuring Notion as a unified knowledge and planning system requires deliberate architecture. The right setup gives each team its own focused workspace while keeping cross-team tasks visible and the company's knowledge base connected.
The Core Architecture: Master Databases + Linked Views
The single most important best practice for multi-department Notion setups is the master database approach. Instead of creating separate, disconnected databases for each team, you create one central database (or a small set of them) and then display linked, filtered views of those databases in each team space.
Here is how that works in practice:
- Create a master task database in a shared or general team space.
- In each team's space, add a linked view of the database filtered to show only that team's tasks.
- Apply a person property to every task so you can filter by assignee.
This means a task that starts in the technical team and needs accounting review lives in one database, not two. Changes made in either view are reflected everywhere instantly.
Why Not Just Create Separate Databases Per Team?
Separate databases seem simpler at first, but they create real problems:
- Tasks that cross team boundaries need to be duplicated or manually copied.
- Reporting across the company becomes nearly impossible.
- Cross-functional work (like logging an invoice and routing it to accounting) has no natural home.
One master database with filtered views solves all three.
Setting Up Team Spaces
Notion team spaces let you organize content by department while controlling visibility. There are three access levels to understand:
- Open: Anyone in the workspace can see and join the space.
- Closed: Everyone can see the space exists but cannot join without an invite.
- Private (Business and Enterprise plans only): The space is invisible to anyone who is not a member.
For most multi-department companies, the recommended setup is:
- One general team space visible to everyone, containing the master databases and company-wide knowledge base.
- One private or closed team space per department, containing team-specific views, SOPs, and documentation.
Moving Databases Between Team Spaces
One common worry when setting up Notion for the first time is making mistakes. If you create a database in a private team space and later decide it belongs in the general space, you can simply drag it to the new location. Notion preserves all references and linked views when you move a database. You will not break anything as long as the people who have access to the new location also have access to any databases that are linked inside it.
Sharing Databases Across Private Spaces
If a database lives in a private team space, it is not automatically visible to people outside that space—even if you reference it elsewhere. However, you can share individual pages or databases with specific people, and a Shared section will appear in their sidebar for that content.
This is useful when a mostly private team (like legal) needs to share a specific document or database view with one other department without opening the entire team space.
Structuring Your Knowledge Base
Beyond tasks, most companies have knowledge that should be shared across departments:
- Site documentation (relevant to an operations team and management)
- Vendor contracts (relevant to legal and finance)
- Onboarding SOPs (relevant to HR and management)
The best approach is to keep this content in the general team space, organized by topic. Use pages as containers and databases for structured content (like a vendor list or asset inventory). Each team can then link to or embed relevant sections in their own space.
Linking Data for AI Context
One underrated reason to use master databases with strong relations is Notion AI. The more your data is connected—tasks linked to projects, projects linked to sites, sites linked to contacts—the more context Notion AI can draw on when answering questions or summarizing information. Building with relations from the start pays dividends as your AI usage grows.
Next Steps
The best way to start is to:
- Create a general team space and add your first master task database there.
- Create one linked view of that database in a second team space with a team-specific filter applied.
- Add a person property and test the "me" filter so you can see it working.
- Then build out your knowledge base pages around the same structure.
Get help structuring Notion for your company
Structuring Notion for a multi-department company usually breaks when teams create separate databases and can't track cross-functional work. We've helped dozens of growing companies set up the master database architecture above — and get it right the first time. Book a ZoomFlow session and one of our certified Notion consultants will map out the right workspace structure for your team in a single call.
