Overview

Choose a supported intake path for PDFs, exported email, structured metadata, and connected document repositories.

Audience

• Admin
• Lawyer
• Ops

Product Area

Document Intake

Prerequisites

• Target matter or workspace selected
• Permission to process the source material

Steps

1. Choose the intake path

Use direct upload for bounded files, a connector for continuously managed repositories, and a manifest-backed batch for legacy collections.

1. Prepare files and metadata

Confirm file readability, remove password protection where policy permits, and provide matter, source, date, and document-type metadata.

1. Run validation before analysis

Review rejected files, duplicate detection, extraction status, and source attribution before starting AI-assisted work.

Expected Result

Every accepted document has an immutable source record, matter scope, ingestion status, and reviewable extraction result.

Security and Audit Notes

• Import only material your organization is authorized to process.
• Treat email exports and document metadata as potentially privileged or personal data.

Limits and Preconditions

• Connector availability depends on tenant configuration.
• Unsupported, encrypted, corrupted, or low-quality scanned files may require manual remediation.

Troubleshooting

• A file is accepted but no text is extracted: Check encryption, scan quality, supported format, and OCR status; retain the original file as evidence.
• Documents appear in the wrong matter: Stop downstream processing and correct the matter binding before re-indexing.

Related Articles

• Import Legacy Contracts
• Import Litigation Documents
• Troubleshoot Failed Import

Escalation

If the documented result cannot be reached after the checks above, capture the workspace identifier, affected product area, timestamp, and a redacted error message, then use Support. Never include secrets, privileged legal content, or customer documents in the initial report.