Compliance Glossary for Confluence

How do I re-import an archive?

Select the archive package and choose Import archive. Compliance Glossary treats the package as untrusted. It validates tenant and schema identity, ordered parts, record counts, canonical hashes, and the root hash. Stored multipart imports run in bounded, resumable deliveries. Promotion occurs only after imported counts and the compact part proof match the manifest.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
JSON or ZIP archiveSelect Archive packageFile ready for importAn administrator and active license are required in the workspace
ManifestValidate tenant, baseline, schema, part count, and root hashAccepted manifest or explicit errorA tenant mismatch blocks import
Ordered archive partsRecalculate content and part hashesVerified part chainMissing, changed, reordered, or mis-keyed parts fail validation
Archived recordsCheck schema, identity, order, duplicates, and section countsReconstructed evidence collectionsInteractive import is limited to 5,000 declared records
Stored multipart importWrite bounded, idempotent slicesResumable import checkpointsEach delivery processes 100 records by default and no more than 500
Completed stored importCompare row count, part proof, and manifest rootPromoted import jobAny parity failure blocks promotion

How it works

  1. Open Enterprise evidence workspace.
  2. Find Verification and portable evidence.
  3. Under Archive package, select the JSON or ZIP file.
  4. Select Import archive.
  5. Read the visible completion or failure message.
  6. Resolve every tenant, schema, count, order, or hash error.
  7. Use the imported evidence only after validation and parity checks pass.

Example

An exported archive contains three ordered parts. The second part was replaced after export. Import recalculates its content and part hashes. They no longer match the manifest. Validation fails, and the package is not promoted. An unchanged package with matching counts, part proof, and root hash can complete the import flow.

What this does not mean

Import restores only evidence contained in the validated package. It does not bypass tenant boundaries. It does not merge damaged records. It does not certify compliance or prove that the original sources were correct. The archive is tamper-evident evidence, not legal WORM storage or a full Confluence backup.

Related questions

Verifiable Compliance Evidence ArchiveVerify Exported Evidence ArchiveEvidence Archive Mutation Detection

Next step

Import one exported archive and resolve every validation error before relying on its evidence.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 26 September 2026.