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

Prepare for organization onboarding

Collect organizational, tenant, security, administrator, licence, billing, and approval information before opening the onboarding link.

Status
Source verified
Article type
Task procedure
Verified
July 15, 2026
Review cycle
90 days
Language
English · Source
Owner
Vianordis onboarding, commercial operations, and support
Source
gscOnboarding · 31be4c3
Start here

Audience, roles, and scope

Defines the information and decisions needed for the seven-stage onboarding wizard; it does not approve the organization or bypass screening.

Who this is for

  • Organization sponsors
  • Prospective tenant administrators
  • Security, procurement, and finance reviewers

Roles

  • Verified registrant
  • Authorized organization representative

Before you begin

  • A valid registration/onboarding link
  • Authority to represent the organization
  • Agreement on tenant name, subdomain, products, security baseline, administrator, and billing method

Article tags

  • onboarding preparation
  • organization setup
  • tenant
  • licence
  • billing
Operating guidance

Procedures

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

Procedure 1

Prepare the onboarding decision pack

Agree inputs before the token-limited wizard session begins.

  1. 1
    Prepare company identity

    Collect trading and legal names, organization type and size, website, registered address, and authorized contact details.

  2. 2
    Choose tenant identity

    Propose a tenant name and acceptable subdomain alternatives that do not use reserved or misleading names.

  3. 3
    Select service scope

    Agree the bundle plan, required products, optional products, quantities, and commercial owner.

  4. 4
    Approve the security baseline

    Choose audit logging, retention, authentication tier, password policy, and any required compliance controls.

  5. 5
    Name the initial administrator

    Confirm the administrator identity, mailbox control, role authority, and separation from the commercial contact where applicable.

  6. 6
    Prepare billing information

    Confirm billing address, method, VAT identifier format, finance contact, and purchasing authority.

  7. 7
    Define final reviewers

    Name the people who must verify data, terms, privacy, pricing, and authority before submission.

Expected result

The onboarding representative has an approved, complete decision pack and does not need to invent security, billing, or authority details during submission.

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.
  • Use a named administrator mailbox controlled by the intended person.
  • Share the onboarding link only with the authorized representative.
  • Agree passwords and secrets directly in supported protected fields, never in preparation documents or support tickets.
Verified scope

Known limitations

  • Sanctions, identity, commercial, tax, and provisioning review may continue after form submission.
  • Available plans, products, countries, payment methods, and security options depend on the current release and commercial configuration.
Problem solving

Troubleshooting

You cannot open Vianordis Onboarding

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

Wizard stage order, required data, synchronous validation, sanctions screening, subdomain availability, VAT rules, and review submission.

Reviewed paths at 31be4c3

  • src/components/wizard/OnboardingWizard.tsx
  • src/components/wizard/CompanyStep.tsx
  • src/components/wizard/TenantStep.tsx
  • src/components/wizard/LicenseStep.tsx
  • src/components/wizard/SecurityStep.tsx
  • src/components/wizard/AdminStep.tsx
  • src/components/wizard/PaymentStep.tsx
Escalation

Contact support

Contact support when

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