Skip to main content

Support

Choose the support path that matches the question.

Workspace access, implementation questions, account protection, privacy requests, and vulnerability reports use different paths. VehicleDesk does not expose a public ticket form or give support standing access to a shop.

Existing workspace users

Sign in to continue working. Product support and service expectations follow the approved implementation or commercial agreement; the authenticated diagnostics console is not a customer ticket inbox.

Sign in

Account protection

Signed-in users can review active sessions and account-security controls. If sign-in is unavailable, use the approved recovery or support channel named during implementation.

Open account security

Product and fit questions

Use the workflow-review page to examine one owner, advisor, implementation, or trust decision without sending production records.

Explore the workflow review

Security reports

Use the bounded vulnerability-disclosure instructions, not a product or sales request. Continuous mailbox monitoring still requires launch confirmation.

View disclosure contact

Privacy requests

Review the current public-site privacy summary. A monitored public request address must be configured before outside requests are accepted.

Review privacy summary

Accessibility feedback

Review the current accessibility target, implemented interaction patterns, remaining manual evidence, and the contact limitation for this environment.

Review accessibility

Support-access boundary

A shop controls when diagnostics become visible.

The implemented support console is an external-operator tool, not permanent Super Admin access to every tenant.

Shop-approved window

Time, scope, operator, and reason are explicit.

An owner can approve an eligible support operator for 15 minutes to 8 hours and limit the grant to readiness, health, audit, or job evidence. The shop can review history and revoke an active grant.

Read-only diagnostics

Support cannot silently work as the shop.

Each view requires a case-specific reason and is recorded in the target shop's audit history. The console is designed not to expose secrets or customer PII, send messages, call providers, or mutate shop records.