Wiki · Included with Pro
A team wiki inside your trackerDocs where the work happens.
Rich pages in nested folders, next to the boards they describe — with discussions pinned to the exact sentence, full version history, and a table of contents that writes itself.
How the wiki works
Build the tree
Folders and pages nested to any depth, per project — drag to reorder or re-parent in the sidebar, rename inline, and star the pages you live in.
Write rich pages
Headings, formatting, embedded files and images — with an auto-generated "On this page" outline that follows your scroll and deep-links to any heading.
Discuss the exact sentence
Select any passage and start a discussion pinned to that quote — threaded replies, rich text, @mentions that notify, resolve and reopen. The comment lives on the words it's about.
A knowledge base with receipts
Discussions anchored to the text
Google-Docs-style: the thread is pinned to a quoted passage. Edit the passage away and the discussion is flagged orphaned — bring the text back and it reactivates.
Version history with safe revert
Every save is a numbered version with author and time. Preview any of them read-only, and revert non-destructively — the rollback is itself a new version.
A table of contents you don't write
The outline builds itself from your headings, scroll-spies as you read, and gives every heading a shareable anchor link.
Favourites and a 30-day trash
Star pages into a per-user favourites flyout; deleted pages and folders sit in trash for 30 days and restore to exactly where they were.
Structure that stays in sync
Tree changes, discussion activity, and favourites broadcast live to everyone in the project — the sidebar you see is the sidebar they see.
@mentions that reach people
Mention a teammate in a page discussion and they're notified; replies notify the thread — questions on docs stop dying in silence.
Why keep the wiki inside the PM tool?
The problem with a separate wiki tool isn't the writing — it's the distance. Docs drift when they live two tabs away from the work they describe: the spec never links the cards, the runbook never gets the question that arose mid-incident, and nobody is sure which version was current when the decision was made.
AgileHero puts the knowledge base inside every project, next to the boards. Pages link tightly to the work, discussions attach to the exact sentence under debate, and the full version history — with preview and safe revert — settles "which version said that" in one click. One tool fewer to pay for, and a wiki that's actually where your team already is.
Common questions
Is the wiki free?
The wiki is part of Pro — and fully included in every 14-day trial. If a workspace moves to the free plan, the wiki is paused but every page is kept and returns on upgrade.
Can I see who changed what?
Yes — every save creates a numbered version with its author and timestamp. Browse the history, preview any version read-only, and revert without destroying anything: the revert becomes a new version.
What happens to deleted pages?
They move to a trash area with their whole subtree, restorable to the original location for 30 days before being purged automatically.
Do discussions survive edits?
A discussion is pinned to its quoted passage. If the passage is edited away, the thread is flagged as orphaned rather than deleted — and it reactivates if the text returns.
Can I organize docs by topic?
Yes — folders nest to any depth per project, and the sidebar tree drags to reorder or re-parent. Favourites keep your daily pages one click away.
Start with two seats, free forever
Every plan begins as a 14-day trial of every premium module. Set up your first project in minutes.
Try it for free14-day free trial · no credit card required