Who it is for
- Growth teams, agencies, and operators that need workspace analytics, approval queues, agent-assisted workflows, integrations, feeds, and an auditable activity timeline under explicit access controls.
Betaatlasloopos
Coordinate paid-media intelligence, approvals, analytics, and GTM execution from the AtlasLoopOS Command Center.
Operate paid-media intelligence, approval workflows, configured integrations, and AI-assisted GTM workflow coordination. Optional automotive and inventory context is handled separately as AtlasCommerce after enablement.
Runtime availability depends on the canonical product status, organization entitlement, workspace permissions, deployment configuration, and any provider-specific authorization required by the workflow.
Codebase contract
- Application route: /dashboard
- Required permissions: atlasloopos.access
How the current workflow works
- 1Sign in, select an entitled organization and workspace, and open Command Center.
- 2Review the month-to-date spend, leads, calls, and CPL summary available for the selected workspace.
- 3Inspect the unified activity timeline to understand recent governed work and recorded lifecycle events.
- 4Review pending GTM play approvals and explicitly approve, reject, or revise material moves through the approval workflow.
- 5Open Agents only for permitted, configured workflows and keep material execution behind the applicable approval and guardrail checks.
- 6Use Feeds, Ask AtlasLoopOS, Analytics, and Integrations for the data and provider context enabled in the deployed environment.
- 7Return to Command Center to verify the recorded activity, approvals, and available outcome metrics after controlled actions complete.
Current codebase capabilities
- Command Center with month-to-date spend, leads, calls, and CPL metrics.
- Unified workspace activity timeline and approval inbox preview.
- Agent, approval, feed, chat, analytics, integration, and settings navigation surfaces.
- Product access and permissions enforced through the shared platform entitlement model.
- AI-assisted workflow coordination with human review for material decisions.
Current boundaries
- Available analytics and provider behavior depend on the deployed environment and configured integrations.
- Interface visibility does not prove that a provider connector or customer credential is configured.
- Optional commerce and inventory behavior remains separated behind AtlasCommerce boundaries and entitlements.
- The platform does not claim unsupervised campaign execution for material moves.
Manifest capabilities and permissions
These identifiers are read directly from the canonical frontend product manifest. They describe access boundaries and capability names; they do not by themselves prove provider configuration or runtime availability.
Capabilities
atlasloopos.accessatlasloopos.analytics.viewatlasloopos.agents.runatlasloopos.approvals.reviewatlasloopos.integrations.manageatlasloopos.inventory.viewatlasloopos.api.validate_licenseRequired permissions
atlasloopos.accessWhat to verify after using it
- Command Center metrics load for the selected workspace rather than another tenant.
- Approval decisions and material workflow events appear in the activity trail.
- Provider-backed actions are attempted only after the required entitlement, permission, configuration, and approval checks pass.