Introduction

Atlas is an autonomous workflow agent for manufacturers. It connects to email inboxes and ERP systems, monitors business state, and keeps work moving through auditable cases.

The docs focus on setup and operation: how to connect systems, what Atlas can read or write, how approvals work, and how to diagnose common connection issues.

1. 1

   Read the core concepts

   Understand cases, workflows, approvals, and how integrations feed Atlas.

2. 2

   Connect an inbox

   Start in Atlas Settings -> Email with Gmail so Atlas can observe customer and supplier communication. Microsoft 365 mailbox setup follows the same consent model when enabled for a workspace.

3. 3

   Connect an ERP

   Use Atlas -> Connectors to add Odoo, SAP, Dynamics, or Business Central so Atlas can ground decisions in operational records.

Atlas needs two kinds of context: communication context from an inbox, and operating context from the ERP. Email tells Atlas what changed. ERP data tells Atlas whether the change matters and what action is allowed.

• Email context: customer requests, supplier updates, quote threads, order exceptions, attachments, and operator replies.
• ERP context: customers, vendors, products, quotes, sales orders, purchase orders, inventory, manufacturing orders, invoices, and delivery state.
• Policy context: which reads are allowed, which writes require approval, and which actions must escalate to a human.

1. 1

   Connect a low-risk inbox first

   Use Settings -> Email to connect a shared operations mailbox or staging inbox so Atlas can learn thread shape without immediately acting on live customer traffic.

2. 2

   Connect a staging ERP if available

   If your ERP has a sandbox or staging environment, connect that first from Atlas -> Connectors and run catalog discovery before production.

3. 3

   Verify reads before writes

   Confirm Atlas can read the entities used by the workflow before enabling write or send actions.

4. 4

   Turn on approvals before autonomy

   Start with human approval for external sends and ERP writes, then relax policy once the team trusts the workflow evidence.