Document Lifecycle
How documents move from upload or provider import through validation, automation, and publication.
A TextMine document usually moves through a repeatable lifecycle.
1. Ingest
Create a document by uploading file bytes directly to Vault or by importing from a connected provider. Provider imports are useful when files already live in systems such as Google Drive, SharePoint, Notion, or other configured sources.
2. Classify and process
Vault assigns or confirms a document type, extracts default fields, applies relevant tags, and makes the document searchable. Custom metadata and review fields can be added for organisation-specific data.
3. Review and validate
Users, agents, reports, or playbooks can review extracted data and evidence. Workflows can assign reviewers, request approvals, send notifications, or wait for processing milestones.
4. Automate downstream work
Processed documents can feed reports, records, Scribe templates, business graphs, alerts, exports, and external systems through integrations or webhooks.
5. Publish when validated
When a document should become part of the validated team archive, publish it from Vault to Legislate. Legislate is the archive view for published team documents, while Vault remains the surface for active processing and analysis.