Wiki Knowledge That Stays Found
Search wikis by title, tags, or anything in the body, and see who changed what, when, in version history. Every write — create, edit, status, delete, owner, share — waits for your confirmation.
Why Wikis Become Write-Only Archives
Wikis Agent attacks the specific failures that turn an active wiki into an unread archive — without forcing teams to re-author what they've already written.
Title-Only Search Misses The Content Inside The Wiki
A wiki titled "Engineering Onboarding Guide" contains the exact answer to a security question in section 4. Search-by-title doesn't surface it. Full-body search is the difference between a wiki that gets read and a wiki that gets re-written.
Version History Is Invisible Without Opening Every Wiki
"When did the on-call escalation matrix last change?" requires opening the wiki, finding the version control panel, scrolling. The agent surfaces version history with author, date, and change type in one prompt — no manual archaeology.
Threaded Discussion Lives Separately From The Wiki Itself
Wiki comments capture institutional context — "we tried this in 2024 and it failed because…" — that never makes it into the body. Without a way to surface threaded comments alongside the wiki, that context disappears with the conversation.
Admins Don't See What's Old, Stale, Or Unread
"Which wikis are nobody reading?" "Which were last updated 18 months ago?" Without get_wiki_stats rolling that up automatically, the wiki garden becomes a wiki jungle within two product cycles.
Nobody Answers For Keeping A Page Accurate
A page outlives the person who wrote it, and when it drifts nobody is on the hook. set_wiki_owner names the person or team who answers for it, and get_wiki_stats lists the pages that may be outdated — not edited or confirmed still accurate within your stale window.
The Right Page Never Reaches The Team That Needs It
The answer exists, but the people who need it are in a chat room or a Teams channel, not in the wiki. share_wiki posts a link card with the page's title and a note to one room, channel, team or colleague — never the page's content, and no title for a page not everyone can read — once you confirm.
Wikis Agent At A Glance
Wikis AI
Full-body search · version + comments · confirmation-gated writes.
Inside Wikis Agent — The Actual Capabilities
Every block below maps to a real tool the agent uses against your Wikis data. Read tools cover search, content, metadata, listing, version history, comments, statistics, and the places a page can be shared to. Write tools — create_wiki, update_wiki, update_wiki_status, delete_wiki, set_wiki_owner, share_wiki — each require explicit confirmation, and each enforce the same permissions as the web app: anyone who can author a wiki in the browser can create or edit one here, the person who manages a page can name its owner, and anyone who can open a page can share it. Status changes and deletion follow the page's Wiki Tools: a company admin, or the person who manages the page.
Full-Body Search With Tag And Status Filters
Employees ask in plain English; the agent searches title, description, and full body content. Tag filters narrow the scope, and a status filter (draft / published / archived) searches the whole tenant for an admin and a member's own pages for everyone else. Once a result is selected, the agent returns the full body and rich metadata in structured form.
search_wikis— natural-language search across title + description + body, with optional tag and status filters (an admin's across the tenant, anyone else's over the pages they manage).get_wiki_content— full body content of a specific wiki by id or title match.get_wiki_details— metadata: author, dates, version count, view count, tags, permissions, status.list_wikis— published wikis sorted by recent / popular / title / oldest / least viewed, optionally tag-filtered.
Version History And Threaded Comments — Audit-Grade
"When did this wiki last change, and who changed it?" gets a structured answer — version numbers, change types, authors, and dates in chronological order. Threaded comments surface institutional context that lives outside the wiki body. Both are read-only and pull from the wiki's actual audit log, not the model's recollection.
get_wiki_versions— version history with version number, change type, author, date, defaulting to 10 versions.get_wiki_comments— threaded comments including replies, defaulting to 20 top-level comments.get_wiki_stats— total count, status breakdown, most and least viewed, newest and oldest updates, and the pages that may be outdated.- Read-only on history — the agent surfaces the audit trail but never rewrites it.
Every Write Confirmed — Create, Edit, Status, Delete, Owner, Share
create_wiki writes a draft (title, optional body, optional tags) — never auto- publishes. update_wiki edits title and body under the same per-page permission rules the browser enforces. update_wiki_status flips between draft / published / archived, and delete_wiki is a soft-delete restored from Trash — both for a company admin or the person who manages the page, as in its Wiki Tools. set_wiki_owner names who answers for a page, and share_wiki sends a link to it. Every write requires explicit confirmation.
create_wiki— creates a DRAFT wiki with title + optional body + optional tags. Drafts never auto-publish.update_wiki— edits title and body, honouring the page's own edit permission (admins and the person who manages it, or any user) and refusing a locked page to everyone but a company admin — the same rules as the web editor. Published edits record a version.update_wiki_status— moves betweendraft,published,archived. For a company admin, or the person who manages the page while it isn't locked, and each transition is confirmation-gated.delete_wiki— soft-delete for a company admin or the person who manages the page; the page and its sub-wikis land in Trash, where the person who manages it or a Wikis admin can restore them, and the confirmation says so — and which of its shared posts will be deleted.set_wiki_owner— names the person and/or team who answers for keeping a page accurate, on pages the asker manages.share_wiki— sends a link card for one page to a chat room, channel, team or colleague; never the page's content.- Permission parity with the web app — publish, archive and delete are offered only to someone who manages a page, and every write re-checks the page's own rules before it runs, so the agent can never do something the same person couldn't do in the browser.
Outcomes Teams Can Measure
The agent's job is to make wiki bodies findable, surface change history without manual navigation, and keep every write behind a confirmation. Measure against your pre-agent baseline.
- Body-search hit rate — share of wiki queries that returned a relevant result via body content vs title-only match.
- Wiki re-author rate — drop in new wikis created on topics that already had wiki coverage; if the agent surfaces existing wikis well, duplicates fall.
- Version-history adoption — share of "when did X change?" questions answered through
get_wiki_versionsvs manual page navigation. - Stale-wiki burndown — wikis last-updated >12 months ago either refreshed or archived per quarter.
- Write override rate — share of confirmation prompts cancelled vs confirmed; high cancellation indicates the agent is being too aggressive on proposals.
Every Write, Always With A Human In The Loop
Every Wikis Agent write — create_wiki, update_wiki, update_wiki_status, delete_wiki, set_wiki_owner, share_wiki — requires explicit confirmation. Authoring mirrors the web app, so anyone who can write a wiki in the browser can do it here, and status changes and deletion follow the page's Wiki Tools — a company admin, or the person who manages the page.
- Confirmation-gated writes —
create_wiki,update_wiki,update_wiki_status,delete_wiki,set_wiki_owner,share_wiki. Status change and delete are for a company admin or the person who manages the page, as in Wiki Tools. - create_wiki produces drafts — never published silently; status transitions are a separate explicit call.
- update_wiki respects the page's own rules — locked pages are refused, and a page only admins and the person who manages it may edit stays that way, exactly as in the browser.
- delete is soft — the page moves to Trash, where the person who manages it or a Wikis admin can restore it, and the confirmation prompt makes that visible.
- Status filter follows the read rules — an admin can scope search to
draftorarchivedacross the tenant; anyone else sees published pages plus their own drafts and archived pages, never someone else's draft.
WHAT TEAMS TRY INSTEAD
The four alternatives — and none of them search your full wiki body, honor your draft/archive states, or gate writes behind confirmation
Wiki knowledge usually decays the day after launch. Search returns titles only, drafts leak into published results, and "is this still current" requires a manual sweep. None of the alternatives keep version history, threaded comments, and admin status visibility in one auditable model.
ChatGPT, Claude, or Copilot ("write a wiki about our deploy process")
Generic AI guessing from no source
- Wikis Agent searches the actual wiki body — not just titles, not the open web
- Version history with author attribution surfaces what changed and when — generic AI has no history
- create_wiki produces a draft that stays out of readers' sight until it is published; generic AI's output is just text
Confluence AI, Notion AI, Guru AI
Vendor wiki AI — separate seat, separate audit, draft/published bleed
- Reads wiki bodies alongside the rest of the platform (HRIS, training, policies) — vendor AI sees only its wiki silo
- Members see published pages and their own drafts, never someone else's draft; vendor tools too often leak unpublished content
- One identity and permission model; vendor wiki AI forces parallel SSO and ACL sync that drifts the day someone changes team
Glean / generic enterprise search bolted on top
A search vendor crawling the wiki — no write back, no governance
- Knows the wiki app's draft/archive/published states natively — Glean indexes whatever it crawled, regardless of status
- Threaded comments and version history are part of the result, not a separate tool to open
- Write actions in the same agent — Glean is read-only and never closes the "create / edit / publish / archive" loop
"We're not allowed to use AI on internal wikis"
The status quo — search returns 200 results, nobody reads them
- Full-body semantic search means the right page surfaces from a question, not a keyword guess
- Soft-delete for admins and the page's manager, behind a confirmation — wikis stay restorable from Trash when "delete this" turns out to be wrong
- Status transitions (draft → published → archived) flow through the agent with an explicit confirmation
PLATFORM ADVANTAGE
Wikis Agent inherits everything the platform already runs
A standalone wiki tool has to plumb each of these. Wikis Agent gets them for free.
Full-body search, not just titles
Search hits the wiki body, description, and tags — not just titles. Knowledge buried in a long page still surfaces.
Status-aware visibility
Members see published wikis plus their own drafts and archived pages, never someone else's draft. Admin search can scope to draft or archived across the tenant — clean separation, no accidental leaks.
Version history with author attribution
Inspect who changed what and when — the version log is a first-class agent tool, not a separate admin console.
Threaded comments visible
The conversation around a wiki page is part of the answer — the agent surfaces threaded comments alongside the canonical text.
Soft-delete with restore from Trash
delete_wiki is soft — the person who manages the page or a Wikis admin restores it from Trash, and the confirmation prompt makes that explicit so deletions aren't a one-way door.
Automatic model tiering
The platform assigns each agent one model tier suited to its work — set for the agent, not picked per question.
INDUSTRY FIT
Industries where wiki knowledge moves the most weight
Wikis Agent shines where institutional knowledge changes weekly and search is the difference between finding and rebuilding.
Technology
Runbooks, ADRs, and on-call playbooks searchable across body content — fewer "rebuild from scratch" incident retrospectives.
Healthcare
Clinical reference and operational wikis surface the current version with attribution — auditors see who reviewed what when.
Financial Services
Internal procedure wikis with strict draft/published states; FINRA examiners see exactly what was authoritative on any given date.
Manufacturing
Engineering and quality knowledge bases searchable by line, station, and material — supervisors find the right page on a kiosk in seconds.
Professional Services
Methodologies, playbooks, and project archives surface across body content — consultants don't reinvent the wheel each engagement.
Public Sector
Policy and procedure wikis keep drafts out of readers' sight until they are published. AI requests go to the platform's configured model providers.
WHY MANGOAPPS WINS
An embedded wikis agent beats a Confluence AI, a Glean bolt-on, or a custom search build on every axis
The argument knowledge owners, IT, and compliance all share — and the one a horizontal AI or a search-only vendor structurally cannot answer.
Cheaper than the alternatives
No Confluence AI / Notion AI / Guru per-seat fee, no Glean enterprise contract, no custom search build — and no knowledge-team hours lost sweeping for stale pages.
More secure
Every write confirmation-gated, with status change and delete for a company admin or the person who manages the page; a member never sees another person's draft; every action audit-logged. AI requests go to the platform's configured model providers, like every MangoApps agent.
Easier to deploy
Already deployed if Wikis is enabled. Turn the agent on and full-body search / version history / threaded comments work the same day.
Easier to use
"Find the deploy runbook" / "who last edited the comp guidance" / "archive the old expense policy" — one prompt each.
Easier to manage
Who can create pages and how long before a page counts as outdated are Wikis settings, laid out like every other app's settings.
Easier to extend
New status transitions, new comment thread types, new version-history signals ship as tools — the agent picks them up the same release.
AI is actually better
A vendor or generic AI can search titles. Wikis Agent also searches the full body, keeps drafts to the people allowed to see them, surfaces version history and threaded comments, and gates writes through confirmation.
At our head office within HR, marketing, and finance, we use ChatGPT quite a bit, and MangoApps AI Helper is a useful tool for us. As I go around to the stores, I’ve been showing them how the AI Intranet Helper can find things and answer plain language questions about our resources, and they’re quite excited about that.
Alison van Zijl
Head of Human Resources
Full House
Customer Success
MangoApps Customers
Organizations that trust MangoApps to run every workflow across their workforce.
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Video Case Studies
Webinars
Frequently Asked Questions About Wikis Agent
14 tools — 8 reads and 6 writes. Reads include search_wikis (title + description + body), get_wiki_content, get_wiki_details, list_wikis, get_wiki_versions, get_wiki_comments, get_wiki_stats, list_wiki_share_places. Writes (all confirmation-gated) are create_wiki, update_wiki, update_wiki_status, delete_wiki, set_wiki_owner, share_wiki.
Every write requires explicit user confirmation. create_wiki creates drafts only, and update_wiki honours the page's own edit permission and refuses locked pages — the same rules as the web editor, so the agent can never do something the person couldn't do in the browser. update_wiki_status and delete_wiki follow the page's Wiki Tools — a company admin, or the person who manages the page — and delete is a soft-delete the person who manages the page or a Wikis admin can restore from Trash. Publish, archive and delete are offered only to someone who manages a page, and every write re-checks the page's rules before it runs.
Yes. search_wikis searches title, description, AND body content. Optional tag and status filters narrow the scope (an admin's status filter covers the whole tenant; anyone else's covers the pages they manage, and a member never sees another person's draft).
get_wiki_versions returns version numbers, change types, authors, and dates from the wiki's audit log. The default limit is 10 versions; the tool is read-only. Pair with get_wiki_comments to surface institutional context that lives in threaded discussion.
Body-search hit rate (vs title-only match), wiki re-author rate (duplicates created on already-covered topics should fall), version-history adoption, stale-wiki burndown per quarter, and admin-write override rate (cancelled vs confirmed). Compare against your pre-agent baseline.
Let's Talk
Every team. Every employee. Every workflow. One AI platform — built for the frontline. Since 2008, trusted by 2 million+ users with an NPS of 78.
Why Choose Us?
- Frontline AI: Governed AI for every employee and workflow.
- Top Security: HITRUST, ISO & SOC 2 certified.
- Exceptional UX: Delightful on mobile and desktop.
- Proven Results: 98% customer retention rate.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Prefer to explore first? Ask AI about Wikis AI Agent →