Security
Security is an architectural feature, not a settings page.
RevenuePilot is built from the database up for strict multi-tenant isolation, capability-based access and complete auditability.
Multi-tenant database isolation
Row-level security is enabled on every tenant table. Frontend filtering is never treated as authorization.
Server-side authorization
Capability-based permissions are re-checked server-side on every route, RPC and workflow action.
Least-privilege credentials
Service-role keys, OAuth secrets and provider tokens are server-side only and never reach browser code.
Comprehensive audit log
Human, AI, automation and integration actions are recorded with before/after state and correlation IDs.
Webhook & input validation
External payloads are validated, idempotency keys prevent duplicates, and replay protection is applied.
Controlled AI
Agents act through authorized tools scoped to one organization. Cross-tenant retrieval is impossible by design.
Testing enforcement
Tenant-isolation, RLS, authorization and webhook-replay tests are part of the release gate. A feature is not finished because its UI renders — it must pass authorization, isolation and audit checks too. Full security documentation is in the product documentation set.