26.11 Release notes
This release adds record versioning, evidence-based AI drafting, document-version submissions in workflows, formula-driven field updates, and new ways to register records, explore data and manage service accounts.
Feature highlights
AI features
Draft model documentation from record evidence
Use Draft Document or Draft Section to write from the record's fields, test results, metrics and attached files, including PDFs, code, notebooks and text files. Draft Document is available on development documents, and Draft Section also works on monitoring and custom document types. Add instructions and context, review each completed draft while the remaining sections are still being written, and insert only the content you accept. For empty sections, review the proposed content blocks before adding them.
Each accepted draft retains its generation history and sources. Evidence used shows what the text relies on, and Evidence reviewed shows what the agent inspected. Sources open in a preview. Drafts can include test tables and figures. When cited evidence changes, affected text is flagged for review, with options to update values or redraft. Instructions are remembered for each document or section. While a Draft Document run is in progress, My Inbox shows the run's progress, then tells you when the draft is ready for review or has failed.
Learn more: Draft documents with AI
Integrations
Manage service accounts for integrations
Customer Admin users can create a service account for an identity-provider application from Settings > Integrations > Service Accounts. The application signs in with its identity provider's client-credentials access token, and its service account belongs to one organization. Before an application can sign in with client credentials, an admin verifies the service account's client with Verify Client. Admins can disable or re-enable the account and rotate its ValidMind API key. Service accounts are marked in the User Directory.
Learn more: Manage service accounts, Configure service accounts
Inventory
Manage multiple versions of an inventory record
Create a new version of a record with a required reason and an optional label, browse its history and lineage, choose the Primary version, and archive versions that should remain read-only. Make another version Primary before archiving the current Primary. Each version has its own lifecycle, workflows and evidence. A new version starts with its record type's default documents, the same as a newly registered record, and doesn't copy the source version's documents. All versions of a record share its group and record type.
Inventory listings and record-level reporting use the Primary version. Artifact, activity and status-duration exports identify the record version they belong to, and interdependency views show the version each link targets. Version actions are recorded in activity and the audit log. The public API also supports listing, creating, promoting and archiving versions.
Learn more: Manage record versions
Register a record from a development document
In Register Model, choose Register from a Document and upload a development PDF. An agent uses the document to fill the record's fields and attaches the PDF. If a record with the same name already exists, choose whether to update it or register a new record.
Learn more: Register records in the inventory › Register records from a document
Import inventory records from CSV or Excel
Create inventory records in bulk from a CSV or Excel file. An agent proposes how your columns and values map to inventory fields, and you review and adjust the mapping before importing. If some rows are missing a required value, choose one value to use for those rows. To import through the API instead, use the bulk upload inventory records notebook. A companion notebook uploads artifacts the same way.
Learn more: Import records into the inventory
Explore a record's data and attachments
Open Data on a record to browse what has been logged or uploaded to it, whether or not it is placed in a document. Test Results shows each test's runs with their parameters, results and figures, Metrics shows values over time, and Attachments lists every file on the record, including document PDFs. From Attachments you can upload files, edit descriptions and remove files. Uploading a file with the same name as an existing one keeps both.
Learn more: View record data
Risk tiering
Assign risk tiers with ordered rules
Risk tier templates have a Rules calculation method for decision-tree and knock-out methodologies. Define named rules in priority order; the first matching rule sets the tier, with a default when none match. Each assessment shows which rule set its tier and why.
API compatibility: publishing an assessment requires a tier the platform can calculate. Complete the required assessment inputs before publishing. Fields used by a risk tier template cannot have their keys renamed, and changing override rules on a published template requires a new template version.
Learn more: Configure risk tier calculation › Set up a Rules template
Workflows
Calculate field values in workflow steps
A Set Field step can calculate a value with a formula when the workflow reaches it, such as setting a review end date to the start date plus 90 days. Use the same formula language as calculated fields, test a formula or the whole step against a record without saving values, and reorder assignments so later formulas can use earlier results.
Formulas are checked when you save the workflow. The run history and activity show the formula, inputs and outcome. When a formula fails, the step writes none of its fields, the workflow continues, and the roles chosen under If a Formula Fails, Notify get a task in My Inbox.
Steps containing only fixed values also validate every assignment before writing. If a value is invalid or a write fails, the step writes nothing and organization admins get a task in My Inbox. Existing steps with invalid values should be corrected before they run.
Learn more: Set field values with formulas
Submit saved document versions in workflows
Add a document selection to a User Action step so the assignee submits a saved version of a document of the required type. The completed step and the record's activity link to the submitted version, preserving which document was used at that point in the workflow.
Saving a document version also records its notes in activity, and the Saved Versions list refreshes when the new version is ready. Saved-version and document-submission events are available in the public events API and activity exports.
Learn more: Workflow step types › Document selections
Enhancements
AI features
Use GPT-6.1 Sol and GPT-6 Luna for AI features
AI features now use OpenAI's GPT-6.1 Sol for document drafting, Document Checker and the copilot, and GPT-6 Luna for quick tasks, replacing GPT-5.6. Organizations that chose a specific model in their AI settings keep it.
Activity
Export activity logs to CSV
Click Export on the Activity page, on a record's Activity page or on an artifact's Activity tab to download every event that matches your filters as a CSV file. Organization-wide exports of Record Activity and Settings Activity show how many events match before downloading and include up to the 10,000 most recent.
Announcements
Target announcements to selected roles
Choose one or more roles when creating an announcement so it reaches users holding at least one of those roles. Customer Admins also receive targeted announcements; leave Roles empty to reach everyone. Before deleting a role, review links to draft, scheduled and live announcements that target it.
Artifacts
Configure default fields for each artifact type
In Settings > Artifact Fields, configure whether each default field is enabled, shown on creation or required on creation for built-in and custom artifact types. The page lists which types use each field and warns about workflows that depend on a field before you disable it.
API compatibility: create requests must provide fields required by the artifact type, and create or update requests cannot set disabled fields. Update integrations and workflow inputs to follow the type's field settings.
Edit artifact type names and details
Admins can edit the name, description and slug of built-in and custom artifact types in Settings > Artifact Types. Changing a slug preserves role permissions on the type.
Attestations
Include artifact custom fields in attestation snapshots
Attestation snapshots show the custom fields that apply to each artifact type, subject to the viewer's field permissions. New snapshots include calculated and aggregate results, attachment counts are shown, and artifact CSV exports include custom-field columns.
Calculated fields
Recalculate calculated and aggregate fields on demand
Organization admins can use Recalculate Now from a field's row menu in Inventory Record Fields or Artifact Fields to refresh its values across records, instead of waiting for cached values to expire.
Document Checker
Explain Document Checker size failures
Failed checks show the stored failure reason, including when a PDF is too large to read or contains more figures than the AI model accepts. A check that assessed no questions is marked failed and cannot be published.
Integrations
Find MCP connection instructions on Getting Started
Each record's Getting Started page has a Connect to MCP section with the MCP URL, headers and a Claude Code configuration snippet prefilled with your API credentials.
Run Databricks tests from a record
Start your Databricks validation notebook from a record's Data page with Run tests now. An admin adds the Databricks Job ID to the Databricks connection, and ValidMind starts that Job through the Databricks Jobs API, passing the record's identifier to the notebook. The page shows the run's progress, links to the run in Databricks, and shows the notebook output when a run fails.
Inventory
Search listings from the toolbar
Inventory, Artifacts and Validation Issues have an always-visible search box. Choose a text column with Search by; your choice is saved. On Inventory, Display Cards/Table, Export and Import are grouped in the More menu.
Choose the order of registration fields
Admins can set the order of registration fields for each inventory record type. In Settings > Inventory Record Fields, click Reorder Registration Fields, select the record type, and drag its fields into order. Each record type's Register form uses its own order. A record type without a saved order keeps its existing field order.
Archive, delete and change the stage of several records at once
In a record's stage field, Archived and Deleted now sit below a divider at the end of the list, and both ask you to confirm. From the inventory list, admins can select several records and archive or delete them from the Actions menu, or change their stage with Bulk Edit.
Public API
Read record documents through the public API
API clients can list the documents on an inventory record, read a document's section and block structure by slug, and retrieve each content block's stored HTML. The endpoints are available under both /vm/api/v1 and /vm/api/latest.
Saved views
Set and manage default table views
Customer Admins can set an organization default view for Record and Artifact tables. Each user can override it with Set as My Default. Admins can edit organization views and field layouts regardless of who created them, and users with shared-view management access can edit the views they published. Changes to organization views and layouts are recorded in the audit log.
User management
Add organization-defined user profile fields
Customer Admins can define user fields such as Business Unit or Team in Settings > User Fields. Users fill in their own profile values, admins can edit them from user details, and the User Directory can show the fields as columns.
Invite users into multiple groups
Assign an invitee to several groups at once. The user joins those groups on first sign-in. The public API also supports inviting a user with multiple groups and adding an existing user to several groups in one call.
View the User Directory and manage role assignments
The User Directory is available to every user. Assigning or removing an existing role on a user, or marking a role as an admin role, requires a Customer Admin. Permissions for inviting users and for creating or deleting other roles are unchanged.
Workflows
Filter Global Workflows by artifact fields
Filter Global Workflows by artifact type, status, severity, owner and due date. Combine these with the existing Inventory and Workflow filters, preserve them in saved views and links, and export the filtered results to CSV.
Show valid drop targets in workflow field layouts
The workflow step editor highlights valid drop targets while dragging a field or field group, and marks places where the item cannot be dropped.
Branch workflows on default record fields
Condition branches in record and risk tier assessment workflows can now check default record fields, such as Tier, Assessed Risk Tier, Business Unit, Use Case, Is Vendor Model, Vendor Name and Stage, in addition to custom fields.
Bug fixes
Activity
Refresh activity after field changes
Record and artifact activity feeds show saved field changes without requiring a page reload.
Attestations
Send blocked attestation notices
Fixed missing email notices to Customer Admins when a scheduled attestation cannot start because another schedule for the same attestation is still active.
Calculated fields
Show calculated-field errors and respect type scope
Failed dependent formulas show their errors instead of appearing blank. Calculated fields are evaluated only for the record or artifact types they apply to, avoiding errors from unrelated fields.
Custom fields
Preserve calendar dates submitted through the API
Fixed date values submitted as timestamps appearing one day early. The app and exports now show the intended calendar day consistently for every viewer.
Fix errors when opening rich-text fields
Fixed a JavaScript error when opening rich-text fields on artifacts, such as remediation plans, and formatted custom fields.
Dashboards
Load dashboard widget options when the dialog opens
Fixed saved views and Analytics pages sometimes not appearing immediately when opening the Add Widget dialog.
Show every column in artifact dashboard widgets
Fixed dashboard widgets for artifact saved views missing columns, including custom fields of every artifact type and inventory record fields.
Document Checker
Keep Document Checker questions in assessment order
Document Checker results follow the assessment's question order, including exports and previously saved runs.
Document templates
Show starter templates for document types
Starter templates for new document types appear in the template list and can be selected when creating a document. Existing starter templates that were unavailable are restored where the organization has no other custom template to use.
Documents
Handle validation reports without guideline blocks
Validation reports without guideline blocks no longer show an empty guideline adherence bar, and Document Checker does not require evidence to be linked before checking them.
Forms
Mark required fields consistently
Required fields show a red asterisk, and values containing only spaces no longer count as filled in. Save and create actions are enabled when their required inputs are ready, and editing a GitLab connection preserves its instance URL.
Inventory
Allow permitted stakeholders to edit default record fields
Users with Update Model permission on a record can edit its default fields from the record page, including Name, ID, Tier, Purpose, Business Unit, Use Case and vendor fields.
Lists
Load invitations, override rules and attestations promptly
Fixed pending invitations, risk tier override rules and attestations sometimes appearing empty for up to 30 seconds after opening their page.
Notifications
Keep SMTP notification emails readable in dark mode
Fixed the message card in SMTP emails becoming difficult to read in Apple Mail dark mode.
Permissions
Apply organization and record access checks consistently
Saved-view filter names, document access, dependency links and artifact-type creation consistently follow organization boundaries and record permissions.
Search
Find command palette searches containing special characters
Fixed command palette searches containing & or # returning incorrect results.
Keep record search results current
Record search leaves out deleted artifacts and finds artifacts by title, even when they have no remediation plan.
Workflows
Keep workflow field editors consistent with field definitions
Fixed orphaned field keys remaining in step layouts after a custom field was renamed. Set Field and Create Artifact steps also preserve rich-text field templates when saving.
Select users for User fields in Set Field steps
Set Field steps use a user picker for custom User fields. Existing steps that stored a typed name show a notice and can be corrected by selecting a user.
Keep document selections valid when a workflow's record type changes
Changing a workflow's record type is refused when a User Action step asks for a document type the new record type doesn't have. The message names the step and the document selection to remove first.
Recover approvals with no remaining voters
When an approval has no remaining eligible voters, newly eligible users are added. If nobody can vote, organization admins and the record owner receive an Inbox notice explaining what needs attention.
Breaking changes
Public API
API responses follow field read permissions
Field read permissions apply to returned values on record and artifact pages, listings, CSV exports, filter options and public API responses. Files in hidden fields are also excluded from attachment listings and downloads, and AI drafting reads only fields and files available to the requesting user.
Integration action: ensure the integration's user has read access to every field it needs. Requests with a non-admin API key no longer return hidden values, and directly reading a restricted field returns HTTP 403. Fields with no read roles configured are readable only by admins.
Reject updates to read-only artifact fields
Artifact update requests that attempt to change read-only values, such as the record an artifact belongs to, return HTTP 400. Remove those fields from update payloads.
Read rich-text field settings from the supported location
Rich-text custom fields created through the API now render formatted content correctly, and existing fields are corrected automatically. API clients should read the supported richTextOptions value; clients that inspect raw settings must read settings.options rather than the former top-level settings keys.
Validate artifact schema requests before saving
Artifact field definitions require a valid typeId and a field key. Invalid types return HTTP 400 with INVALID_FIELD_TYPE, missing keys return MISSING_FIELD, and full schema replacement requires a settings map or returns INVALID_FIELD. Update schema-writing integrations to provide these values.
Documentation
Python library
Find the individual-tests documentation quickstart
The notebook catalog includes a quickstart for documenting a model by running and logging individual tests without applying a document template.
Customer-managed deployments
Fix PDF uploads, downloads and conversion with configured settings
Fixed PDF upload and download failures caused by configuration value types, including after settings were viewed in the admin application. PDF conversion also works when the LiteLLM proxy is configured through the configuration file.