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

Growth Hub

A command center that connects standalone business modules without owning them.

Open module/growth-suite
businessgovernance

Overview

Growth Hub is the cross-module cockpit for revenue, legal, signing, and PDF posture. It does not replace Sales CRM, Contract Hub, Document Sign, or PDF Studio. Use it to see integrated status, open the right module, review governance, and move across related records when a workflow genuinely spans modules.


Highlights

The capabilities worth knowing before you dive in.

  • Searchable Growth Hub Action Catalog for orientation, module launch, list jumps, governance, analytics, and optional handoffs
  • Standalone-module launcher for Sales CRM, Contract Hub, Document Sign, and PDF Studio
  • Overview metrics for optional links, governed actions, and no-key provider posture
  • Lists tab for direct jumps into CRM records, contract queues, signing envelopes, and PDF documents
  • Governance tab for delegated access, RBAC, audit evidence, and export posture
  • Hash-based section links that switch tabs without forced scroll jumps

Important to know

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

  • Growth Hub is not a required starting point. Open the standalone module directly when you already know the job.
  • Provider adapters and external CRM, signature, and PDF systems are optional. Atlas-owned records continue to work without provider keys.
  • Analytics ids are attached to the launcher, tabs, and handoff links so product adoption can be audited without exposing customer payloads.
  • Everywhere the account, deal and contact views name an owner, a reviewer or a contact owner, they show that person by name rather than by their stored identifier. Where the identifier resolves to nobody it is shown as it stands, because a record owned by somebody who has left is not an unowned record, and Unassigned still means unassigned.

How to use it

The primary workflow, start to finish.

  1. 1Open /growth-suite when you want to understand cross-module posture.
  2. 2Choose Catalog and search the Growth Hub Action Catalog when you are unsure which control or module owns the next job.
  3. 3Choose Workspaces to open Sales CRM, Contract Hub, Document Sign, or PDF Studio directly.
  4. 4Choose Lists when you know the object family you want to inspect.
  5. 5Choose Governance to review access, delegation, and evidence posture before high-risk work.

FAQ

Do I need Growth Hub to use PDF Studio or CRM?
No. Each module has a top-level route and can be used independently. Growth Hub is only an integrated command center.
Why do I see CRM, contracts, signing, and PDF in one place?
Some enterprise workflows cross those boundaries, such as turning a deal into a contract and then sending a signed PDF. The hub shows those links without making any module depend on another.
Does anything stop working if we never configure provider keys?
No. Records that Atlas owns continue to work without them. Provider adapters and external systems are optional, and configuring credentials activates delivery through them rather than turning the module on.

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