Module Directory

A plain-English map of what every Atlas module owns.

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

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

Important to know

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

Open /modules from the Business sidebar group.
Use the Business boundaries section when you are unsure which module owns a workflow.
Use Search all modules for every Atlas module doc, including work, planning, capture, and admin pages.
Open Product docs for how-to guidance or Action registry for analytics/API/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 workspace before touching data.

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.

Atlas docs · Atlas - the AI-native work platform