Security

Workspace isolation by default.

Crimson treats every workspace as a hard tenancy boundary enforced in the database, not in application code.

Row-level security

Every record carries a workspace id, and access is granted through capability checks rather than role-name string comparisons.

Messaging, telephony, and mailbox credentials are stored encrypted and scoped to the workspace that owns them.

Writes are recorded with actor, workspace, and payload so any change can be traced and reversed.