Vianordis
--:--:-- UTCVianordis / SUPPORT
Beta guidance · Task procedure

Configure voice and personal agent settings

Review the personal voice and agent controls exposed in My Vianordis and validate availability before relying on them.

Status
Beta guidance
Article type
Task procedure
Verified
July 15, 2026
Review cycle
45 days
Language
English · Source
Owner
Vianordis identity, profile, and support
Source
gscMy-v2 · 1f3e2e3
Start here

Audience, roles, and scope

Personal configuration surfaces; not tenant AI-provider, model, policy, or agent governance.

Who this is for

  • Users with enabled voice or agent capabilities

Roles

  • Account holder

Before you begin

  • An authenticated account
  • The relevant capability enabled for the tenant and user

Article tags

  • voice
  • agent
  • ai
  • preferences
  • preview
Operating guidance

Procedures

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

Procedure 1

Configure an available capability

Confirm enablement and test with non-sensitive input.

  1. 1
    Open the relevant settings page

    Choose Voice or Agents and read any availability, preview, or policy notice.

  2. 2
    Apply the minimum preference

    Select an approved option without entering secrets, regulated data, or confidential instructions.

  3. 3
    Test and verify

    Use a harmless test, confirm the visible result, and revert the preference if behavior differs from expectation.

Expected result

An enabled preference behaves as shown, or the user identifies that the capability is unavailable or preview-only.

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

  • Voice and personal agent capabilities are beta surfaces whose availability and persistence can vary by deployment.
  • This page does not configure tenant model providers, credentials, retention, or organization-wide AI policy.
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

Personal voice and agent routes and controls were reviewed; backend availability must still be confirmed per deployment.

Reviewed paths at 1f3e2e3

  • src/app/(my)/voice/page.tsx
  • src/app/(my)/agent/page.tsx
  • src/components/account/UserVoiceSettings.tsx
  • src/components/settings/AgentSettingsForm.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