Processing workspaces

Create and open a workspace

An organization owner or manager can create a workspace from the Workspaces page. Each workspace supports the Resume document type. All Documents contains its uploads; Workflow, Integrations and Permissions configure how they are processed and accessed.

Choose your returned fields

Open Resume to enable fields, rename their labels and configure validation. Save before processing. The configured response contains enabled values in projection.data, keyed by the stable field IDs shown in the Schema tab. Download that schema when integrating the response. Source evidence remains available separately in the canonical result review.

Processing and review

Selecting a file previews it locally. Process document submits it using the saved configuration. Native parsing costs 1 credit; OCR costs 3 credits. The server also applies your organization’s upload, access and quota policies.

Workflow offers automatic, skipped, partial and full OCR. Page splitting processes each page independently; leave it off for a resume spanning multiple pages. Unsupported file and workflow combinations return an error or a warning rather than silently discarding content.

Validation checks configured fields and rules. Automatic confirmation requires the rules to pass. Allow failed validation permits a reviewer to accept failing rules, but cannot make a failed parse successful. Each document retains the configuration used when it was processed.

Reference documents

Enable Model memory in Workflow, then add a manually confirmed document from the Model Memory tab. References retain reviewed values and exact evidence. A reference cannot supply unsupported facts to another resume. Adding a reference does not train or fine-tune an external model.

Exports and integrations

Add JSON or CSV exports in Integrations to download selected fields from a document. Connect an active organization webhook subscribed to parse.completed for supported completion deliveries. Manage endpoints and their signing secrets from Developers.

CVault does not provision an inbound email address or third-party connector credentials from this screen. External automation can use the documented API. Console document endpoints require an authenticated, same-origin browser session.

Access and retries

Organization access includes your organization’s members. Restricted access includes selected members and organization owners and managers. Archived workspaces leave the list without deleting stored documents. Concurrent configuration changes return a conflict so that an older save cannot overwrite a newer one.

For document submission retries, retain the original idempotency key and payload. Reusing a key for different content or settings returns a conflict. An in-progress retry returns the existing document rather than starting another parse.

Use a workspace through the API

Copy the workspace ID from Resume settings. Send parser_workspace_id with your multipart parse request or JSON upload-session request. The API validates access and saves the configuration revision with the job, so later settings changes do not change that job’s response.

Read the completed job’s results to receive an additive workspace_result containing projection.data, selected evidence, validation and review status. That results read also saves the workspace document. If it returns 503 parser_workspace_persistence_unavailable, retry the read; do not submit the file again. The original canonical result remains available through the job. A persisted workspace document is a separate copy: job erasure does not establish deletion of that saved document, exported data or receiver copies. Manage their lifecycle separately.