Access Control
Authentication and authorization remain separate concerns.
Security is architectural: tenant isolation, RLS, RBAC, secure sessions, protected secrets, auditing and least privilege.
BEZ CRM is structured around Organization → Customer → Conversation → Activity → Opportunity → Revenue, with shared architecture rather than disconnected mini-apps.
Authentication and authorization remain separate concerns.
Cross-tenant data leakage must be prevented at multiple layers.
Provider credentials and privileged keys never belong in browser bundles.
Consequential actions require traceable actor, target and event history.