Organizational identity, company isolation, application permissions and protected connection credentials are part of the architecture. These mechanisms are material for a deployment-specific security review. No SOC 2 report, independent penetration-test result or security certification is claimed here.
WorkOS-backed identity connects the organization to supported sign-in and enterprise identity administration. Single Sign-On, directory synchronization and domain administration use the available setup and entitlements. The application resolves company membership and permissions alongside that identity, so signing in and authorizing a consequential business action remain separate decisions.
Company scope follows the request into data access. Tenant-scoped connections require an explicit company context, and database policies constrain company records. Application authorization distinguishes laboratory members, platform operators and portal customers, with additional role and privilege checks where the operation requires them.
Customer portal access follows the account and permitted sites. Internal conversations, customer-service conversations, released documents and technical approvals each have their own access rules. The person who may read a record does not automatically acquire permission to change, approve or release it.
Connection credentials are encrypted with tenant-bound authenticated encryption and stored with a key version so supported rotation can preserve the connection. Administrative summaries show identifying metadata rather than the secret itself. Company message policies govern editing, deletion and retention, while file and real-time access use their own checks.
Deployment configuration, provider choices and organizational operating procedures complete the security design. Identity, permissions, tenant boundaries and retained evidence give the organization concrete controls to examine during its own security review.