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

Manage the user lifecycle

Add, review, disable, restore, and offboard tenant users with identity verification, least privilege, and retention checks.

Status
Source verified
Article type
Task procedure
Verified
July 15, 2026
Review cycle
90 days
Language
English · Source
Owner
Vianordis administration product and support
Source
gscAdmin-v2 · 8f3a86e
Start here

Audience, roles, and scope

User records and lifecycle controls in Admin; the authoritative identity provider and HR process can impose additional steps.

Who this is for

  • Tenant identity and user administrators

Roles

  • Tenant administrator
  • User administrator

Before you begin

  • Approved user-lifecycle request
  • Verified identity, employment or membership state, manager, and required access

Article tags

  • users
  • offboarding
  • disable
  • identity
  • lifecycle
Operating guidance

Procedures

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

Procedure 1

Add or update a user

Create the minimum approved identity record and confirm downstream state.

  1. 1
    Validate the request

    Verify the person, unique identifier, tenant, manager or sponsor, start date, and approved access.

  2. 2
    Create or update the record

    Search for duplicates, enter verified fields, assign no more than the approved baseline, and review before saving.

  3. 3
    Verify effective access

    Confirm status and required assignments; notify the requester without sending credentials or sensitive identity data.

Expected result

One accurate user record exists with the approved status and minimum access.

Procedure 2

Disable or offboard a user

Contain access while preserving required records and ownership.

  1. 1
    Confirm authority and timing

    Validate the offboarding request, effective time, legal or retention constraints, and affected applications.

  2. 2
    Disable and remove access

    Use the approved status control, revoke applicable entitlements and privileged access, and follow identity-provider procedures.

  3. 3
    Transfer and verify

    Reassign owned resources where required, verify access loss, and retain the change evidence under policy.

Expected result

The user can no longer access the tenant while required data and ownership are handled according to policy.

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.
  • Never delete or disable a user solely on an unverified email or chat request.
  • Treat restoration as a new authorization decision, not an automatic undo.
Verified scope

Known limitations

  • Admin controls may not automatically update external identity providers, devices, sessions, or every connected application.
  • Deletion, retention, ownership transfer, and legal hold are deployment- and policy-specific.
Problem solving

Troubleshooting

You cannot open Vianordis Admin

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

User list, detail, creation, status, and editing controls were reviewed in the pinned source.

Reviewed paths at 8f3a86e

  • src/app/(base)/management/users/page.tsx
  • src/app/(base)/management/user/details/[userId]/page.tsx
  • src/app/(base)/management/user/add/UserAddView.tsx
  • src/app/(base)/management/disabled-users/DisabledUsersView.tsx
  • src/app/actions/users.ts
Escalation

Contact support

Contact support when

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

Understand administrator access

Distinguish tenant and application administration, verify active scope, and avoid assuming that interface visibility grants authority.