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
    Still loading. Try again in a moment.Still loading. Try again in a moment.Still loading. Try again in a moment.
    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
    • Client portal domains

    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, contracts and signing. It does not replace Sales CRM, Contract Hub or Document Sign. Use it to read pipeline, forecast, customer health, contract and signature figures in one place, and to open the module that owns the work.


    Highlights

    The capabilities worth knowing before you dive in.

    • Overview tab with the headline figures for the pipeline, contracts and signing
    • Module cards for CRM, Contracts and Agreements, each with a few live figures and a button that opens the module
    • Forecast tab with the commit, best case, open pipeline and closed-won figures and a chart of the pipeline by expected close date
    • Health tab with the health spread of accounts, the items that need attention, recent activity and next best actions
    • Pipeline tab with the pipeline by stage and the gaps that put deals at risk, such as stale deals and deals with no owner or no next step
    • Header buttons that open the CRM reports, Insights, the Today queue and Quick capture
    • Governance and controls section on the Overview tab, showing your role, which privileged controls you hold or lack and why, and the CRM action policy
    • Action catalogue on the Overview tab, with search and category filters, that opens the page or section where each hub job is done
    • Object search on the Overview tab that finds accounts, deals, agreements, PDF documents and visibility groups by name, with a record type filter, an include archived switch and a link to each record
    • Evidence export on the Overview tab that downloads the Growth Hub evidence records as a JSON Lines file

    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.
    • The hub reads from Sales CRM, Contract Hub and Document Sign, and each of them works on its own at its own address. None of them depends on the hub.
    • Each figure loads on its own. When a read fails, its tile says Unavailable rather than No data, and the retry button reloads the hub.
    • The account and contact lists show an owner by name rather than by stored identifier. An owner the member directory no longer knows reads as Unassigned in those lists, while an account detail page shows the stored identifier.

    How to use it

    The primary workflow, start to finish.

    1. 1Open /growth-suite when you want the cross-module picture.
    2. 2Read the Overview tab for the headline figures, then use a module card's Open button to go to the module that owns the job.
    3. 3Choose Forecast to read the commit, best case, open pipeline and closed-won figures.
    4. 4Choose Health to see which accounts are at risk, which signatures are pending and the next best actions.
    5. 5Choose Pipeline to find stale deals and deals with no owner or no next step.
    6. 6Use "What do you want to do in Growth Hub?" to search for a job and go straight to the page that does it.
    7. 7Open Governance and controls to see which privileged actions your role can take and why any are withheld.
    8. 8Use Find a Growth Hub record to type at least two characters, narrow by record type if needed, and open the record from the result.
    9. 9Press Download evidence export to save the evidence records as a JSON Lines file. The export needs permission to export, and a failure message appears when your role lacks it.

    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 and signing figures in one place?
    A deal often becomes a contract and then a signed agreement, so the hub shows those figures side by side. It does not make any module depend on another.
    Does anything stop working if we never connect Salesforce or HubSpot?
    No. Records created in Atlas work without any external connector. A connector only adds a path for syncing or enriching records.

    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?
    About this page

    On this page

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