All posts
Allen
Author, Content Operations Manager·Originally published Nov 7, 2025 · Updated Oct 27, 2026

Corporate Wiki: How to Build a Company Wiki People Use

A company wiki works when it starts with real questions, uses five simple spaces, and gives every page an owner and a review date. Here is the template, the rollout plan, and how 7 tools compare.

Corporate wiki guide: five company wiki spaces for company, teams, processes, onboarding, and decisions, each with an owner and review date

A corporate wiki (also called a company wiki or internal wiki) is a shared, editable set of pages where employees write down how the company works: policies, processes, team pages, onboarding guides, and decisions. Anyone with access can find, edit, and link pages, so the knowledge lives in one searchable place instead of in chat threads and people's heads.

This guide covers what to put in a company wiki, a structure you can copy, who should own it, a 30-day rollout plan, and how seven common tools compare on price and hosting. It ends with the mistakes that kill most wikis within a year.

At a glance

  • Start small: five top-level spaces (Company, Teams, Processes, Onboarding, Decisions) and 20–30 seed pages beat an empty structure with 200 placeholders.
  • Assign owners, not editors: every page needs one named owner and a review date. Everyone else can still edit.
  • Pick the tool last: decide structure, ownership, and hosting needs first. Notion, Confluence, Slite, Nuclino, Outline, BookStack, and AFFiNE all work if the rules are in place.
  • Measure use: track searches with no result and pages past their review date, not page count.

Published on the AFFiNE blog. AFFiNE makes one of the tools compared below. Vendor prices and plan limits were checked on each vendor's official pricing page on October 27, 2026. We did not benchmark the tools for this article.

Corporate wiki structure: five top-level spaces for company, teams, processes, onboarding, and decisions, each with example pages

What is a corporate wiki?

A corporate wiki is an internal website made of pages that employees can create and edit. Pages link to each other, have a change history, and are searchable. The idea comes from Wikipedia, but the audience is your own staff and access is limited to people you invite.

"Corporate wiki", "company wiki", and "internal wiki" mean the same thing in practice. Larger organizations tend to say corporate wiki; startups and agencies tend to say company wiki or team wiki. Engineers often say internal wiki or internal docs.

A wiki is different from three nearby tools:

ToolWho writesWhat it holdsTypical example
Corporate wikiAny employee, with page ownersHow the company works, living reference"How we run a release", team pages, holiday policy
Knowledge baseA small team of writers or support staffCurated answers to known questions, often for customers"How do I reset my password?"
IntranetInternal communications, HRNews, announcements, links to systemsCEO update, office closures
Shared driveEveryone, unstructuredFiles: contracts, decks, spreadsheetsSigned contracts, board decks

Many companies run a wiki and a knowledge base side by side. If you are deciding between them, our guide on what a knowledge base is explains where curated answers fit better than open editing. For the wider category, see knowledge management software. For a side-by-side look at governance, search, and when to run both, read our wiki vs knowledge base comparison.

Why companies build an internal wiki

The case for a wiki is rarely "we need more documentation". It is usually one of these problems:

  • The same questions in chat every week. "Where is the brand kit?" "How do I request a laptop?" Each answer is written once in a wiki and linked forever.
  • Slow onboarding. New hires spend their first weeks asking who owns what. A good onboarding space cuts that to a reading list and a checklist.
  • Knowledge leaving with people. When the only person who knows the billing run goes on leave, a written process is the difference between a delay and an incident.
  • Decisions that get relitigated. A short decision log ("we chose Postgres over MySQL in March because...") stops the same debate every quarter.
  • Remote and multi-timezone teams. Written answers do not depend on someone in another timezone being awake.

If none of these hurt yet, a single shared doc with a table of contents may be enough. As a rule of thumb, not a measured threshold, a wiki earns its overhead once you have roughly 15 people or more than two teams that depend on each other.

What to put in a company wiki

Start with pages people already ask for. A useful test: search your team chat for "where is", "how do I", and "who owns". The top 20 answers are your first wiki pages.

Content that belongs in almost every company wiki:

  1. Company basics: mission, org chart or team directory, who to ask for what, office and remote work rules, holiday calendar.
  2. Policies: expenses, travel, security basics, equipment, leave. Link to the signed HR version if one exists; the wiki page is the readable summary.
  3. Team pages: one page per team with what they own, how to request work from them, their current priorities, and their recurring meetings.
  4. Processes and how-tos: release process, month-end close, incident response, customer escalation, hiring loop. Write these as numbered steps.
  5. Onboarding: a first-week checklist, accounts to request, people to meet, and reading order for the rest of the wiki.
  6. Decision log: short records of important decisions with date, owner, context, options considered, and the choice.
  7. Glossary: internal acronyms, product names, and customer segment names.

What does not belong: files that need signatures (keep them in the document system and link), secrets and passwords (use a password manager), fast-moving task status (keep it in the project tool), and personal notes.

A company wiki structure you can copy

Five top-level spaces cover most companies from 15 to 500 people:

SpaceExample pagesDefault ownerReview cadence
CompanyMission, team directory, holidays, who to askPeople or operations leadEvery 6 months
TeamsOne page per team: scope, requests, ritualsEach team leadEvery quarter
ProcessesReleases, expenses, incident response, hiringProcess ownerEvery quarter, and after each change
OnboardingFirst week checklist, accounts, reading listPeople lead + a recent hireAfter every hiring cohort
DecisionsDated decision recordsPerson who made the decisionNot reviewed; superseded by new records

Keep the tree no deeper than three levels. If people need a fourth level, the page usually needs splitting or a link from a hub page, not another folder.

A simple page template keeps pages consistent without slowing writers down:

  • Title that matches how people search ("Expense policy", not "Finance > Policies > Reimbursement v3").
  • Owner and last reviewed date at the top.
  • Summary in two or three sentences: what this page answers.
  • Steps or details, using numbered lists for processes.
  • Related pages at the bottom.

Who owns the wiki: governance that stays light

Wikis rarely fail because of the software. They fail because nobody is responsible for keeping pages true, the same problem that stalls a team knowledge base. Governance does not need a committee. It needs three roles:

  • Wiki lead (one person, a few hours a month). Owns the top-level structure, the page template, and the monthly health check. Often someone in operations, people, or developer experience.
  • Space owners. Each top-level space has an owner who approves new sub-sections and chases stale pages in their area.
  • Page owners. Each page names one person. They do not have to write every edit, but they confirm the page is still correct at each review date.

Simple rules that make this work:

  1. Everyone can edit; owners approve structure. Open editing keeps typos and small updates cheap. Only space owners create new top-level sections.
  2. Every page has a review date. Set quarterly for processes and every six months for reference pages. Most tools let you show the date in the page header even if they do not track it automatically.
  3. Archive, do not delete. Move outdated pages to an Archive space with a note that points to the replacement.
  4. Link instead of copy. If information already lives in the HR system or a project tracker, link to it so there is one source of truth.
  5. Permissions follow sensitivity, not org charts. Make most of the wiki readable by everyone. Restrict only the spaces that truly need it, such as HR cases or legal.

Company wiki ownership model: a wiki lead, space owners, and page owners with a review cycle of write, review, update, and archive

How to roll out a company wiki in 30 days

A wiki that launches empty stays empty. This plan front-loads the content people need and builds the habit in the first month.

  1. Days 1–3: collect the questions. Search chat and email for repeated questions. Ask each team lead for the five things new hires always ask them. Pick 20–30 pages to seed.
  2. Days 3–5: choose the tool and structure. Set up the five spaces, the page template, and permissions. Shortlist tools with the comparison below and try importing two existing documents before committing.
  3. Days 5–15: write the seed pages. Assign each page to an owner with a deadline. Short and correct beats long and polished: a page with seven accurate steps is finished.
  4. Days 15–20: test with new or recent hires. Ask two people who joined recently to answer ten real questions using only the wiki. Every miss becomes a page or a fix.
  5. Day 21: launch. Announce it with three links to useful pages, not a tour of the tool. Pin the wiki home page in your chat tool.
  6. Days 21–30: answer with links. When a question shows up in chat, reply with a link to the page. If the page does not exist, write it and then link it. Team leads doing this consistently matters more than any training session.
  7. Day 30: first health check. Review searches that returned nothing, pages with no owner, and pages nobody opened. Fix the top ten.

After the first month, the wiki lead runs the health check monthly and space owners review pages on their due dates.

Corporate wiki software compared

Most teams choose between hosted all-in-one workspaces, dedicated wiki tools, and self-hosted wikis. The table lists what each vendor publishes on its pricing page. Prices are per user or per seat per month and change often, so confirm them before you buy. If you are still choosing between hosted and self-hosted, start with this hosted vs self-hosted comparison.

ToolBest forFree optionPaid plans (listed)Self-hosting
NotionTeams that want wiki pages and databases in one hosted toolFree plan; multi-member workspaces have a block limitPlus $10/seat, Business $20/seatNo
ConfluenceCompanies already on Jira and AtlassianFree for up to 10 usersStandard from $5.78/user, Premium from $11.16/userData Center closed to new customers since March 30, 2026
SliteSmall teams that want a focused wiki with AI answersFree trialBasic $10/user, Pro $20/user (billed yearly)No
NuclinoSmall teams that want a fast, simple wikiUp to 50 items, 3 canvases, 2 GBStarter and Business; check the vendor page for current pricesNo
OutlineTeams that want a clean wiki they can host themselvesSelf-hosted Community edition at $0, no supportCloud from $10/month; paid self-hosted licensesYes
BookStackIT teams that want a structured, MIT-licensed wikiFree and open source (MIT)NoneYes (self-host only)
AFFiNETeams that write docs, whiteboards, and databases togetherFree cloud plan with 10 GB and 3 members per workspaceTeam $10/seat (see pricing page)Yes, free up to 10 seats per workspace

How to read it:

  • Notion is the default for many startups because pages, databases, and wiki structure live together. Its free plan works for one person; teams hit the block limit and move to Plus.
  • Confluence pairs closely with Jira and offers space and page permissions on paid plans; the Free plan for up to 10 users leaves out some permission settings. Paid plans include up to five free guests per paid user. Self-managed Confluence is no longer an option for new buyers: Atlassian stopped selling Data Center to new customers on March 30, 2026, and Data Center reaches end of life on March 28, 2029. If you are moving off Confluence, our Confluence alternatives guide compares self-hosted options by importer, permissions, and paid tier.
  • Slite and Nuclino are lighter, wiki-first tools. Slite's plans center on doc verification and AI search answers; Nuclino keeps a simple structure with list, board, table, and graph views.
  • Outline and BookStack are the common picks when a company wants the wiki on its own servers. BookStack is MIT-licensed and organizes content as shelves, books, chapters, and pages. Outline's code is under the Business Source License 1.1.
  • AFFiNE combines docs, an Edgeless whiteboard, and databases in one workspace, with local-first desktop apps. Its editor is MIT-licensed and the server backend is source-available, so it is an open-core product: the editor is open source and the backend is not. If your wiki must stay on your own infrastructure, our self-hosted Notion alternative guide compares server requirements and licenses in more detail.

Who should not choose AFFiNE as a corporate wiki

AFFiNE is a good fit for teams of up to a few hundred people who want wiki pages, diagrams, and planning boards in one place. It is not the right choice if you need a mature enterprise identity and compliance stack today, deep Jira integration, or a large catalog of marketplace add-ons. In those cases, Confluence is the safer pick. If you only need a plain text wiki on your own server, BookStack is simpler to run.

Choosing corporate wiki software: decision path from hosting requirement to team size and content type, ending in example tools

Company wiki examples

The first three examples below are composite, illustrative setups rather than named customers. The fourth is a public handbook you can read yourself.

  • The 30-person agency. Five spaces, about 80 pages. The most visited pages are "Client onboarding checklist", "How we estimate projects", and "Who to ask". Each account lead owns their client process page.
  • The 150-person software company. Engineering keeps runbooks and architecture decision records in the wiki; everyone else uses Company, Teams, and Onboarding. A monthly report of failed searches drives new pages.
  • The 400-person distributed company. Every team page has the same four sections: what we own, how to request work, current priorities, and rituals. Team leads review them each quarter alongside planning.
  • GitLab's public handbook. GitLab publishes its company handbook at handbook.gitlab.com, which shows how far a written-first culture can go. Most companies need a fraction of that, but the "write it down, then link it" habit is the same.

For more patterns, see these internal knowledge base examples.

Common corporate wiki mistakes

  • Building the structure before the content. Hundreds of empty folders make the wiki look abandoned on day one. Seed with real pages first.
  • No owners. "Everyone owns it" means nobody does. Pages without an owner go stale within months.
  • Copying content from other systems. Duplicated policies drift apart. Link to the source of truth instead.
  • Deep hierarchies. If a page is five clicks deep, people search chat instead. Keep three levels and use hub pages with links.
  • Titles nobody searches for. Use the words people type: "Laptop request", not "IT Hardware Provisioning Procedure".
  • Launching with a tool tour. People adopt a wiki because it answers their question, not because they watched a demo.
  • Measuring page count. A wiki with 2,000 pages and 40% stale content is worse than one with 200 correct pages. Track failed searches, stale pages, and how often chat answers link to the wiki.

FAQ

What is the difference between a corporate wiki and an internal wiki?

There is no practical difference. Corporate wiki, company wiki, and internal wiki all describe an editable, internal set of pages about how a company works. The term usually depends on company size and culture, not on the tool.

What should be included in a company wiki?

Start with company basics, policies, one page per team, step-by-step processes, onboarding, a decision log, and a glossary. Seed it with the 20–30 questions people ask most often in chat, and leave signed documents, passwords, and task status in their own systems.

Who should own a corporate wiki?

Name one wiki lead for the structure and monthly health check, an owner for each top-level space, and one owner per page with a review date. Everyone can still edit; owners make sure their pages stay correct.

How do you keep an internal wiki up to date?

Give every page an owner and a review date, run a monthly health check on stale pages and failed searches, archive instead of deleting, and answer chat questions with wiki links. When a process changes, update the page as part of the change.

Is Notion or Confluence better for a company wiki?

Confluence suits companies already using Jira that need detailed permissions. Notion suits teams that want wiki pages and databases in one flexible tool. Smaller teams may prefer lighter tools like Slite or Nuclino, and teams that need self-hosting can look at Outline, BookStack, or AFFiNE.

Can I host a corporate wiki on my own servers?

Yes. BookStack is MIT-licensed and self-host only. Outline offers a free self-hosted Community edition and paid self-hosted licenses. AFFiNE can be self-hosted with Docker Compose and is free up to 10 seats per workspace. Notion, Slite, and Nuclino are hosted only, and Confluence Data Center is no longer sold to new customers.

Sources and editorial notes

How this guide was prepared: Allen first published this guide on the AFFiNE blog in November 2025, and the AFFiNE team rewrote it in October 2026 to cover company and internal wikis, ownership, rollout, and a current tool comparison. Prices are taken from vendor pages and may differ by billing cycle, region, or team size. The structure template, ownership model, and 30-day plan are AFFiNE's recommendations, not results from a measured study. The examples are composites, except GitLab's public handbook. Nuclino's paid prices did not load on its pricing page when we checked, so they are not listed. AI tools assisted with research and drafting, and the AFFiNE team reviewed and edited the content.