Concepts
The handful of objects Arc0 is built from, from your organization down to a single call.
Two hierarchies matter in Arc0. One is yours: org, project and environment. The other is your user's: customer, connected user and connection. Everything else — apps, actions, policies, approvals and the audit log — sits between them.
Org, project, environment
An org is your company, e.g. Acme. It holds billing, members and org-wide settings like custom domains and OpenTelemetry export.
A project, e.g. "Acme Desk", is where the work happens. Apps, connected users, policies, API keys and the audit log all belong to a project. Most teams run one project per product.
Every project has two environments, Production and Development, picked by the ?env=
query param on any dashboard URL — leave it off and you get production. They share a project's
apps and policies, but keep separate users, keys and audit history. See
Environments for what differs between them.
Customer, connected user, connection
Your customer is the id you pass for a tenant of your own product, such as northwind.
Under it are connected users — the people who actually connect apps, identified by the
external id you already use for them, such as u_8f2.
A connection is one connected user's authorized account in one app: a Gmail inbox, a
Salesforce org, a Slack workspace. Arc0 stores its credentials in a vault encrypted per tenant,
refreshes tokens before they expire, and lets you export them at any time from
POST /v1/orgs/{orgId}/projects/{projectId}/connections/{connectionId}/export
with an authorized staff session, not an execution key. See Token export. A connection can go active, expired (the user needs to
reconnect), revoked, or error ("Refresh failing", while Arc0 retries with backoff).
So the full path from your org down to a single credential is org → project → environment on your side, and customer → connected user → connection on your user's side. An action call sits at the intersection: it runs in a project and environment, as a connected user, over one of their connections.
Apps, actions and scopes
An app is a third-party service, such as Gmail, Slack or Salesforce. A project turns apps on one at a time from a catalog of about 1,500, each declaring how it authenticates — OAuth 2, an API key, or basic auth — and which actions it exposes.
An action is something an agent can do in an app, named app.action, e.g.
gmail.send_email or salesforce.delete_record. Every action carries a grade:
| Grade | Examples |
|---|---|
read | Search messages, list records, fetch a file |
write | Send an email, post a message, create a ticket |
destructive | Delete a record, remove a user, revoke access |
Grades are what policies act on — see below.
Arc0 Connect
The flow your user sees when they authorize an app. It carries your logo and colors on every plan; on paid plans it runs on your own domain and can use your own OAuth apps, so the provider's consent screen names you, not Arc0. See Arc0 Connect.
Arc0 MCP
One MCP endpoint with an authenticated user binding, at https://api.arc0.ai/mcp. Point any remote-MCP
client at it — your own agent, Claude, Cursor — and it can discover and call whatever that
user's connections and your policies allow. The same connections are reachable from your
backend without an agent, over REST or the authenticated proxy. See Arc0 MCP and
REST API and proxy.
Policies, approvals and the audit log
A policy sets rules — Allow, Ask or Deny — for a scope, an app, or a single action, and
applies to the agents it names (or to all other agents, through the * policy). Evaluation
checks the most specific rule first: an action override, then an app rule, then the policy
default.
An ask rule creates an approval: the call is held, logged as blocked with the reason
"Requires approval", and the people in policy.approvers get an email with Approve and Reject
buttons. Once approved, the agent's retry goes through and is logged as allowed. See
Policies and Approvals.
Every call, allowed or not, is written to the audit log — which agent, for which user, in which app, at what scope, and which policy decided it. This is on every plan, including free. See Audit log.