AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus
Skip to documentation
Docs
Back to Atlas

Start here

  • Overview

Developer

  • REST API guide
  • Authentication
  • API reference
  • MCP (AI agents)
  • SDKs
  • Quick actions

Webhooks

  • Overview
  • Quickstart
  • Events
  • Payloads and headers
  • Security and signing
  • Delivery and retries
  • Managing via API

Connect

  • Connectors
  • Integrations

Product

  • Collaboration and chat

Reference

  • Glossary
  • Keyboard shortcuts
  • Module reference
Module reference

Module guide

Wiki

Tenant-scoped knowledge base with revisions and restore.

Open module/wiki
knowledgedocs

Overview

A hierarchical knowledge base with auto-generated slugs and Markdown bodies. Every save captures a revision, and a one-click restore puts any earlier version back in place while preserving the newer state as history.


Highlights

The capabilities worth knowing before you dive in.

  • Slug is auto-derived from the title, with conflict-avoidance suffixes
  • Every update snapshots the prior body into a WikiRevision
  • POST /wiki/pages/:id/revisions/:revisionId/restore rolls back without losing forward history
  • Tree-structured pages with parent-reparent cycle prevention

Important to know

Limits, permissions, and sharp edges to keep in mind.

  • Soft-delete keeps a page in the audit trail but hides it from the UI.
  • Reparenting a page under one of its own descendants returns 400 with an explanation.
  • The revision timeline names who made each change rather than showing their stored identifier. Where that identifier no longer resolves to a workspace member it is shown as it stands, because a page revised by somebody who has since left is still a revision somebody made.

How to use it

The primary workflow, start to finish.

  1. 1Click "New page" at /wiki to create a root entry.
  2. 2Use the tree nav on the left to drill into subpages.
  3. 3Click Revisions on any page to see the timeline, then hit Restore to roll back.

FAQ

Where does my content render as HTML?
The body is stored and displayed as plain Markdown today. A sanitized HTML renderer is on the roadmap; inline Markdown preview ships first.
Can I share a wiki page externally?
Yes. Use Settings > Public share links to generate a tokenized read-only (or comment-scope) URL with an optional password and expiry.
Why was I refused with a 400 when I tried to move a page?
You attempted to reparent the page underneath one of its own descendants, which would detach that branch from the tree. Choose a destination that is not below the page you are moving.

Automate this module

Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
All modules
Was this page helpful?

On this page

  • Overview
  • Highlights
  • Important to know
  • How to use it
  • FAQ