Import storage files into an App

Capture independent App files for document processing without moving the originals.

Select provider files and drag them onto the App's File Upload component, or use Add to App files for the equivalent keyboard action. The App must include a configured upload target and permit imports from the selected connection.

What an import does

Strive copies the selected bytes into the App's managed storage. The upload component receives the imported file references and continues its normal ingestion behavior. The source provider file stays independent from the App copy.

An import is a snapshot, not a live connection to a mutable file. Later changes, renames, or deletion at the provider do not rewrite the imported bytes. Import a later revision deliberately if you want the App to process it.

Follow the stages

Admission means the import was accepted for processing. A completed storage copy means the snapshot is available. Document ingestion and extraction can still be running afterward. Check the File Upload component's per-file feedback and resulting document records before treating the entire batch as ready.

If a transfer completes but finalization is interrupted, recovery can use the verified existing snapshots without duplicating the ingestion event. Inspect the current job and App files before starting a new import for the same selection.

Policy and limits

Strive rechecks the current App, owner, selected connection policy, and import permissions before finalization. An App deletion or ownership change can prevent completion even after some bytes were copied. Storage transfer limits and App ingestion limits both apply; passing one does not bypass the other.

Import only the documents needed for the task. For extraction, selecting an explicit source set makes it easier to understand which files contributed to a draft and which remained outside it.

Continue with document processing, table drafts, or storage job recovery.