Choose an intake route

Use authorised uploads or configured intake channels for repositories, storage and integrations enabled for your deployment. An administrator must configure the connection, approved source boundary, credentials and processing policy before unattended collection can operate.

Cloud storage, enterprise repositories, email/API routes and local-directory integrations require their supported connector or integration path. Do not assume a personal local folder is automatically synchronised simply because it exists on your computer.

Before processing

  1. Confirm you have access to the source and that the configured route accepts its format and size. Upload acceptance alone does not prove the parser supports every file.
  2. Check the current object/version and malware status. Pending scans, unsafe content, changed source bindings or unsupported formats should be resolved through the reported blocker.
  3. Choose preparation settings only where supported: rotation, page selection, clipping, reviewed splitting/grouping, pairing or blank-page removal.
  4. Inspect any proposed change before applying it. A changed file may create a new source version requiring clearance and reprocessing.

Preserve source context

Processing binds to the exact authorised stored source version. Available evidence can include page regions, text offsets, spreadsheet cells or Office XML parts. Different formats provide different geometry; Office parts must not be treated as physical page coordinates.

Splitting and grouping preserve lineage. Pairing two records expresses a relationship, such as invoice and purchase order; it does not establish that their financial values reconcile.

When intake fails

Check the file type, size, scan result, source access and connection state. Ask an administrator to resolve configuration or clearance issues. Repeated retries cannot legitimately bypass malware checks or repair an outdated source/version binding.

Verify a new intake boundary

  1. Choose an approved sample readable by the connection account.
  2. Confirm discovery includes the intended object and excludes material outside the boundary.
  3. Admit the sample and inspect source version and security outcome.
  4. Process it and verify the result links back to that source.