Academy
Academy
Learn how Acumatica teams can adopt AI agents through controlled workflows, OAuth, permissions, allowlists, approvals, and audit review.
Academy is the practical path for teams evaluating Acumatica MCP Tools. It explains how an AI agent can help with real Acumatica work while OAuth, Acumatica permissions, MCP scopes, allowlists, limits, metadata validation, and audit logs keep the workflow bounded.
Use this Academy to choose one workflow for the first deployment. A good first workflow is narrow enough to review, useful enough to test with real records, and clear enough that the admin can verify the allowed path and at least one denied path before expanding access.
How to Use Academy
Start with the foundation lessons if your team is still aligning on what an ERP agent should be allowed to do. These pages explain the operating model: the AI client coordinates the work, Acumatica remains the system of record, and the MCP server controls the tool surface between them.
Then choose one workflow. These pages are not generic examples. Each one names the Acumatica records involved, the tools likely needed, the approval point, and the guardrails that should be visible during guided deployment.
Use the developer docs when you are ready to configure or verify the runtime. The Academy helps you choose the work. The docs explain the setup details.
Foundations
The foundation lessons explain the control model before a team chooses a workflow.
Agentic Operations defines the difference between chat and controlled operational assistance. It is the best first page for business owners, operators, and implementation partners.
ERP Guardrails explains the control stack in practical ERP terms: OAuth, Acumatica permissions, MCP scopes, allowlists, limits, metadata validation, and audit logs.
MCP Connection shows where the AI client, hosted MCP endpoint, Acumatica OAuth flow, and Acumatica APIs fit together.
Read vs. Write Access helps teams decide whether the first workflow should stay read-only or add one narrow write, attachment, or action path.
Workflows
Workflow pages show how the first implementation can be useful without becoming broad automation.
Order Desk is for customer PO intake, item matching, reviewed sales order work, source document attachment, and shipment handoff.
Inventory & Fulfillment is for availability questions, ready-to-ship review, shipment blockers, allocation recommendations, and fulfillment exceptions.
Executive Intelligence is for read-only operating briefs across approved Acumatica data sources.
Document Reconciliation is for comparing invoices, packing lists, BOLs, PODs, customer POs, claims, and warehouse notes against Acumatica records before attachments or updates.
CRM Sales Development is for reviewed prospecting that combines territory context, enrichment, Acumatica duplicate checks, lead creation approval, campaign attribution, tasks, and email activity drafts.
Choosing the First Workflow
Pick a workflow your team already repeats every week. Avoid starting with a broad instruction like “make Acumatica smarter.” Bring a concrete example instead: one customer PO, one blocked shipment question, one executive exception brief, one document packet, or one CRM segment.
A strong first workflow has a clear owner, approved Acumatica data sources, a visible human approval point, and an obvious denied operation to test. The denied operation matters because it proves the workflow did not accidentally open every ERP action.
Safety Reference
Before enabling writes, review the Safety Model, Acumatica OAuth Setup, and Configuration Reference. Those developer docs are the source of truth for OAuth, Acumatica permissions, MCP scopes, allowlists, rate limits, concurrency limits, and audit logs.
For a first guided deployment, start read-only, verify the records and inquiries needed for the workflow, then enable only the specific write, attachment, action, task, or email-draft path the team approves.