Build a Company Wiki with Guru: Step-by-Step Setup Guide

If your team is constantly asking the same questions, hunting for documents in Slack, or losing critical knowledge when someone leaves, you are not alone. Most growing companies hit the same wall: information is everywhere, but knowledge is nowhere.

That is where Guru comes in.

Guru is one of the most powerful knowledge base platforms available today. It lets you build a centralized company wiki where every policy, process, playbook, and piece of institutional knowledge lives in one place — searchable, verified, and always up to date. Whether you are a 10-person startup or a 500-person enterprise, a well-built Guru wiki can save your team hours every week.

In this step-by-step guide, you will learn exactly how to set up your company wiki with Guru from scratch — including how to structure it, create Cards, organize Collections, and maintain knowledge over time.

Why Guru Is the Right Tool for Your Company Wiki

Before diving into the setup, it is worth understanding what makes Guru different from a traditional wiki tool like Confluence or Notion.

Guru is built around verified knowledge. Every piece of information — called a Card — has an owner and an expiration date. If content is not reviewed by its expert, it gets flagged as unverified. This simple mechanic solves the biggest problem with most company wikis: outdated, unreliable information that nobody trusts.

Other key advantages include:

Browser extension that surfaces Guru knowledge inside Gmail, Salesforce, Zendesk, and any other tab your team uses
AI-powered search that understands natural language questions
Slack and Teams integration so employees can find answers without leaving their workflow
Permissions and Collections to keep department-specific knowledge private

Now let’s build it.

Step 1: Set Up Your Guru Account and Invite Your Team

The first step is creating your Guru workspace. Go to getguru.com and sign up with your company email. You can start with a free trial that includes full access to core features.

Once inside, navigate to Settings > Members and invite your core team. For the initial setup phase, you do not need to invite everyone at once. Start with:

Knowledge managers — people who will own the structure and quality of the wiki
Subject matter experts (SMEs) — department leads who will write and verify content in their area
IT or operations — if you need SSO or advanced integrations configured

Pro tip: Assign roles carefully. Guru has three main roles — Author (can create and edit), Collection Owner (manages a Collection), and Admin (full access). Start lean. You can always expand permissions later.

Step 2: Plan Your Wiki Structure Before Writing a Single Word

This is the most important step that most teams skip — and it is the reason so many company wikis fail within six months.

Before you create a single Card, map out your knowledge architecture on paper or a whiteboard. Ask yourself:

What are the main departments or functions in your company?
What knowledge does each department need to access regularly?
Which information is internal only, and which is cross-functional?
What questions does your team ask most often?

In Guru, your wiki is organized using three layers:

Collections — the top-level folders, typically organized by department or topic (e.g., Sales, HR, Product, Engineering)
Boards — sub-folders within a Collection that group related Cards (e.g., inside HR: Onboarding, Benefits, Policies)
Cards — individual articles that contain specific knowledge

A clean structure for a mid-sized company might look like this:

📁 HR & People
   📋 Onboarding
   📋 Benefits & Perks
   📋 Performance Reviews
   📋 Policies

📁 Sales
   📋 Pitch Decks & Messaging
   📋 Objection Handling
   📋 CRM Processes
   📋 Competitive Intelligence

📁 Product
   📋 Roadmap & Vision
   📋 Feature Documentation
   📋 User Research

📁 Engineering
   📋 Dev Environment Setup
   📋 Deployment Processes
   📋 Architecture Decisions

📁 Company-Wide
   📋 Mission & Values
   📋 Org Chart
   📋 Brand Guidelines
   📋 Meeting Rhythms

Do not over-engineer this. You can always add Boards and Collections later. Start with the structure that reflects how your team actually works today.

Step 3: Create Your Collections in Guru

Now it is time to bring your structure to life inside Guru.

In the left sidebar, click “+ New Collection”. Give it a clear, simple name. Avoid vague names like “Resources” or “Misc” — every Collection should have an obvious purpose.

For each Collection:

Set visibility — decide if it is public to the whole workspace or restricted to specific team members
Assign a Collection Owner — this person is responsible for the overall health of knowledge in this area
Write a short description — a one or two sentence summary of what lives here helps new employees navigate quickly

Repeat this for each major department or topic you mapped in Step 2.

Step 4: Build Your Boards

Inside each Collection, create Boards to group related Cards. Think of Boards like chapters in a book.

Click into a Collection, then select “+ Add Board”. Name it clearly and add a brief description.

A few naming best practices:

Use nouns, not verbs: “Sales Processes” not “How We Sell”
Be specific: “Customer Onboarding Checklist” not “Onboarding”
Keep names short: aim for three words or fewer

Once your Boards are created, you have the skeleton of your wiki. Now it is time to fill it with content.

Step 5: Write Your First Cards

A Card is the atomic unit of knowledge in Guru. Each Card should answer one specific question or explain one specific process. Think of it as a standalone article.

To create a Card, click “+ New Card” from inside a Board. The Card editor supports rich text formatting, images, videos, tables, code blocks, and more.

What makes a great Guru Card?

Clear title — written as a noun phrase or question (e.g., “How to Submit a Vacation Request” or “Vacation Request Process”)
Short summary — one to two sentences at the top explaining what this Card covers
Structured body — use headers, bullet points, and numbered steps for scannable content
Verification owner — assign the Card to the person who owns this knowledge
Verification interval — set how often this Card should be reviewed (30, 90, or 180 days is typical)

Start by creating Cards for your most frequently asked questions. Talk to your support team, ops team, and HR — they know what questions come up over and over again. Those are your first twenty Cards.

Do not aim for perfection on day one. A rough Card that exists is infinitely more valuable than a perfect Card that is still being drafted.

Step 6: Import Existing Content

You do not have to start from scratch. Guru supports direct imports from:

Google Drive — import Docs as Cards
Confluence — migrate your existing wiki
Notion — export and import your pages
CSV — bulk create Cards from a spreadsheet

Go to Settings > Import to access import tools. For large migrations, Guru’s support team can help with the process.

After importing, go through each Card and:

Assign a verification owner
Clean up formatting
Update any outdated information
Place each Card in the right Board and Collection

Step 7: Connect Guru to Your Team’s Workflow

A wiki only works if people actually use it. The biggest mistake companies make is building a wiki and then telling people to “go check Guru.” That does not work. Knowledge needs to come to the people, not the other way around.

Here is how to embed Guru into your existing workflow:

Install the Browser Extension

The Guru Chrome extension is arguably its most powerful feature. Once installed, it surfaces relevant Cards automatically based on the page you are viewing. If a support rep is looking at a ticket in Zendesk, Guru proactively suggests related articles. This is called knowledge push and it eliminates the need to search in the first place.

Have everyone on the team install it on day one.

Connect to Slack or Microsoft Teams

In Settings > Integrations, connect Guru to Slack or Teams. This allows team members to search Guru directly from a Slack message using the /guru slash command. They can also share Cards as links in channels.

For new hires especially, this is a game changer — they can ask questions in Slack and get a verified Guru Card back instead of waiting for someone to reply.

Link Cards in Your Other Tools

Paste Guru Card links anywhere your team works — in Notion project pages, in Jira tickets, in Asana tasks, in Confluence pages. Guru links preview inline in most modern tools. The more you embed Guru into existing workflows, the more naturally it gets used.

Step 8: Set Up a Verification Cadence

This is what separates a thriving wiki from an abandoned one.

Guru’s verification system works like this: every Card has an owner and a verification interval. When the interval expires, the owner gets an email prompt to review and re-verify the Card. If they do not, the Card is marked as unverified and flagged for readers.

To manage this effectively:

Assign every Card to a real person — never leave the owner as “Unassigned”
Set realistic verification intervals — HR policies might need quarterly review, while a product overview might only need review twice a year
Schedule a monthly Guru review — the Collection Owner should check their dashboard for unverified Cards and follow up with owners
Celebrate wiki maintenance — recognize team members who keep their Cards up to date

In My Guru > Verify, each owner can see their queue of Cards due for review. Make this part of your team’s regular rhythm.

Step 9: Measure Usage and Improve

Guru provides analytics that show you which Cards are being viewed, searched, and shared. Use these insights to improve your wiki over time.

Key metrics to track:

Most viewed Cards — is the right content being surfaced?
Search queries with no results — what are people looking for that does not exist yet? These are content gaps.
Verification rate — what percentage of your Cards are currently verified?
Adoption rate — how many team members are actively using Guru each week?

Review these monthly. Use search queries with no results as a content roadmap — every failed search is a Card waiting to be written.

Common Mistakes to Avoid

Even with the best intentions, many company wikis fail. Here are the most common pitfalls:

Trying to document everything at once. Start with twenty high-value Cards, not two hundred mediocre ones. Quality over quantity, always.

No ownership model. If everyone owns the wiki, no one does. Every Collection needs an owner, and every Card needs a named expert.

Making it a one-person project. A wiki that only one person maintains will reflect only one person’s knowledge. Build a culture where contributing to Guru is part of everyone’s job.

Ignoring adoption. Launch with a team training session. Show people how to search, how to use the browser extension, and how to create Cards. Repeat this for every new hire during onboarding.

Final Thoughts

Building a company wiki with Guru is one of the highest-leverage investments you can make in your team’s efficiency and scalability. When done right, it reduces repetitive questions, accelerates onboarding, preserves institutional knowledge, and frees up your best people to do their best work instead of answering the same Slack messages over and over.

The key is to start simple, assign clear ownership, embed Guru into your existing tools, and treat knowledge maintenance as an ongoing practice rather than a one-time project.

Your wiki will never be finished — and that is exactly the point. It grows with your team, reflects your current reality, and becomes more valuable every day someone adds to it.

Start today. Create your first ten Cards. Assign owners. Install the extension. The rest will follow.

Looking for more tech guides, software tutorials, and productivity tips? Visit VyvyMangaTech for expert resources to help your team work smarter.