Security and trust

Architecture boundaries

The platform separates a shared application layer from tenant data. Tenant workspaces cannot read or write each other's records.

• Shared services: authentication, messaging gateway, API
• Tenant-scoped services: data, forms, workflows, files

Tenant isolation

Each customer organisation has its own workspace and a tenant-specific database. Requests are resolved to a single tenant before any data is accessed.

Authentication

Users sign in to their own workspace. Sessions are managed server-side and can be revoked by administrators.

Permissions (RBAC)

Access is granted by role, team and branch. Authorization is enforced on the server for every request, never trusted from the browser.

• Administrator, manager and operational roles
• Branch- and team-scoped visibility
• Module entitlements per workspace

Credential handling

WhatsApp Business and integration credentials are stored encrypted and are never exposed to the browser.

Audit

Key actions such as sign-ins, assignments, approvals, record changes and configuration changes are recorded.

Backups

Tenant databases are backed up on a regular schedule.

Recovery

Restore procedures are documented and tested so that a tenant can be recovered independently.

Public-link controls

Smart Links are unique per recipient and support expiry, one-time use and OTP verification. Expired or used links cannot be reopened.

Secure development practices

Separate development, staging and production environments, code review before release and ongoing dependency management.