Issue · 02 · Spring Knovya · Letters
Letter · 07

Team collaboration software that remembers.

— Spring, the year knowledge needed a home

Built for the team whose new engineer asks where the runbook is — and gets three different answers. One letter, in three parts: where the knowledge is now, where it should live, and what the next handoff finally keeps.

The Letter

Dear Team, on team collaboration software that remembers

The new engineer asks where the runbook is. Three teammates point to three different places. The product spec from December is in someone's drafts folder. The retro from last sprint happened, but the action items are in Slack DMs that scrolled away. Where does our knowledge live? — and the honest answer is "in five tools and four heads."

Distributed knowledge is the team tax. Every onboarding, every handoff, every "wait, didn't we decide that already?" is a paid debt. Wikis fall behind because no one updates them. Slack scrolls away because Slack is for talking, not remembering. The team collaboration software you're already paying for handles the chat, but not the memory. You need knowledge management software built into the same surface — not as a side tab, not as a separate tool, but as the place the team already writes.

And the cost isn't only the time spent looking. It's the decisions remade because the original was lost. The pattern re-derived because the spec wasn't searchable. The customer promise re-explained to the AE who joined last quarter. Every team has its version of this — the line in the standup that starts with "do we know where…" and ends with someone shrugging.

Knovya is where team knowledge has to live somewhere. Real-time collaboration with live cursors — write the spec together, not after. Folder sharing by role, with admin and member permissions. Workspace policies — enforce 2FA, audit who saw what, restrict by domain. MCP for teams — every AI agent on the team reads from one canonical brain, not seven scattered ones. A team wiki that doesn't fall behind, because it's where you already write.

The handoff stops being a disaster. The new engineer searches for "runbook" and finds the runbook — with the three retros that updated it, the postmortem that prompted the third one, and the customer issue that started the whole thread. One search, four kinds of context, every connection live.

Stop paying the team tax. Knowledge lives in one place — Knovya — and the whole team can find it.

— Knovya

The Workspace · Try it

Three teammates, one canonical brain.

This is what survives the handoff. Three lenses on the same team — the live doc, the shared shelf, the onboarding trail.

doc · "Q2 Product Strategy" · v3
— 3 editing now · 1 unresolved
Q2 Product Strategy
v3

Goal: ship the new editor by mid-May.

Risk: integration regressions on legacy editorAlex

Rollout: feature flag for first 100 users on MondayMei

Success: 80% of pilot cohort completes a doc within first sessionJin

A M J 3 editing now
1 unresolved on Risk

Three people in the same paragraph. Live cursors, presence, inline comments. No merge conflicts.

Three lenses, one workspace. The doc is what you're writing now. The shelf is what's stored. The trail is what makes the new teammate's first day feel like the team's tenth.

The Stack — six things, one team workspace

From the live doc to the audit log, in one workspace.

Real-time co-editing, shared folders, workspace policies, knowledge graph, MCP for the team's AI, and the templates that keep the wiki from falling behind.

  1. 01

    Real-Time Collaboration

    Live cursors, presence avatars, inline comments, and threaded resolution. Three teammates can write the same paragraph; the editor handles the merge. The same surface that handles solo work handles the four-person doc.

    Real-time collaboration →
  2. 02

    Shared Folders + Permissions

    Folder structure by team, project, or topic. Role-based permissions — admin, editor, viewer — at the folder level. Sensitive folders stay restricted; public folders open to the whole workspace. The filing system the team agrees on.

    Folder sharing →
  3. 03

    Workspace Policies

    Enforce two-factor authentication. Restrict membership by email domain. Audit who saw what and when. SAML SSO for enterprise. The governance layer that turns a workspace into a workspace your security team actually approves.

    Workspace policies →
  4. 04

    MCP for Teams

    One MCP server per workspace. Every AI agent the team uses — Claude, Cursor, ChatGPT, Continue, and the rest — reads from the same canonical knowledge base. New teammate onboarding becomes a search query, not a tour.

    MCP for teams →
  5. 05

    Knowledge Graph

    The runbook links to the postmortem links to the RFC links to the customer issue. Org-wide. Decisions become precedent across squads, and the new teammate's first search returns a door, not a dead end.

    Knowledge graph →
  6. 06

    Team Templates

    RFC, ADR, postmortem, sprint retro, runbook, onboarding doc, OKR review. Templates the team agrees on, with prompts and structure baked in. The wiki stops falling behind because the template makes capture take five minutes, not fifty.

    Team templates →
A Week, in Practice

A team of fourteen, somewhere between standup and ship.

Engineering, product, and design — three squads, one workspace. Here's the week, in seven scenes.

  1. Mon · 09:30

    Standup capture

    Engineering standup runs twelve minutes. The eng lead writes the day's blockers into the team daily — three people watch the cursor land. By 10:00, design has read it and updated the related ticket from the same surface.

  2. Tue · 14:00

    New teammate onboards

    Sam starts. Their first search is "deployment runbook". The runbook surfaces, plus the postmortem behind the canary step, plus the RFC that proposed it. By the second hour, Sam knows enough to ask better questions.

  3. Wed · 11:00

    Spec, written together

    Q2 strategy doc — three editors, live. Alex flags a risk; Mei adds the rollout plan; Jin proposes the success metric. One paragraph, three teammates, one source of truth. The comment thread closes by Friday.

  4. Wed · 16:30

    AI on the team's brain

    Product asks Claude through MCP: "what's the latest on the orders service refactor?" Claude reads the RFC, the in-progress spec, the related postmortem — all from Knovya. The answer takes thirty seconds and includes sources.

  5. Thu · 10:00

    Sprint retro

    The retro template runs the team through what shipped, what slipped, what surprised. Action items get owners. Linked to the sprint folder. Six weeks later, the next sprint's retro inherits the open threads from this one.

  6. Fri · 15:00

    Customer voice, captured

    Customer Success pastes a Zoom transcript into Knovya. AI transforms it into themed quotes linked to the open RFCs they affect. Engineering reads it Monday in the same workspace. The customer voice never leaves the team's memory.

  7. Sun · 21:30

    Weekly snapshot

    The team lead writes one paragraph: what shipped, what's still open, who's blocked. Reflect & Crystals files it with last week's. Three months later, the quarterly retro already has thirteen weekly snapshots to pull from.

None of this is theoretical. It's a week. The team kept growing. The brain came with.

The Blind Spot — what every team tool gets wrong

Team memory is a graph problem, not a page problem.

The team collaboration category solves one piece of the work and leaves the rest to your wiki. Slack handles the chat — and does it well; it's the chat layer most teams default to. But Slack scrolls. The decision in last sprint's retro thread is gone by next sprint's, and the action items are in DMs that never made it to a doc.

Confluence holds the wiki — and at scale, with governance, it's the structured choice for engineering organizations already in Atlassian. The trade-off is adoption: when people stop opening the wiki, the wiki falls behind. Pages go stale. Search returns ten matches and the right one is on page four. The structure is sound; the daily writing happens elsewhere.

Notion is the flexible workspace, the one most modern teams reach for first. It reads your knowledge as documents — pages, databases, blocks — and that model works well for teams whose knowledge maps to records. For teams whose memory is shaped like a graph (a runbook linked to a postmortem linked to an RFC linked to a customer issue), the document model under-fits. AI agents on top read pages, not connections.

Knovya is built for the graph, the share, and the handoff. Real-time co-editing on the same surface as the team wiki. Shared folders with role-based permissions. Workspace policies your security team can audit. Knowledge graph as the primary structure. MCP that exposes the whole graph to every AI agent your team uses. One canonical brain — the team writes there, the AI reads from there, the new teammate searches there.

The wiki stops falling behind when the wiki is where the team already writes.

The Plan — for teams, specifically

Three ways in. Pick the one your team is ready for.

Solo writers run Pro. Distributed teams run Team. Free is enough to point three teammates at one shared workspace and see if the handoff holds.

Free

$0 forever

Run a small team through Knovya. Set up shared folders, write one runbook together, see if it sticks.

  • Up to fifty notes — enough for a small team's runbooks and weekly docs
  • Real-time collab on shared notes
  • Three workspace members
  • One public link, to share a runbook outside the team
  • Templates for runbook, onboarding, weekly review
Open the workspace
For solo

Pro

$15 per month

Built for the individual contributor running their own knowledge base, even when the team isn't on Knovya yet.

  • Unlimited notes — every doc, every decision, every retro
  • Full Knowledge Graph + Hybrid Search + NoteRank
  • MCP across all seven AI clients
  • End-to-end encryption — sensitive notes stay private
  • Unlimited public links
  • API + webhooks for personal workflows
Start with Pro
For distributed teams

Team

$25 per seat / month

For engineering, product, and design squads sharing one workspace. Real-time co-editing, role-based folders, workspace policies, org-level memory.

  • Everything in Pro, for the whole team
  • Real-time co-editing on every doc
  • Shared folders with admin / editor / viewer permissions
  • Workspace policies — enforced 2FA, domain restriction, audit log
  • Workspace-level Knowledge Graph — org-wide memory
  • Team templates and shared workflow conventions
  • SAML SSO and advanced audit (enterprise add-on)
Start with Team

Need an enterprise contract with custom SSO, dedicated support, or a procurement-friendly invoice? Talk to sales →

Other Letters

We wrote six more. One might read like yours.

Try Knovya for the next handoff.

Bring three teammates, set up one shared folder, write one runbook together. Free is enough to see if the wiki stops falling behind.

Start with Team Or browse all 26 features
Questions, answered

What teams usually ask first.

  1. What's the best team collaboration software for knowledge management?

    The best team collaboration software is the one your team actually uses to find things. Most teams pay a tax: knowledge lives in five tools and four heads. Slack handles the chat but scrolls away. Confluence holds the wiki but falls behind. Notion holds the workspace but reads as documents, not as a graph. Knovya is built for the gap — real-time collaboration plus a knowledge graph plus an MCP layer that exposes your shared knowledge to every AI agent on the team. One canonical brain, not seven scattered ones.

  2. Is Knovya a Confluence alternative for teams?

    Knovya solves a different problem than Confluence. Confluence is a structured wiki tied to Atlassian — it's the workhorse for engineering organizations already running Jira. Its strengths are governance and hierarchy. Its weaknesses are speed and adoption: people stop opening the wiki, and the wiki falls behind. Knovya is built for the wiki that doesn't fall behind because it's where the team already writes — daily docs, RFCs, retros, and decisions live in one editor with real-time co-editing. Plus a knowledge graph that connects them, and an MCP for AI.

  3. How is Knovya different from Notion for teams?

    Notion is a flexible all-in-one workspace with strong AI agents on the Business plan. It reads your knowledge as documents — a powerful approach for marketing, ops, and project management. For knowledge-heavy teams whose memory is interconnected (decisions linked to retros linked to specs linked to customer voice), the graph matters more than the page. Knovya is graph-native: shared folders, workspace policies, real-time collab, and an MCP that exposes the whole graph to whatever AI you connect.

  4. Does Knovya support real-time collaboration?

    Yes. Live cursors, presence avatars, inline comments, and collaborative blocks. Three teammates can write the same paragraph; the editor handles the merge. Comments thread on selections and resolve in place. Presence shows who's reading and who's editing right now. The same surface that handles solo work handles the four-person doc.

  5. What workspace policies does Knovya support?

    Workspace-level policies include enforced two-factor authentication, domain-restricted membership, role-based folder permissions (admin, editor, viewer), and audit logs covering who saw what and when. SAML SSO is available as an enterprise add-on. Public links are workspace-level toggleable, and sensitive folders can be restricted from public sharing entirely.

  6. How does MCP work for teams?

    Knovya runs one MCP server per workspace. Every AI agent the team uses — Claude, Cursor, ChatGPT, Continue, Goose, VS Code, Copilot — reads from the same canonical knowledge base. New teammate onboarding becomes a search query, not a tour. The AI tools your team is already running can answer questions about your runbook, your RFC, your last quarter's retro — without anyone re-pasting context into each chat.

  7. Can Knovya replace our team wiki?

    Yes. Knovya works as a team wiki out of the box: shared folders by team or topic, role-based permissions, page templates for runbooks and onboarding docs, and full-text plus semantic search across the whole workspace. The difference from a traditional wiki is that the wiki is also where the team writes daily — so it doesn't fall behind. RFCs, retros, decisions, and runbooks live in the same surface, linked through the knowledge graph.