Security approach

Paid launch gate: WorkQuarter will not intentionally onboard production customer CRM data until its multi-tenant controls and production data architecture have been verified.

Current early-access controls

• Private setup and Automation Studio records require authenticated access.
• Current preview records are scoped by the authenticated account rather than accepted from a browser-supplied owner ID.
• Automation Studio is test-only and does not send messages or book live jobs.
• The setup flow does not currently collect payment-card details or claim mailbox access.
• Secrets must be stored in server-side secret stores and never committed to source or exposed to browser code.

Production controls being required

• Every customer-owned record must carry a workspace identifier and be protected by tenant-aware authorisation.
• Database Row Level Security will provide a second boundary in addition to application checks.
• Owner, administrator and staff permissions will be explicit and least-privilege.
• Security-sensitive actions will be auditable.
• Backups, restore testing, customer export/deletion and incident response will be defined before commercial launch.
• Production API credentials will remain server-side and be independently rotatable.

Source and hosting resilience

Production readiness requires a private source-control master copy independent of the deployment host, reproducible database migrations and documented exit/export procedures. This is intended to prevent the hosting platform from becoming the only copy of the product.

Responsible disclosure

A dedicated security contact and disclosure process will be published before general availability. Until then, do not test the service in a way that could access another person's data or disrupt availability.