// DOCUMENTATION
Connect a system. Build a board. Write an agent.
Everything here assumes no technical background. If a step needs an engineer, it says so.
Getting started
Your organization, your first connection, and the shape of the workspace.
02Connections
Connecting systems, what access ORiON inherits, and how to widen or narrow it.
03Dashboards
Widgets, the canvas, saving boards, and exporting a PDF report.
04Asking questions
How to phrase things, and how to check where an answer came from.
05Agents
Writing a goal, scheduling a run, and approving the actions it proposes.
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
Pick the one holding the numbers you're asked about most. Connecting more later makes existing boards and agents better informed automatically.
Ask it something you already know the answer to
The fastest way to calibrate trust. Ask a question you can verify, then check the Context Graph to see which records it used.
Rebuild your existing report as a board
Not a new report — the one you already produce. It gives you a direct comparison, and it's usually where the first discrepancy turns up.
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. For systems without a native connector, ORiON connects through the Model Context Protocol — that route may need someone technical for the initial setup.
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 pipeline, cash, spend, headcount, correspondence 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 an operational 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. Good goals describe the outcome and the boundary: what to look at, what counts as worth flagging, and what to do about it. Agents run on demand or on a schedule.
When an agent wants to write to a connected system or send something, it stops. The proposed action appears with its reasoning and source data attached, and waits for a person to approve or reject it. Nothing reaches your systems before that.
Your first agent should be the recurring report nobody enjoys producing. It's low risk, the output is easy to check, and it pays for itself in the first month.
Administration
Administrators manage who belongs to the organization and which systems are connected. Members work inside it — asking questions, building boards, running agents.
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