1. Security model in one paragraph
WorkBOS is multi-tenant by design, and isolation is enforced where it cannot be bypassed: the database. Every table carries row-level security (RLS) that scopes every read and write to your workspace; the application UI is never the security boundary. Role-based access control layers on top, AI agents act under the same permissions as the human who approves them, and every metered or public path is rate-limited and cost-capped.
2. Tenant isolation
- Row-level security enabled on every business table — fail closed: an unauthorized query returns nothing.
- Org membership predicates gate all access; archived workspaces disappear platform-wide automatically.
- Restrictive database policies additionally enforce per-page create/update/delete rights (84 policies and growing).
- Cross-tenant reads and writes are structurally impossible, and we prove it: every schema change ships only after simulated allow / deny / cross-tenant tests run against the real policies.
3. Access control & authentication
- Role-based access control: owner, admin, member and guest tiers, per-page permission matrices, per-user overrides.
- Guests are permission-fenced to explicitly granted areas (Viewer / Collaborator / Contributor levels).
- Authentication via Supabase Auth; passwords are hashed, never stored in plaintext, never visible to us.
- Multi-factor authentication support is built into the platform (rolling out progressively).
- Session-scoped API keys with per-day caps, one-time display, and instant revocation for programmatic access.
4. AI agent governance
- Approve-first: agents propose; a human with authority approves; only then does execution happen.
- Agents execute through the same permission-checked paths as humans — no elevated backdoors.
- Optional unattended execution is off by default, limited to low-risk action classes, guarded by denylists, daily caps and a kill switch.
- Every proposal, approval, execution and rollback is logged with who, what and when.
- Per-tenant AI cost ceilings prevent runaway usage; bring-your-own-model endpoints are SSRF-guarded.
5. Data protection
- Encryption in transit (TLS) and at rest (managed Postgres encryption).
- Secrets and credentials live in an encrypted vault with server-only reveal — never in the codebase.
- Every uploaded file is antivirus-scanned at ingest and quarantined on failure; unscanned files cannot be downloaded (enforced by RLS, not UI).
- Per-workspace storage quotas and upload size caps.
- Soft-delete and archive flows precede any permanent deletion; deletion is scheduled, cancellable, then purged on a fixed retention schedule.
6. Payments security
- All payments processed by Stripe (PCI-DSS Level 1); WorkBOS never sees or stores full card numbers.
- Webhooks are HMAC signature-verified with replay-window checks; conversion and billing writes are idempotent.
- Amounts are always computed server-side — never trusted from a browser.
- Hard cost caps and circuit breakers on email volume, AI usage and scanning spend.
7. Secure development lifecycle
- Branch-protected main; every change lands through a pull request.
- Automated gates on every PR: secret scanning (gitleaks), static analysis (semgrep), dependency audit (npm audit), type checks and tests.
- Progressive delivery: features ship dark and roll out by cohort (internal → beta → percentage → GA), containing blast radius.
- Versioned releases with an audited publish flow and one-click rollback.
- Database changes follow expand→contract migration patterns with backups before risky operations.
8. Abuse prevention
- All anonymous/public endpoints (forms, booking, referral clicks) are rate-limited with honeypots and payload caps.
- Authenticated abuse ceilings on heavy operations (exports, bulk deletes) — fair-use protection for all tenants.
- Platform-level RLS coverage monitoring: zero tables ship without policies.
9. Availability & continuity
- Hosted on Vercel (application) and Supabase (database) with managed redundancy.
- Automated database backups with retention; tested restore paths for risky changes.
- Health and scale-readiness instrumentation reviewed continuously; capacity decisions are data-driven.
10. White-label & reseller security
Reseller sub-tenants inherit the same isolation guarantees as any workspace. Resellers manage only their own child workspaces; snapshot cloning copies configuration, never another tenant’s data; and agent autonomy settings are deliberately excluded from cloning so every new workspace starts approve-first.
11. Responsible disclosure
Found a vulnerability? Email security@workbos.com with details and reproduction steps. We commit to acknowledging reports quickly, fixing verified issues promptly, and crediting reporters who wish to be named. Please do not access data that is not yours or degrade the service while researching.
12. Questions
Security questionnaires, DPA requests and compliance questions: security@workbos.com.