Skip to content
DocumentationSecuritySecurity architecture
SecurityCurrent contractVersion DOCS-2.0

Security architecture

Defense in depth across authentication, backend authorization, RLS, tenant scope, secrets, API controls and auditable evidence.

How to interpret this document

This content describes technical and methodological behavior that is implemented or explicitly planned in the product. When a control depends on configuration, a provider, a secret, a contract or legal approval, that dependency must remain visible.

Authentication and authorization

Base44 authentication establishes the session. The application adds role, tenant, entitlement and service-role authorization where required.

RLS

Sensitive entities define row-level security rules. These complement, but do not replace, explicit backend scope validation.

Tenant scope

Organization, Workspace and Department are revalidated in sensitive flows. Frontend navigation does not grant authorization.

Secrets

Runtime secrets should not be persisted in user-readable business entities. Secret-dependent features remain unavailable or degraded when the dependency is not present.

API credentials

The raw key is returned once. Persistence stores a prefix and SHA-256 hash, with hash access restricted to service-role flows.

Anti-SSRF

Webhooks require HTTPS, reject localhost and private ranges, check private DNS resolution and disable redirects.

Trust boundary

An implemented technical control is not the same as certification, legal opinion or contractual commitment. The Trust Center separates these categories explicitly.