Documentation
Security & sign-in
Tenant isolation at the database layer, hardened sign-in, and verified account changes.
Workspace isolation
Every workspace's data is segregated with PostgreSQL row-level security enforced on every tenant table. Records of another workspace are invisible — requests for them return not-found, never a hint that they exist.
Ways to sign in
- Password — with a strength policy, rate limiting, and automatic lockout after repeated failures.
- Google and Microsoft sign-in — for existing members only; SSO never creates accounts.
- Passkeys (WebAuthn) on the web — sign in with Face ID, Touch ID, or a security key.
- Biometric unlock on mobile, and per-workspace OIDC configuration for enterprise identity providers.
SAML is not available today; it is on the roadmap.
Verified account changes
Signup and email changes are confirmed with emailed verification codes; password resets are code-based, and you can revoke all of your active sessions at once. Sensitive actions land in the audit log with the actor and IP.
Content safeguards
Uploads reject executable file types, oversized files, and unsafe logo formats; downloads that can't be previewed safely are served as attachments. API traffic is rate-limited and served over TLS in production deployments.
On mobile
Mobile signs in with password or Google/Microsoft, and offers biometric unlock (Face ID / Touch ID / fingerprint). Passkeys are web-only.
Related