> ## Content Index > Fetch the complete content index at: https://notionsolutions.net/llms.txt > Use this file to discover other available public pages before exploring further. # Notion Company Wiki: Build One Your Team Will Trust (and the Plan You Need) - URL: https://notionsolutions.net/notion-company-wiki/ - Published: 2026-10-30T10:18:17.000Z - Updated: 2026-11-02T09:55:53.000Z - Description: Turn one page into a Notion wiki, give every page an owner and an expiring verification, and set access by teamspace. A 14-point plan audit shows why Plus is the floor for a team and when Business is worth it: a private HR area, verifying pages outside the wiki, or cited AI answers. - Author: Kevin Turner - Tags: template, Notion task workflows **To build a Notion company wiki, make one top-level page and turn it into a wiki with ••• → More → Turn into wiki: every page inside it then gets an Owner and a Verification field, and the wiki gets Home, All pages and Pages I own views.** Put that page in a teamspace everyone can open and give each section an owner. Plus is the floor I'd pick for any team, because a Free workspace with two or more people is capped at 1,000 blocks in total. Pay for Business only if you need a hidden HR or leadership area, verification on pages outside the wiki, or cited AI answers from the wiki. For a small company with one shared set of policies, choose Plus and the five-section skeleton below. For a company whose HR or leadership docs need an area nobody else can even see, choose Business, because private teamspaces are a Business feature; a handful of sensitive pages can still be shared page by page on Plus. A personal wiki follows the same steps, and the plan limits below mostly stop mattering, because a workspace with only one member gets unlimited blocks. What follows covers the structure, the build, owners and verification, permissions, a 14-point plan audit, search, upkeep, the public handbook and how to judge a template. ## Plan the structure before you build I'd start every company wiki with the same five sections, because a new hire should be able to guess where a page lives before searching for it: - **Start here:** the onboarding path, with the first pages a new person reads and an “Onboarding checklist”. - **Company:** mission, policies, benefits and holidays, so an “Expense policy” has one obvious home. - **How we work:** SOPs, the tools you use and your meeting rhythm. - **Teams:** one page per team, linking out to that team's own docs. - **People:** the directory of who does what. The sections live on the wiki's Home view. Notion's help suggests you “organize your pages by creating headings, then dragging and dropping specific pages under those headings”, so each section is a heading with its pages under it. I put Start here first because onboarding is where a wiki pays off soonest; [super.so's roundup of wiki templates](https://super.so/templates/notion-wiki-templates?ref=notionsolutions.net) lists faster onboarding among a wiki's benefits. Keep one company wiki, in the teamspace everyone joins. Each team's working docs belong in that team's own teamspace, and the Teams page in the wiki links to them. A wiki per person or per team splits the answers up again, which is the problem a wiki is supposed to fix. A wiki is still a page underneath. [Thomas Frank's lesson on Notion wikis](https://thomasjfrank.com/learn-notion/wikis/?ref=notionsolutions.net) describes a top-level wiki page as “essentially a regular Notion page where all sub-pages gain properties and we get light filtering options”. Frank recommends a full database “for maximum power”, and he also says “Wikis are fantastic whenever using Notion with a less tech-proficient team.” A company wiki is read by everyone and edited by a few, so I'd pick the wiki: the Owner and Verification fields are what make it trustworthy, and nobody has to learn database views to read a policy. ## Build the wiki in Notion The page you convert has to be, in the words of [Notion's help on wikis and verified pages](https://www.notion.com/help/wikis-and-verified-pages?ref=notionsolutions.net), “a standalone page that you have Full access to.” The same page states that “only pages can be turned into wikis. You can't turn a database into a wiki.” 1. Hover over the teamspace name in your sidebar and click the **+** button to add a new page in that teamspace. Name it after the company or call it “Company wiki”. 2. If the wiki should hold a database, such as the People directory, add it to this page as a full-page database now (the note below explains why). 3. Select **•••** at the top of the page, open **More** and select **Turn into wiki**. 4. On **Home**, add a heading for each of the five sections. 5. Create the section pages inside the wiki and drag each one under its heading. The wiki opens with three views. **Home** “shows you all of the pages within the wiki”, and you can add any blocks to it. **All pages** “is a database view of all the pages within the wiki”, and **Pages I own** shows only the pages you own. You can add more views with other layouts, such as a calendar, timeline or list. Every page in the wiki gets properties. Frank's lesson lists the three defaults as Owner (a Person property), Verification and Tags (Multi-select), and notes that wiki pages “can have almost all types of Database properties, except ID.” According to [notion.vip's walkthrough of the wiki feature](https://www.notion.vip/insights/notions-wiki-feature-overlooked-superpower?ref=notionsolutions.net), Owner and Verification “can be hidden but not deleted”, so plan your columns around them. Two details save a hunt through menus. Wiki home pages have a shorter **Appearance & layout** menu, without **Full width**, **Table of contents** or **Customize layout**. And if you change your mind, the same menu that converted the page has the way back: ••• → **More** → **Undo wiki**. ### Databases inside the wiki notion.vip reports that “If a page contains a full-page database when you convert it to a Wiki, that database becomes an item of the Wiki.” It adds that after conversion you can duplicate an inner database, “but you can't add one from elsewhere in the workspace.” That's why step 2 comes before the conversion: I'd create the People directory as a database on the page first, then turn the page into a wiki. A directory with photos reads well as a [gallery view of that database](https://notionsolutions.net/notion-gallery-view/). ## Owners and verification keep it true A wiki goes stale one page at a time, and the owner and verification fields are how Notion lets a person vouch that a page is still right. By default, “whoever creates a page in a wiki becomes the page's owner,” and you can change the owner at any time. To verify a page: 1. Open a wiki page you own. 2. Click the **Verification** section at the top. 3. Choose whether to verify it until a specific time or indefinitely. In the **All pages** view you can do the same by selecting the verification property value for a page you own. Verified pages show a blue check mark next to their name when they're @-mentioned and in Notion search results. When verification expires, the owner is notified in their Notion inbox and by email. Every verified page is listed in one place: go to **Settings** in your sidebar and select **Verified pages**, where you can search for a page and filter by owner or teamspace. I'd set an end date on every policy page instead of choosing indefinitely. The expiry email becomes the reminder to reread the page, so nobody has to keep a separate review calendar. The length is your call, and I'd match it to how often the policy changes: a few months for an expense policy, once a year for a holiday calendar. Indefinitely suits pages that record something settled, such as a past decision. Verification records that someone vouched for a page; whether the page is right is still the owner's judgment. The plan rules here are narrower than they look. Verifying individual pages that don't belong to a wiki is “available on Business and Enterprise Plans,” and [Notion's pricing table](https://www.notion.com/pricing?ref=notionsolutions.net) lists Verify any page only under Business and Enterprise. For verification inside a wiki, and for the Verification property you can add to a database (••• → Properties → New property → Verification, which also adds an Owner property), the help page gives no plan rule. For any page you can't verify on your plan, the [review-date setup from the SOP library](https://notionsolutions.net/notion-sop/) is the fallback: a review date, a formula that flags what's due and a view that lists it. Nothing emails the owner in that setup, so someone has to open the view. [![A Notion company wiki in two views: Home with Start here, Company, How we work, Teams and People headings, and All pages with Owner, Verification and Tags columns and two verified pages](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/notion-company-wiki-wiki-views.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/notion-company-wiki-wiki-views.webp?ref=notionsolutions.net) Home holds the five sections; All pages shows who owns each page and whether it's verified. ## Permissions and teamspaces: who sees, who edits [Notion's sharing and permissions help](https://www.notion.com/help/sharing-and-permissions?ref=notionsolutions.net) lists five access levels: - **Full access:** edit anything on the page and share it with anyone. - **Can edit:** edit the content, but not share the page. - **Can edit content:** a level “only found on database pages”. - **Can comment:** comment, without editing or sharing. - **Can view:** read the page, without commenting, editing or sharing. A subpage “will take on the permissions of its parent page,” so what you set on the wiki root flows down to every section unless you change it on a lower page. Teamspaces decide who finds the wiki at all. [Notion's teamspace help](https://www.notion.com/help/intro-to-teamspaces?ref=notionsolutions.net) defines three kinds: - **Open:** “Anyone can join and view the content inside this teamspace.” - **Closed:** “Everyone can see that this teamspace exists, but can't join unless they're invited by an owner or member.” - **Private (Business and Enterprise Plans only):** only members or owners can invite others, and “it won't be visible to people who are not added.” Turning on **Make default teamspace** adds every member of your workspace “except restricted members”, and each workspace has at least one teamspace that includes everyone. That default teamspace is the natural home for the company wiki. The pricing table checks permission groups on every plan, Free included, so you can grant access to a group such as “Managers” rather than person by person. Advanced teamspace permissions, which override a teamspace's permissions for specific people or groups, are Business and Enterprise only. The setup I'd recommend for a small company: everyone gets Can comment on the wiki root, and a small owner group gets Can edit. A comment is the easiest way for a reader to flag “this is out of date” without rewriting someone else's policy, and the owner decides what changes. Can view works too if you'd rather keep comments off policy pages. HR and leadership pages go into a private teamspace on Business. On Plus, keep them outside the wiki and share each page with “Only people invited”, where only you and the people you invite can access it. ### Permission mistakes to avoid - **Lock page doesn't hide anything.** Per [Notion's collaboration help](https://www.notion.com/help/collaborate-within-a-workspace?ref=notionsolutions.net), a locked page “will immediately become read-only for everyone” and prevents accidental edits “without fully revoking edit rights,” so [Lock page stops edits, not readers](https://notionsolutions.net/notion-lock-page-vs-database/). Anyone with full or edit access can switch the lock off from the same menu. - **A closed teamspace is visible.** Everyone can see that it exists; only joining needs an invite. If even the name of an HR area shouldn't show up, that's the job of a private teamspace. - **Your own domain makes members, not guests.** [Notion's help on members and guests](https://www.notion.com/help/add-members-admins-guests-and-groups?ref=notionsolutions.net) says “People who use one of your organization's domains are added as members, not guests, whether they join here or you share a page with them,” and on paid plans “you'll be charged per member.” Guests are free of charge but only see the pages they're invited to, and Free allows 10 of them; the [guest vs member comparison](https://notionsolutions.net/notion-guest-vs-member/) covers which role fits whom. - **A client area doesn't belong in the company wiki.** Put clients in a [client portal with its own permissions](https://notionsolutions.net/notion-client-portal-permissions/) instead of inviting them as guests to wiki pages. - **Synced blocks need access to the original.** [Notion's synced block help](https://www.notion.com/help/synced-blocks?ref=notionsolutions.net) warns: “If a user doesn't have access to the page containing the original block, they won't be able to see a synced block's contents and can request access to that page.” A policy snippet synced into the Onboarding checklist shows nothing to someone who can't open the source page, so check [who can open the original synced block](https://notionsolutions.net/notion-synced-block-permissions/) before reusing one across sections. - **Broad access wins.** “Notion respects the broadest level of access given to a user,” so a sensitive page tucked under an open section stays as open as its parent until you change it. ## Notion wiki by plan: the 14-point audit We scored 14 things a company wiki has to do against Notion's pricing table and help pages, for Free (a team of two or more), Plus and Business. Full means the feature is documented without a cap a small team hits in normal use. Capped means a numeric limit or trial-only access. No means Notion documents it as a higher-plan feature, and “Not stated in help” means the help page gives no plan rule. Enterprise is out of scope. __Company wiki requirements by Notion plan, scored from Notion's pricing table and help pages__ | Requirement | Free | Plus | Business | What decides it | | ----------------------------------------- | -------------------- | ------------------ | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | 1\. Wiki home with views of every page | Full | Full | Full | Turn into wiki carries no plan note in the [wiki help](https://www.notion.com/help/wikis-and-verified-pages?ref=notionsolutions.net) | | 2\. A named owner on every page | Full | Full | Full | The creator becomes owner by default ([wiki help](https://www.notion.com/help/wikis-and-verified-pages?ref=notionsolutions.net)) | | 3\. Expiring verification inside the wiki | Not stated in help | Not stated in help | Full | No plan rule in the wiki section; Business has [Verify any page](https://www.notion.com/pricing?ref=notionsolutions.net) | | 4\. Verify pages outside the wiki | No | No | Full | “Available on Business and Enterprise Plans” ([verified pages help](https://www.notion.com/help/wikis-and-verified-pages?ref=notionsolutions.net)) | | 5\. Open or closed teamspaces per team | Full | Full | Full | Checked on all plans in the [plan comparison](https://www.notion.com/pricing?ref=notionsolutions.net) | | 6\. A hidden HR or leadership area | No | No | Full | Private teamspaces are Business and Enterprise only ([teamspace help](https://www.notion.com/help/intro-to-teamspaces?ref=notionsolutions.net)) | | 7\. Access by group | Full | Full | Full | Permission groups on all plans; advanced teamspace permissions Business+ ([pricing table](https://www.notion.com/pricing?ref=notionsolutions.net)) | | 8\. Contractors as guests | Capped: 10 guests | Full | Full | External guest limit ([pricing table](https://www.notion.com/pricing?ref=notionsolutions.net)) | | 9\. Ask the wiki, get a cited answer | Limited trial | Limited trial | Full | Enterprise Search is Business and Enterprise ([Enterprise Search help](https://www.notion.com/help/enterprise-search?ref=notionsolutions.net)) | | 10\. See who opened a policy page | Full | Full | Full | Basic page analytics on Free and Plus ([pricing FAQ](https://www.notion.com/pricing?ref=notionsolutions.net)) | | 11\. Roll back an edit found weeks later | Capped: 7 days | Full: 30 days | Full: 90 days | Page history length ([pricing table](https://www.notion.com/pricing?ref=notionsolutions.net)) | | 12\. Keep writing with two or more people | Capped: 1,000 blocks | Full | Full | Block limit for shared Free workspaces ([block usage help](https://www.notion.com/help/understanding-block-usage?ref=notionsolutions.net)) | | 13\. Export the whole wiki | Full | Full | Full | HTML, Markdown and CSV workspace export on all plans ([pricing table](https://www.notion.com/pricing?ref=notionsolutions.net)) | | 14\. Publish the public part | Full | Full | Full | Publishing and one notion.site domain ([publishing help](https://www.notion.com/help/public-pages-and-web-publishing?ref=notionsolutions.net)) | The composite: Free covers 7 of the 14 fully, 4 with a cap, 2 not at all, and 1 is not stated. Plus covers 10 fully, leaves 1 trial-only (AI answers), misses 2, and has 1 not stated. Business covers all 14. The split says three things. Free's caps are ones a team hits in normal use: 1,000 blocks, 7 days of page history and 10 guests. Plus's two gaps are both about hiding and vouching: no private teamspace, and no verifying pages outside the wiki. Business closes both and adds Enterprise Search, whose help page says “it'll always cite its sources so you can go back to the source.” ### The 1,000-block cap is what decides Free Every piece of content you add counts as a block, per [Notion's block usage help](https://www.notion.com/help/understanding-block-usage?ref=notionsolutions.net). A Free workspace with more than one workspace owner gets 1,000 blocks per workspace, and people added to a Free workspace “can only join as workspace owners,” so the second person you invite starts the meter. Deleting blocks or emptying the trash doesn't reduce the count. When the workspace hits 1,000 blocks, Notion offers a three-day grace period; after that it needs a paid plan to keep creating content, while existing pages stay editable. Teamspaces aren't blocks, so they don't count. In my view, Free stops being a wiki tool once a second person joins. Every heading, paragraph and list item on a policy page counts toward the same 1,000, and that text is exactly what makes a wiki worth opening. My verdict: Plus for most small companies, chosen before the second person joins. Business when one of its three extras is a need you have today rather than someday: a hidden HR or leadership area, verification on docs that live outside the wiki, or cited answers from the wiki. Count the people on your email domain before you choose, since each of them joins as a member. [![Table scoring 14 company wiki needs on Notion Free, Plus and Business; Free and Plus show No for a hidden HR area and for verifying pages outside the wiki, Business is Full on all 14](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/notion-company-wiki-plan-audit.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/notion-company-wiki-plan-audit.webp?ref=notionsolutions.net) The 1,000-block cap decides Free; a private area and verification outside the wiki decide Business. ## Find things in the wiki Wiki pages show up in workspace Search like any other page. Click **Search** at the top of your sidebar, or press cmd/ctrl + P (cmd/ctrl + K if your cursor isn't in a block). Verified pages carry the blue check in the results, which helps a reader pick the current page over an old copy. Two filters in [Notion's search](https://www.notion.com/help/search?ref=notionsolutions.net) narrow things down: **In** limits results to the pages you select and their subpages, so choosing the wiki root searches only the wiki, and **Teamspace** “is visible in Plus, Business or Enterprise Plan workspaces.” Search has two blind spots to design around. Comments and discussions aren't included in search results, so when a comment thread settles a question, the owner should move the answer into the page. And a database's own search bar looks at page titles and property values, not page contents; workspace Search does look inside database pages, which is how you [find a phrase inside a database page](https://notionsolutions.net/notion-database-search-page-text/). Link instead of copying. Per [Notion's links and backlinks help](https://www.notion.com/help/create-links-and-backlinks?ref=notionsolutions.net), backlinks are “created automatically every time you @-mention a page,” so an @-mention of the Expense policy from the Onboarding checklist leaves a trail back from the policy, and there's still only one copy to keep current. People only see backlinks for pages they have access to. On Business and Enterprise, [Enterprise Search](https://www.notion.com/help/enterprise-search?ref=notionsolutions.net) takes a question typed into the search window on the Home tab and answers it with citations, drawing on [“pages in your Notion workspace that you have access to”](https://www.notion.com/help/notion-ai-faqs?ref=notionsolutions.net); the [Notion AI review for small teams](https://notionsolutions.net/notion-ai-review-small-teams/) weighs when that's worth paying for. Free and Plus get “a limited number of complimentary AI responses” to try Notion AI. ## Keep the wiki alive Expiring verification tells an owner when to look. Three more habits cover the rest of the upkeep. **Page analytics** shows whether a new policy was opened. The page's owner or an editor selects ••• → **Updates & analytics** and opens the **Analytics** tab, which shows total and unique views, per [Notion's page analytics help](https://www.notion.com/help/page-analytics?ref=notionsolutions.net). On Free and Plus, the pricing FAQ describes basic analytics as a list of page viewers plus a chart of views over time. Business adds a list of page editors, and workspace analytics is an Enterprise feature. Members can opt out in Settings → Preferences: under **Privacy**, set **Show my view history** to **Don't record**, so the viewer list can be incomplete. Analytics tells you a page was opened, not that anyone read it; if a policy needs an acknowledgment, ask for one on the page. **Page history** is [your undo for content](https://notionsolutions.net/notion-undo/): 7 days on Free, 30 on Plus and 90 on Business. A bad edit to the Expense policy that someone spots two weeks later is already outside Free's window, which is one more reason Plus is my floor. **Ownership hand-offs** are where wikis quietly rot. When someone changes roles or leaves, reassign Owner on their pages, then filter Settings → Verified pages by that owner to catch anything still verified in their name. A filter on Owner in the All pages view finds the rest, and the new owner's Pages I own view becomes their checklist. Two kinds of docs sit next to the wiki rather than inside it. SOPs get a page under How we work that points to the SOP library, and [meeting notes live in their own database and link into the wiki](https://notionsolutions.net/notion-meeting-notes/) instead of piling up as wiki pages. ## Publish the public part as its own page Some company docs are meant for outsiders: a public handbook, a careers page, press information. [Notion's publishing help](https://www.notion.com/help/public-pages-and-web-publishing?ref=notionsolutions.net) lets you publish pages to the web, claim one notion.site domain and turn on search engine indexing. Paid plans add search engine optimization, themes and Google Analytics, and a custom domain is a purchased add-on. To publish, open **Share**, open the **Publish** tab and select **Publish**. Don't publish the wiki root. “Publishing a Notion page to the web means all of its subpages will be published too,” so I'd keep the public handbook as its own page outside the wiki, with only public pages under it. Published pages also carry contributor details: the page's metadata “will include the names, profile photos, and email addresses associated with any Notion users that have contributed to the page.” The guide to [building a Notion website](https://notionsolutions.net/notion-website/) covers the site settings. For a copy outside Notion, the pricing table lists “Export entire workspace as HTML, Markdown, & CSV” on every plan and workspace PDF export on Business and Enterprise; for a single database such as the People directory, follow the steps for [exporting a Notion database](https://notionsolutions.net/notion-export-database/). ## Company wiki templates: what to check first The [Marketplace's wiki category](https://www.notion.com/templates/category/wiki?ref=notionsolutions.net) showed 3,072 templates when checked, so the work is ruling most of them out. Before you duplicate one, ask five questions: 1. **Is it a real wiki?** Look for Owner and Verification columns and a Home view. Nested pages without them give you none of the upkeep tools above. 2. **Does it assume Business features?** A template built around a private teamspace or verified pages outside the wiki won't work as designed on Free or Plus. 3. **How many blocks does it add?** On Free with two or more people, every block counts toward the 1,000. 4. **Are there sections nobody would own?** Delete them before launch; an unowned page is the first one to go stale. 5. **Does it use embeds or synced blocks guests can't see?** A synced block shows nothing to someone without access to the original page. I'd build the five-section skeleton first, then borrow one page type from a template, such as a policy page layout or an onboarding checklist. You get the template's useful part without importing a structure nobody on your team chose. ## Verdict and first actions A Notion company wiki works when every page has an owner and an expiry, and when the plan doesn't cap the writing. Choose Plus before the second person joins. Choose Business when a hidden HR or leadership area, verification outside the wiki or cited AI answers is a need today. Then, in this order: 1. Create the Company wiki page in the teamspace everyone joins and turn it into a wiki. 2. Add the five sections on Home: Start here, Company, How we work, Teams and People. 3. Give each section an owner. 4. Set expiring verification on every policy page. 5. Give everyone Can comment on the root and the owner group Can edit. ## Questions about Notion wikis ### Can I turn an existing database into a wiki? No. Notion's help says “only pages can be turned into wikis.” Put the database on a page instead and convert the page: per notion.vip, a full-page database on a page you convert becomes an item of the wiki. ### Is a Notion wiki free? Turn into wiki carries no plan note in Notion's help, and the audit above scores the wiki home and owners as Full on every plan. For a team, though, a Free workspace with two or more people is limited to 1,000 blocks, which is why I'd start a company wiki on Plus.