Growth Hub

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

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

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

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/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.

How to use it

Open /growth-suite when you want to understand cross-module posture.
Choose Catalog and search the Growth Hub Action Catalog when you are unsure which control or module owns the next job.
Choose Workspaces to open Sales CRM, Contract Hub, Document Sign, or PDF Studio directly.
Choose Lists when you know the object family you want to inspect.
Choose 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.

All docs