Compliance Glossary for Confluence

Can I add text files?

Yes. Production v6 accepts allow-listed TXT, Markdown, CSV, JSON, and XML files when the extension and MIME type match. It validates UTF-8 content, checks JSON or basic XML structure where relevant, computes SHA-256, and records artifact, revision, provenance, retention, and bounded extracted text evidence.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
TXT, MD, or CSV fileDecode strict UTF-8 textCaptured extracted textInvalid UTF-8 is rejected
JSON fileDecode and parse JSONCaptured text and parser metadataInvalid JSON is rejected
XML fileDecode and check basic document formCaptured text and parser metadataThis is not schema or semantic validation
Accepted bytesHash and normalize evidenceArtifact and immutable revisionUpload and extracted-text limits apply

How it works

  1. Open Upload controlled evidence.
  2. Select an allow-listed text file.
  3. Set retention class and date.
  4. Select Upload evidence.
  5. Wait for integrity and parser checks.
  6. Record the returned artifact and revision identities.

Example

A JSON policy manifest is uploaded as controlled evidence. The parser confirms valid UTF-8 and JSON syntax. The app records the original file hash, revision identity, provenance, retention, and extracted text. It does not judge whether the policy statements are correct.

What this does not mean

Parsing proves that the accepted file meets bounded structural checks. It does not validate a JSON schema, an XML schema, business meaning, legal validity, or regulatory compliance.

Related questions

Evidence Upload IntegrityLarge Evidence File UploadPdf Compliance Evidence

Next step

Use a matching extension and MIME type for every uploaded text file.

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