Vianordis
--:--:-- UTCVianordis / SUPPORT
Source verified · Professional reference

Review privacy and account analytics

Use the privacy and analytics views to understand the personal information and account-level activity presented to you.

Status
Source verified
Article type
Professional reference
Verified
July 15, 2026
Review cycle
90 days
Language
English · Source
Owner
Vianordis identity, profile, and support
Source
gscMy-v2 · 1f3e2e3
Start here

Audience, roles, and scope

Personal privacy information and account-facing analytics displayed by My Vianordis.

Who this is for

  • Signed-in users reviewing their own account

Roles

  • Account holder

Before you begin

  • An authenticated session
  • Authorization to view the selected personal data

Article tags

  • privacy
  • analytics
  • account-data
  • activity
Operating guidance

Procedures

Follow the sequence and stop when identity, authorization, target, or result differs from the article.

Procedure 1

Review personal data and activity

Interpret the displayed information without treating it as a tenant audit record.

  1. 1
    Open Privacy

    Read the available account-data explanations and confirm which account the page represents.

  2. 2
    Open Analytics

    Review the displayed time range, units, and activity summaries before drawing conclusions.

  3. 3
    Escalate discrepancies safely

    Record sanitized labels, timestamps, and expected behavior; use the approved support route for material discrepancies.

Expected result

You can identify what the personal views show and where a discrepancy should be investigated.

Operating rules

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.
Verified scope

Known limitations

  • Account analytics are not a substitute for tenant audit, billing, security-monitoring, or compliance records.
  • Displayed metrics and retention depend on available backend data and deployment configuration.
Problem solving

Troubleshooting

You cannot open My Vianordis

Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.

  1. Open the service through the approved Vianordis entry point and sign in again.
  2. Confirm the intended organization, tenant, and account are in use.
  3. 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.

  1. Confirm the audience, role, prerequisites, and limitations in this article.
  2. Refresh after a new sign-in and verify the correct tenant context.
  3. 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.

  1. Review inline validation, status indicators, filters, and the selected tenant or workspace.
  2. Refresh once and search by a stable identifier before repeating the action.
  3. Do not repeat irreversible or externally visible actions until the first operation's state is known.
Provenance

Source verification

Privacy and analytics views, labels, and navigation were reviewed in source.

Reviewed paths at 1f3e2e3

  • src/app/(my)/privacy/page.tsx
  • src/app/(my)/analytics/page.tsx
  • src/components/account/UserPrivacy.tsx
  • src/components/account/UserAnalytics.tsx
Escalation

Contact support

Contact support when

  • A repeatable My Vianordis 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
Contact support
Continue reading

Related guidance