# Enterprise Wiki Software & Internal Knowledge Base | MangoApps Internal knowledge base with rich-text editing, hierarchy, version history, diffs, rollback, mentions, and AI search — an enterprise wiki teams actually use. # One Source Of Truth For Your Team > Write it once, find it forever — rich pages with sub-wikis, @mention comments, side-by-side version diffs, and rollback, plus edit locking so two people never trample each other's changes. ## What Wikis Help You Do ### Author Collaboratively Quill rich-text editor with cover images, tags, templates, drafts, publishing, archive status, duplication, ownership transfer, and sub-wiki creation. ### Track Versions Every change tracked. View history, compare versions, restore earlier states, and see who changed what — built-in, not bolted on. ### Control Access Per-wiki edit and comment permissions let admins decide whether any user, creators, or admins can update and discuss a page. ### Search Semantically Full-text search covers title, description, and body. Semantic search can surface wiki content by meaning when embeddings are available. ### Prevent Edit Conflicts Edit locking prevents simultaneous edits, with configurable lock duration and an admin break-lock control for stuck drafts. ### Reach Mobile Employees can browse, search, pin, comment on, and export important pages from the same platform they use for work. ## Wikis In Practice A practical scope check: what the app covers, which controls matter, and the workflows teams usually run first. ### Core workflow Create and edit rich wiki pages with a WYSIWYG editor powered by Quill, including image uploads. ### Controls that matter Collaboration & Permissions includes Threaded comments with reply support and @mention notifications in comments. ### Scope and specs Useful specs: Wiki title max length: 255 characters; Comment max length: 2,000 characters; Default edit lock duration: 30 minutes (admin-configurable). ### Team runbook A team maintains a wiki of operational procedures and troubleshooting guides, using sub-wikis for each system and version history to track updates. ### Process documentation HR documents company processes in wikis with rich formatting, then pins the most-referenced pages for easy access across the organization. ### Onboarding knowledge base New hires browse a structured wiki hierarchy covering company culture, tools, and role-specific procedures, leaving comments when they have questions. ## Connected To The Rest Of MangoApps ### → Libraries Wikis link from Libraries for one-step navigation. Department resource hubs and operational reference live alongside each other. ### → Workspaces Each Workspace can contain its own wiki for project specs, retros, and decisions. Knowledge stays scoped to the project. ### → Training Course materials and reference content live in wikis linked to LMS modules. One source of truth for both learning and reference. ### → AI Search AI surfaces relevant wiki content across the whole platform — alongside posts, files, and Library resources. ### → Content Governance The Governance Engine assigns owners, sets renewal schedules, and flags stale wikis for review. ### → Service Desk Service Desk articles and wikis cross-reference each other. Resolution guides and SOPs share one canonical source. ## Wikis inherits everything else MangoApps already does A standalone wiki tool has to build, buy, or integrate each of these. Wikis gets them for free because the platform already runs them. ### HRIS-aware audiences Wiki access scopes by role, location, or department from the live HRIS — no parallel space-permission groups. ### Identity & SSO Inherits SAML/OIDC SSO and SCIM. New hires see the right wikis on day one based on their HR record. ### Versioning & governance Every edit captured with author, timestamp, and rollback — governed by the same workflow engine that runs policy approvals. ### Answers in your language Ask AI replies in the language each person asks in, so readers can ask about a page in their own language. ### AI search & semantic Answers are grounded in the wiki AND the rest of the platform (chat, drive, training, tasks) under one permission model. ### Mobile app & push Frontline staff read wiki articles in the same app they use for shifts — no second login, no corporate email required. ## Built for organizations whose knowledge has to reach the frontline Wikis fits operators whose SOPs, playbooks, and reference content need to land for a deskless workforce, not just HQ. ### Healthcare Clinical SOPs, policy articles, and accreditation playbooks with versioning and a record of status and ownership changes. ### Manufacturing Standard operating procedures, safety playbooks, and quality protocols in the worker's preferred language on personal devices. ### Retail Brand playbooks, merchandising SOPs, and store-operations articles surface to associates in the app they already use for shifts. ### Field Service Service manuals, asset-specific procedures, and troubleshooting playbooks one tap from the technician's work order. ### Public Sector Department playbooks and procedural references with versioning and a record of status and ownership changes. ## One platform beats a stack of point solutions on every axis The case Ops, KM, IT, and Compliance all share — and the one a standalone wiki tool structurally cannot answer. ### Cheaper than the stack One per-employee suite license replaces Confluence, Notion, Guru, and the SharePoint wiki add-on — and AI search comes built in. ### More secure One identity perimeter and one set of roles and permissions across every page and version. Nothing extra for security to certify. ### Easier to deploy Already deployed if you have MangoApps. Create the first wiki, scope by HR audience, publish the same day. ### Easier to use Frontline staff read articles in the app they already opened for shifts and pay — one login, native search and preview on mobile. ### Easier to manage Approvals and audience scoping reuse the same RBAC every other module uses — no parallel KM admin tree. ### Easier to extend A wiki article can be embedded in a site, attached to a task, or surfaced in Service Desk — same content, no copy-paste. ### AI is actually better Wikis AI returns answers grounded in the article PLUS surrounding context (chat history, drive files, training) — under the same permission model as every other agent. ## How Teams Build Their Knowledge Base ## Customer Testimonials > "I think our work product would not be as strong if we didn’t have a centralized place to save our 70 years of experience and the thousands of documents that my colleagues create every day. Being able to access that in a moment’s notice is absolutely amazing." — Annie Bidwell, Senior Director, CCS Fundraising > "For many of our standards development committee members, MangoApps was a breath of fresh air and it was a place for them to really start to gel as a big community. Prior to MangoApps, we would have to email back and forth and make sure everyone was on the same page and they could reach out to each other. Now, they can just chat if it’s available, or send a message and get that communication going." — Teresa Rowe, Sr. Director, Assembly & Standards Technology, IPC > "With all of the resources we built within MangoApps, getting employee engagement was very easy. We currently have over 90% monthly employee engagement.‍" — Rebecca Wolfs, Director of Training, Development, and Compliance, Columbia Basin Health Association ## Frequently Asked Questions ### Q: Do Wikis support rich content? A: Yes. The Quill rich-text editor supports structured page authoring with images, tags, templates, drafts, publishing, and sub-wikis. Edit locking prevents simultaneous edits from overwriting each other. ### Q: How does version control work? A: Every change is tracked automatically. View edit history per page, compare versions side-by-side, restore earlier states, and see exactly who changed what. No external tool required. ### Q: How granular are the permissions? A: Edit and comment permissions are set per wiki. Teams can keep editing open, restrict it to the creator, or limit it to admins, depending on the sensitivity of the content. ### Q: How does AI Search work across Wikis? A: AI-powered semantic search across every wiki in your platform — finds content by meaning, not just keywords. Results respect read permissions; users only see what they're authorized to. ### Q: How do we keep wikis from going stale? A: Assign content owners and renewal cycles. The Content Governance Engine flags stale wikis for review automatically and notifies owners. Wikis that aren't current get surfaced for refresh before they decay into misinformation. --- Every team. Every employee. Every workflow. One AI platform — built for the frontline. 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.