Skip to main content
This is a draft of the planned transfer workflow, not a verified procedure you can complete today. The current source marks upload-to-artefact import as not built. The supported bundle format, destination import controls, provenance checks, and availability must be confirmed against the release build before publication.
Use this route when you want a selected Arc output, such as a collection plan, to become a separate artefact in a Vantage workspace. The specified route is to download the selected artefact and upload it into the destination. It is not a live link between the two products.

​
Prepare the source and destination

You need access to export the source artefact and permission to create an artefact in the destination workspace. The destination audience must be authorised to receive the content, and the content’s security classification must be compatible with the destination. Inspect the exact source version and its supporting assets before transfer. Follow Create, revise, and export a chat artefact to prepare it. Keep source references and unresolved questions intact. For a collection plan, decide which workspace will use it and which purpose, questions, and collection scope belong in that workspace’s description. Obtain any approval required for the plan before describing it as approved.

​
Planned transfer procedure

The following steps describe the required experience once artefact import is available. A normal file upload does not establish that this procedure has completed.
  1. Select the saved Arc artefact version you want to transfer. Do not rely on an uncommitted editing draft.
  2. Download it through the supported transfer route, including its source and required assets. Keep the version’s provenance and security classification with the transfer.
  3. In the intended Vantage workspace, explicitly import the supported content as an artefact. The operation must check source and destination permissions and whether the destination audience can receive the content.
  4. Open the newly created destination artefact. Check its content, supporting assets, source-version provenance, classification, and destination ownership.
  5. Compare it with the selected Arc version before using it in workspace work. Treat missing assets or unverifiable provenance as an incomplete transfer, not a successful import.
Do not substitute a reference attachment or an ordinary source-file upload for artefact import. Uploaded content becomes an artefact only through the explicit supported operation.

​
What transfers and what stays separate

Copying or importing content does not lower its security classification. A source reference also does not grant a workspace reader access to the original conversation.

​
Use the plan in the workspace

The workspace description can record the purpose, research questions, and collection scope agreed in the collection plan. Configuring that scope and importing the selected artefact are separate parts of setting up the workspace. Import is not a publication action. The wider shared workspace review capability and publication receipts remain planned, as does Explorer’s output/review route. Existing workflow Verdict and Publish steps are a separate implementation; do not assume import automatically creates a review item or starts that workflow. Where review is required, approve the exact version and use an approval-only publication path. A changed version does not inherit an earlier decision. Do not assume that the transfer has collected data, attached datasets, or authorised an ingestion job. Those operations need their own configuration and access checks.

​
Check the result

A completed transfer should give you a separate workspace artefact containing the selected content and its required assets, with verifiable source-version provenance and preserved classification. It should not expose the source chat or project. Until the explicit import route is available and verified, keep the selected Arc version and treat the transfer as unfinished. Do not label an ordinary workspace upload as an imported artefact. For the wider access boundaries, see Understand project sharing boundaries and What carries over.