Manage products, licences, and marketplace subscriptions
Review commercial scope and capacity before changing product, licence, or Marketplace subscription state.
Audience, roles, and scope
Admin subscription-management surfaces; executed contracts, invoices, and provider terms remain authoritative.
Who this is for
- Authorized subscription and licence administrators
Roles
- Subscription administrator
- Licence administrator
- Procurement reviewer
Before you begin
- Purchase or change authorization
- Known tenant, product, quantity, term, owner, and cost centre
Article tags
- products
- licences
- subscriptions
- marketplace
- billing
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Prepare a subscription or licence change
Reconcile commercial authority and operational effects before saving.
- 1Verify the commercial request
Confirm product or skill, quantity, term, tenant, currency, taxes, approver, and contract or order reference.
- 2Review impact
Check current use, available capacity, renewal or cancellation timing, dependent entitlements, and displayed price limitations.
- 3Apply and reconcile
Make the approved change once, retain confirmation, and verify capacity, entitlement, and later invoice state.
The subscription state matches the approved commercial request and can be reconciled to entitlement and billing records.
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.
- Separate purchasing authority from technical assignment where policy requires it.
Known limitations
- Displayed catalogue or price information is not a substitute for the executed contract, order, tax treatment, or invoice.
- Provider Marketplace terms and provisioning can add separate obligations or delays.
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.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- 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.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- 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.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
Product, licence, and Marketplace subscription routes and controls were reviewed in source.
Reviewed paths at 8f3a86e
src/app/(base)/subscription/myproducts/MyProductsView.tsxsrc/app/(base)/subscription/licences/LicencesView.tsxsrc/app/(base)/subscription/marketplace/MarketplaceView.tsxsrc/database/subscriptions.ts
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