Vianordis
--:--:-- UTCVianordis / SUPPORT
Source verified · Task procedure

Open assigned applications from Portal

Find an entitled application, confirm its state, and launch it through the approved Portal path.

Status
Source verified
Article type
Task procedure
Verified
July 15, 2026
Review cycle
90 days
Language
English · Source
Owner
Vianordis portal, marketplace, and support
Source
gscPortal-v2 · e7035d9
Start here

Audience, roles, and scope

Application discovery and launch from Portal; assignment and licensing are administrator tasks.

Who this is for

  • Users assigned one or more Vianordis applications

Roles

  • Portal user

Before you begin

  • An authenticated Portal session
  • An application entitlement in the current tenant

Article tags

  • portal
  • applications
  • launcher
  • entitlement
Operating guidance

Procedures

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

Procedure 1

Launch an assigned application

Use the Portal card so identity and tenant context are carried through the intended path.

  1. 1
    Confirm Portal context

    Verify the signed-in identity and organization before selecting an application.

  2. 2
    Find the application

    Use the application area or search and review any unavailable, setup, or entitlement status shown on its card.

  3. 3
    Open and verify

    Launch the application, complete sign-in if requested, and confirm the expected tenant before working with data.

Expected result

The assigned application opens in the intended account and tenant, or Portal displays an actionable availability state.

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

  • Portal displays available launch options but does not grant licences or entitlements.
  • An application card can be visible while service setup, subscription, or role requirements remain incomplete.
Problem solving

Troubleshooting

You cannot open Vianordis Portal

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

Portal application cards, launcher behavior, and entitlement-dependent states were reviewed in source.

Reviewed paths at e7035d9

  • src/app/(portal)/page.tsx
  • src/components/dashboard/ServiceCards.tsx
  • src/data/products.ts
Escalation

Contact support

Contact support when

  • A repeatable Vianordis Portal 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

Find app manuals and task guidance

Choose between product manuals, task-oriented knowledge-base articles, service status, and direct support based on the question you need to answer.