Use service status and administrative reports
Interpret Admin status and report views as operational indicators, confirm freshness and source, and avoid treating sample activity as audit evidence.
Audience, roles, and scope
Status and report interfaces in Admin; authoritative incident, audit, financial, and compliance records may reside elsewhere.
Who this is for
- Tenant administrators
- Operational reviewers
Roles
- Tenant administrator
- Service reviewer
Before you begin
- Authorization for tenant operational information
- A defined reporting question and time range
Article tags
- status
- reports
- metrics
- sample-data
- operations
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Review a status or report indicator
Validate scope and freshness before escalation or decision-making.
- 1Confirm context
Check tenant, service, metric definition, time range, filters, update time, and any sample or preview indication.
- 2Corroborate material findings
Compare with the support status route, source service, ticket, or authoritative audit system as appropriate.
- 3Record a qualified conclusion
State the source, timestamp, filters, limitations, and corroborating evidence rather than copying a number without context.
The indicator is used with its source and limitations understood, and material discrepancies follow the correct investigation path.
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.
Known limitations
- Administrative reporting is beta in this revision and some activity is sample data, not production audit evidence.
- Status and metrics can lag, aggregate, or omit events and must not be used alone for compliance, billing, or incident conclusions.
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
Status and reporting surfaces were reviewed; portions of report activity are represented by sample data in the pinned revision.
Reviewed paths at 8f3a86e
src/app/(base)/status/overview/StatusOverviewView.tsxsrc/app/(base)/status/reports/ReportsView.tsxsrc/database/reports.tssrc/app/actions/status.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