Contact support with safe diagnostic evidence
Prepare a reproducible support request that includes useful context while excluding credentials, regulated data, and unnecessary confidential content.
Audience, roles, and scope
Support request preparation and contact route; contractual priority and response terms depend on the applicable agreement.
Who this is for
- Vianordis users and administrators opening support cases
Roles
- Support requester
- Tenant administrator
Before you begin
- A defined question or symptom
- Completion of safe relevant troubleshooting
- Authorization to disclose the proposed evidence
Article tags
- contact-support
- diagnostics
- screenshots
- privacy
- ticket
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Prepare and submit a support request
Give support a minimal, structured, and safely redacted reproduction package.
- 1State the task and impact
Name the product, tenant, role, expected result, observed result, start time and zone, affected population, and business impact.
- 2Add safe reproduction evidence
List exact steps, browser and version, relevant status, and sanitized record or correlation IDs; crop and redact screenshots before attachment.
- 3Submit once and track
Choose the correct topic and priority, record the case identifier, add follow-up evidence to that case, and verify any proposed resolution.
Support receives one actionable request with sufficient context and no avoidable secret or sensitive-data exposure.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
- Review screenshot browser chrome, notifications, other tabs, filenames, and background content before sharing.
- Use an approved secure transfer channel when support explicitly requires sensitive evidence.
Known limitations
- Submitting a request does not guarantee a particular priority or response time outside the applicable support agreement.
- Support may need additional tenant-authorized evidence or administrator involvement to reproduce the issue.
Troubleshooting
You cannot open Vianordis Support
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
Contact route, form context, and article support guidance were reviewed in the pinned source.
Reviewed paths at 4753b1a
src/app/[locale]/contact/page.tsxsrc/components/ContactForm.tsxsrc/app/api/contact/route.tssrc/app/[locale]/knowledgebase/[category]/[slug]/page.tsx
Contact support
Contact support when
- A repeatable Vianordis Support error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel