Prepare and export A5 conformity evidence
Prepare a scoped A5 conformity evidence package with source, period, owner, review, secure export, and chain-of-custody controls.
Audience, roles, and scope
Admin A5 conformity and export surfaces; qualified legal or assurance professionals determine sufficiency and conformity conclusions.
Who this is for
- Authorized compliance and audit personnel
Roles
- Compliance reviewer
- Evidence custodian
- Auditor
Before you begin
- Approved assessment scope and period
- Named evidence owner and recipients
- Approved secure export destination and retention schedule
Article tags
- a5
- conformity
- evidence
- export
- audit
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Prepare an A5 evidence export
Validate the evidence set before creating a portable package.
- 1Define and review scope
Record tenant, criteria, systems, evidence period, exclusions, owners, reviewers, and purpose of the package.
- 2Validate evidence
Check source, timestamp, completeness, integrity, classification, and relationship to each claimed control; document known gaps.
- 3Export and safeguard
Use the approved export control once, verify the package and manifest, then apply encryption, access, transfer, logging, retention, and disposal rules.
A traceable evidence package exists for the approved scope with limitations and custody controls documented.
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 documented custody record for every evidence copy and recipient.
Known limitations
- The A5 interface and exported material do not establish certification, legal conformity, audit sufficiency, or operating effectiveness.
- Evidence completeness and export format depend on configured sources, retention, permissions, and deployment.
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
A5 conformity and export interfaces were reviewed in the pinned source; no assurance result was inferred from their presence.
Reviewed paths at 8f3a86e
src/app/(base)/administration/a5-conformity/A5ConformityView.tsxsrc/app/api/a5/export/route.tssrc/database/a5.tsdocs/a5-conformity.md
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