Security belongs in the product
Operators need to see whether sender domains, signed routes, secrets, and policy gates are ready before support traffic scales.
- Signature verification
- Domain status
- Outbound limits







A visible control plane for MFA, signed inbound routes, domain readiness, prompt-injection flags, and executor gates.
Security health is part of daily operations.
Workspace access and project data stay separated.
Executors check policy before side effects.
Operators need to see whether sender domains, signed routes, secrets, and policy gates are ready before support traffic scales.
Suspicious instructions in email bodies and attachments are flagged as support risk, not treated as trusted system context.
These pages describe the product contract behind the UI, not a decorative brochure. Each surface should connect back to the same governed support loop.
Provider tokens are never exposed client-side.
Support moves through secure ingest, AI preparation, human approval, outbound execution, and audit evidence.
Provider setup, project policies, knowledge trust, retention, and billing limits decide how this behaves for a real workspace.
These external links point to provider documentation, privacy notices, data-processing terms, or platform terms that shape production operation.