AuraOne / Support

Choose the support path that matches the object and risk.

Documentation, product support, and security disclosure have different owners. Send each one to the right place.

Route product support, documentation questions, and security disclosures directly to the responsible team.

At a glance

Support routing

Overview
Object
A product, an account, or an incident
Impact
Affected users, workflow, and deadline
Evidence
Safe logs, identifiers, and reproduction
Boundary
No secrets or restricted data in public forms

Support paths

Send the right context without exposing sensitive data.

Never send credentials or private datasets through the public form. The same goes for protected health information and anything customer-confidential.

Documentation

Product concepts, task guides, and Open product references.

Category
Self-service
Includes
Current documentation
Good to know
Verify commands, releases, and environment details against the current product documentation.

Product or account support

Tell us the affected product and the impact. Include safe reproduction steps.

Category
Support request
Includes
Submitted brief and governing agreement
Good to know
Coverage and response expectations depend on the customer agreement and request severity.

Security disclosure

Report suspected vulnerabilities through the security report form. Keep exploit detail out of the first message.

Category
Security
Includes
Security disclosure process
Good to know
Avoid public disclosure of exploit detail before a secure communication path is established.

Service status

Check the website health result and the public status paths before opening a duplicate incident.

Category
Operations
Includes
Current status page
Good to know
The public status page may not include customer-specific or restricted incidents.

Commercial and procurement

Pricing, contracts, and security review. Send procurement questions here.

Category
Commercial review
Includes
Qualified brief and governing documents
Good to know
Final pricing, service terms, and review outcomes are confirmed through the commercial process.

Support brief

What to include in a support request

Tell us what broke, how much it hurts, and what you need next. Keep the diagnostics safe to share.

Product
The product, workspace, and page or itemYour request
Impact
Observed behavior, affected scope, and urgencyRequester statement
Evidence
Safe timestamps, request identifiers, and stepsApproved support channel
Next action
Owner, requested information, and any workaroundSupport response
Support request

Send a support request.

Include the affected workflow, impact, and evidence already captured. The request is saved only after the support endpoint accepts it. If the form is unavailable, email [email protected].

Owner
Support desk
Response
Set per program
Record
Saved on acceptance

Request details

Tell the support desk what changed.

Severity
Response targets are set per program