AtlasWork, planned itself.

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

    System status
    • SSO
    • SCIM
    • Two-factor sign-in
    • Audit log

    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

    You are in control of your cookies

    Atlas uses strictly necessary cookies to keep you signed in. With your consent, we add anonymized product analytics, conversion attribution, and remembered preferences. Change your mind any time at /privacy/cookies.

    Off until you agree · Change it any time

    • Necessaryalways on
    • Analyticsopt-in
    • Marketingopt-in
    • Preferencesopt-in
    Skip to documentation
    Docs
    Back to Atlas

    Start here

    • Overview

    Developer

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

    Webhooks

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

    Connect

    • Connectors
    • Integrations

    Product

    • Collaboration and chat
    • Signing in and security
    • Client portal

    Reference

    • Glossary
    • Keyboard shortcuts
    • Module reference
    Module reference

    Module guide

    Apps

    A plain-English map of what every Atlas app owns, and why one is not in this workspace.

    Open module/modules
    businessdocs

    Overview

    The Module Directory is the front door for understanding Atlas. It separates standalone modules from optional connected workflows so users can open CRM, PDF Studio, Contract Hub, Document Sign, Growth Hub, and every core work module without guessing which area owns the work.


    Highlights

    The capabilities worth knowing before you dive in.

    • Business module boundary cards explain standalone ownership and optional integrations
    • All module docs are searchable from one in-app route
    • Each business module links to its product docs and the action registry for API/MCP parity
    • PDF Studio is explicitly labelled standalone and not dependent on Sales CRM
    • An app this workspace does not show says why: a team app in a personal space is marked Team workspaces with a link to create one, and an app the plan lacks offers See plans to an owner or administrator

    Important to know

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

    • Growth Hub is a command center, not an owner for CRM, signing, contracts, or PDF files.
    • Connected workflow links are optional handoffs; they are not required to use the destination module.
    • The directory is navigation and documentation; it does not mutate customer or document data.

    How to use it

    The primary workflow, start to finish.

    1. 1Open the Module reference from the sidebar Help menu, or press Cmd-K and search "modules".
    2. 2Use the Business boundaries section when you are unsure which module owns a workflow.
    3. 3Use Search all modules for every Atlas module doc, including work, planning, capture, and admin pages.
    4. 4Open Product docs for how-to guidance, or Action registry for analytics, API, and MCP semantics.

    FAQ

    Why does Atlas need a module directory?
    The product has grown into many standalone modules. The directory makes ownership explicit so a user can choose the right app before touching data.
    Why is Client Delivery, or People, missing from my sidebar?
    Two things decide which apps a workspace has. A personal space is for you and your household, so it does not include the team apps, People and Client Delivery; the sidebar shows More apps, and this page marks them Team workspaces with a link to create one. A team workspace includes them, and Client Delivery also needs the Business plan. The workspace picker and the switcher at the top of the sidebar say beside each name whether it is personal or team, and which plan it is on.
    What is the difference between a workspace and a personal space?
    Both are workspaces: each has its own projects, people, plan and apps, and you switch between them from the top of the sidebar. A team workspace is for a company, a team or client work. A personal space is for home. Create either from Settings, Workspaces, from the switcher, or from the workspace picker; a new workspace starts as a team workspace unless you choose otherwise.
    Does opening a module from this page create linked records?
    No. It is a navigation surface only. CRM, PDF, signing, and contract records are created inside their owning modules.
    Is the directory itself doing anything to my data?
    No. It is navigation and documentation only. Opening a module from it does not create, link or change any customer or document record.

    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