// HELP CENTER
Common questions, honestly answered.
Setup, agents and approvals, access and limits: what finance and ops teams ask most.
How long does setup actually take?
Connecting a system is minutes — it's an OAuth authorization, not an implementation. Getting a first workflow running, such as CRM-to-ERP customer setup, takes days to weeks; env0 was live in under a week from first connection.
Do we need engineering help?
Not for connecting your ERP, CRM or payroll, running agents or building boards. You may want someone technical to set up a custom system 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 reach a connected system are ones a person approved, or a workflow you chose to run unattended.
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?
Not by default. Every write and send is held: you see the actual record, values or recipient, then approve it, approve part of it, or discard the run. Auto-run is opt-in, per workflow.
What if an agent gets something wrong?
You discard it and nothing is written. 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. Writes wait for approval by default; once you trust a routine workflow, you can set it to run unattended. Every write is logged with who approved it.
Our system has no API. Can you connect it?
Usually, yes. Anything with an API connects through MCP. Web tools without one can be reached through the ORiON Companion, our Chrome extension (in beta). 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 workflow (say, AP matching), board or question it involved, and roughly when.
// NOT ANSWERED HERE