Skip to content

Support

Onboarding and normal operation are self-service. Start with in-product validation and the troubleshooting guide. Support is an optional escalation or recovery path, never a prerequisite or completion gate.

Escalate a blocked step

contact@venturi.systems

Include only non-secret diagnostic evidence:

  • tenant and connector ID;
  • failed step and validation timestamp;
  • provider error code or correlation ID;
  • redacted command output;
  • last known source-freshness timestamp.

Do not send cloud secrets, federation tokens, provider keys, or customer data. Rotate a credential in-product if exposure is suspected.

Support can interpret evidence and help recover a failed check. It does not create the tenant, issue setup values, register connector outputs, mark a persona complete, or override validation. See guided onboarding.

Product feedback

Use feedback.venturi.systems for feature requests, workflow improvements, non-sensitive bug reports, and connector requests. Do not put secrets, vulnerabilities, or urgent operational evidence in the feedback portal.

Security reports

Follow the disclosure process in the Trust center, or email security@venturi.systems. Do not open a public issue for a suspected vulnerability.

Support access boundary

Venturi has no standing access to a customer tenant. Approved support access is time-boxed, MFA-gated, least-privileged, tenant- and residency-bound, read-only by default, fully audited, and fail-closed. Review Support tiers and Support-access architecture.

Reference material