Security
Trust is a product surface
Security is presented as actual boundaries and controls—not aspirational badges. Identity, authorization, tenant scope, secrets and durable actions are separate concerns.
Identity is not blanket authority
A valid sign-in proves identity. Access still depends on organization membership, role, entitlement, assurance level and policy.
Credentials stay out of the browser
Provider secrets belong in authorized server-side or vault-backed flows. Customer-facing UI should receive connection state and scoped results, not raw credentials.
Tenant boundaries
Private resources are resolved only inside the authorized tenant and route context. Error behavior must not reveal another tenant’s existence.
Higher-risk actions
Administrative and other high-impact actions require stronger assurance when the corresponding production control is activated. This candidate does not claim every future factor or compliance control is already deployed.