All capabilities
12 / 14Fail closed
Access that is explicit, scoped, and auditable.
Organizations, roles, and revocable API keys decide who can reach each connection, file, and job. Secrets stay encrypted, and read-only connections stay read-only — enforced by the engine, not by convention.
Guardrails
Organizations & rolesRevocable API keysRead-only enforcementEncrypted secretsAudit trailFail-closed routing
The problem
One shared database password makes every tool a full-privilege tool. Auditing who ran what becomes impossible exactly when it matters most.
The River approach
River gates every route with a permission catalog, scopes access per organization, and rejects write plans against read-only connections before they reach a backend.
See it working
Inside Security & Access.
river.local / access
PermissionOwnerAdminDeveloperAnalyst
Queries
Dashboards
Files
Connections
Members
Billing
secrets encrypted at restread-only enforced by the plannerevery AI execution audited
What changes for your team
Less friction between the question and the answer.
Give each person and service only the access they need
Prove who confirmed a query, including AI-generated SQL
Keep credentials encrypted and out of logs and APIs
01
Scope
Assign roles and permissions per organization.
02
Protect
Encrypt secrets and revoke keys centrally.
03
Audit
Review the trail behind every execution.
Next capability