// HELP CENTER
Common questions, honestly answered.
Setup, access, agents and limits — the questions that come up most.
How long does setup actually take?
Connecting a system is minutes — it's an OAuth authorization, not an implementation. Getting to a board you'd actually show someone is usually a few days, and the time goes into deciding what belongs on it rather than into technical work.
Do we need engineering help?
Not for native connectors, dashboards or agents. You may want someone technical for the initial setup of a custom system connected over the Model Context Protocol, and that's a one-time task.
Does anything change in our existing systems?
No. Nothing is migrated, no schema is altered, and your team keeps working exactly where they work today. The only changes that ever reach a connected system are ones a person explicitly approved.
Why can't ORiON see something I expected it to see?
Almost always the connecting account. ORiON inherits the permissions of whoever authorized the system, so if that person can't see a team's records, neither can ORiON. Reconnect with an account that has the visibility you need.
Can other organizations see our data?
No. Isolation is enforced by the database through row-level security rather than by application logic, so a query that loses its organization scope returns nothing rather than returning another tenant's rows.
How do you handle security review?
The Security & Architecture page covers isolation, credential handling, access scope and the approval gate on writes. Send your questionnaire over and we'll work through it with you.
What happens if we leave?
Revoke the connections and ORiON stops seeing your systems. Because it was never a system of record, there's nothing to migrate back — your data never left your ERP, CRM or payroll platform.
Can an agent send something without me knowing?
No. Writing and sending are gated: the agent assembles the action, it's held as pending with its reasoning attached, and a person approves or rejects it. This is structural, not a setting to be switched off.
What if an agent gets something wrong?
You reject the action and it doesn't happen. Because proposals arrive with their source data, a wrong proposal is usually traceable to a wrong input — most often a system connected with narrower access than expected.
Can it run fully autonomously?
Reading and analysis, yes — on a schedule with no involvement. Writing, no. If unattended write access is your requirement, ORiON is the wrong tool and we'd rather say so now.
Our system has no API. Can you connect it?
Usually, yes. Most systems connect through their API or MCP, and where neither exists we can build a secure integration to reach it. Bring the system to the call and we'll tell you what's involved.
Can it replace our BI tool?
Often, for operational reporting at this company size. Not if you need arbitrary custom modelling or a governed semantic layer — that's what BI platforms are for, and they're better at it. The competitive analysis is specific about where the line falls.
Is there an on-premise version?
ORiON runs as a hosted platform. If your environment has specific deployment requirements, raise them on the call.
// REPORTING A PROBLEM
What to include so we can fix it fast.
Your organization name, so we're looking at the right workspace.
What you expected, and what happened instead. Both halves — the gap is the diagnosis.
Which board, question or agent it involved, and roughly when.
// NOT ANSWERED HERE