An AI conversation may look like one thread on screen, but its useful record can span prompts, answers, generated images, citations and links to changing Workspace files. Google Vault can now export more of that context. Records and legal teams still need to preserve the pieces as one traceable package rather than treating a JSON file as the finished case record.
What Google released
On 22 October 2026, Google announced filtered Vault exports for Gemini in Workspace. Administrators can search conversations by custodian or organisational unit—up to 5,000 users—and date range with a selected time zone. Matching histories can be exported as JSON through the Vault interface; Google says API support will arrive within 14 days of the interface rollout.
The export can include the user's prompts, AI responses, generated attachments such as images, citations and links to referenced Workspace items such as Drive files or Gmail threads. It covers Gemini conversations created in Gmail, Drive, Docs, Sheets, Slides and Meet when conversation history was turned on.
Build a reviewable evidence package
1. Record the scope before exporting. Note the matter or request, authorised custodians, organisational units, date range, time zone and operator. A narrow, documented query is easier to explain than a broad collection with no stated purpose.
2. Preserve the downloaded original. Keep the original export and its folder structure unchanged in an access-controlled location. Work from a copy. If organisational procedure requires a cryptographic digest or evidence log, create it at collection time and record the tool and algorithm used.
3. Reconcile every component. Review the JSON alongside generated attachments. Treat referenced-file links as pointers, not as proof that the linked content is preserved: permissions, content and availability can change. Follow the organisation's authorised legal or records process to collect any referenced source file that belongs in the package.
4. Make a readable working copy. JSON is useful to software but awkward for many reviewers. Create a separate table or report that keeps prompt-and-response order, timestamps and attachment references together. Label it as a derived review copy and retain the original JSON. Do not silently rewrite an AI answer or remove an inconvenient exchange.
5. Check completeness and errors. Compare exported counts, expected custodians and date boundaries. Record missing attachments, inaccessible references, export errors and any conversation known to be outside scope. A successful download only proves that an export completed; it does not prove the search was legally sufficient or captured material that was never retained.
6. Prepare a static handoff deliberately. If a PDF copy is needed, show the query scope, time zone, source filenames and creation date. Visually inspect page breaks, long prompts, tables, links and image captions. Keep the PDF beside—not instead of—the original machine-readable package.
Important limits
Google says the feature only captures conversations created while conversation history was on. There is no end-user setting for the Vault export itself, and availability depends on an eligible Workspace edition or Vault add-on. Most importantly, Google says additional Workspace-Gemini governance features, including retention rules and litigation holds, will follow in future releases. This export should not be presented as a complete retention or hold solution.
FileStation does not connect to Vault, collect Workspace evidence or certify completeness. For a non-sensitive sample or an authorised working copy, JSON Formatter and CSV Tools can help inspect structure locally in the browser. If an approved process has produced a PDF review copy, use PDF Reader for a page-by-page visual check. Follow your organisation's legal, privacy and security requirements.
The durable record is not just the chat text. It is the documented scope, untouched export, linked materials, review copy and an honest account of anything that could not be captured.
Primary sources: Google Workspace Updates, 22 October 2026 and Google Vault export contents documentation.