Keep files and versions identifiable
Preserve the source behind later comparisons and reviews.
Vault files and versioned records have different roles. Keep working documents editable while using explicit versions for the inputs behind results.
Update a Dataset deliberately
Use Update data to create a version of the existing Dataset. Dropping files onto a detail page adds another item; it does not silently replace that Dataset’s data.
Labelling drafts keep the Dataset identity. Save version publishes validated labels and retains earlier versions and results. Dataset inputs and Ground Truth have their own versions.
Retain the Model configuration
The Model’s execution settings, including output interpretation, belong to its versioned configuration. Select the intended Dataset and source versions when preparing a Run.
Work with documents
Vault → Add → Document and Chat → New document create the same kind of saved Vault file. The Preview/Source reader lets you read it, select a passage, and use Add to chat to request an edit.
Desktop provides Open in Editor for local working files; browser and Team views provide Download. Refresh the reader after external changes.
Reports and decisions retain their saved basis rather than adopting later working-file edits.