Trust
Security overview
Qanivo’s target product authority treats Workspace isolation, backend authorization, secret non-exposure, governed actions, evidence, and safe degradation as product requirements—not optional implementation details.
Scope and authorization
- Protected operations require authenticated actor context
- Workspace or platform scope is resolved from trusted context
- Screen visibility and portal separation never replace backend authorization
- Cross-Workspace access must fail closed
Credentials and integrations
- Provider credentials remain within their Connection Instance custody boundary
- Raw secrets must not appear in browser bundles, UI responses, logs, analytics, exports, Event Hooks, or AI traces
- External Consumers use scoped non-human credentials and never receive human roles or provider credentials
- Provider Webhooks, Qanivo Event Hooks, and Workflow webhook actions remain distinct
Sensitive actions
Publishing, public replies, campaign activation, spend, audience, destination, tracking, and other sensitive operations retain their accepted permission, approval, current-state revalidation, idempotency, and Audit boundaries.
Operational evidence
Security and operational claims require independent implementation evidence, testing, monitoring, recovery validation, and acceptance. Product authority alone does not prove readiness.