// DOCUMENTATION
Connect your ERP. Write an agent. Build a board.
For finance and ops teams automating manual ERP work. If a step needs an engineer, it says so.
Getting started
Your organization, your first connection, and the shape of the workspace.
02Connections
Connecting your ERP and the systems around it, what access ORiON inherits, and how to change it.
03Agents
Handing manual ERP work to an agent, scheduling runs, and approving each write.
04Dashboards
Seeing the ERP work: widgets, the canvas, saved boards and PDF reports.
05Asking questions
How to phrase things, and how to check where an answer came from.
06Administration
Members, roles, and what happens to connections when someone leaves.
Getting started
Everything in ORiON belongs to an organization. When you first sign in you're placed in one, and every connection, board and agent you create lives inside it. If you work across two legal entities, they're two organizations.
Connect one system first
Start with your ERP, where most of the manual work lands. Connecting the CRM, billing or payroll later makes existing agents and boards better informed automatically.
Hand an agent one task you do by hand
Pick something repetitive and easy to check, like re-keying a closed deal into the ERP. Every write waits for your approval.
Check it against what you already know
Ask a question you can verify, or rebuild a report you already produce as a board, then check the Context Graph for the records it used.
Connections
Connecting a system is an OAuth flow: you authorize ORiON from inside the system you're connecting, and no credentials are typed into ORiON itself. ORiON works with NetSuite, SAP, Dynamics 365, QuickBooks and other ERPs, plus your CRM, billing, payroll and email. Anything else with an API connects through MCP, which may need someone technical to set up.
The single most important thing to understand: ORiON inherits the permissions of whoever connected the account. Connect with a narrow account and you get a narrow view.
If answers look incomplete, check who connected the system before assuming a data problem. Reconnecting with a broader account takes under a minute and resolves most of these.
Dashboards
The workspace is a canvas. Open the widget catalog, drag what you want onto the board, and arrange it. There are forty widgets covering cash, AR and AP, spend, revenue, payroll and system activity. Widgets read live from your connections, so a board is current whenever it's opened.
You can also skip the assembly: describe the board you want and ORiON builds it. Editing afterwards works the same as a board you built by hand.
Save as many boards as you need, and export any of them as a PDF report — which is how most boards end up in front of an executive team.
Asking questions
Write the question the way you'd ask a colleague. Two habits make answers noticeably better:
"This quarter" or "since June" removes the biggest source of ambiguity in a finance or operations question.
"Why?" and "which ones?" are cheap. The first answer is a summary; the second is usually the useful one.
Every answer carries its sources. Before a number goes in front of anyone who might challenge it, open the Context Graph and check what it was drawn from.
Agents
You give an agent a goal in plain language, not a flowchart: for example, "each morning, find overdue invoices and draft a reminder per customer." Any manual ERP process works the same way. Good goals say what to look at, what to flag and what to do. Agents run on demand or on a schedule.
When an agent is about to create a record, change a field or send an email, it stops. You see the actual values or recipient and approve it, approve part of it, or discard the run. Nothing executes by default; trusted workflows can be set to run unattended.
Start with the re-keying nobody enjoys, for example building a closed deal's customer in the ERP from the CRM. It's repetitive, easy to check, and every write waits for approval.
Administration
Administrators manage who belongs to the organization and which systems are connected. Members work inside it — running agents, building boards, asking questions.
One operational consequence worth planning for: because connections are per-user, removing someone's access also removes the connections they own. If a person who connected a critical system is leaving, reconnect it under someone who is staying first.
// STUCK