Read this procedure from Vault and draft a checklist for our review.
Neil
- I’ll work from the selected document capture, keep its version reference and flag anything the procedure leaves unclear.
- Reads
Selected steady-state document- Returns
- Requirements from the procedure
- Document and version references
- Questions for the process owner
1What’s connected.
Connect Vault once for your company and share an automatically updated document collection with selected Seal groups. Employees find documents in search and @ mentions without connecting their own Vault account. Optional text copying lets them read in Seal and use excerpts with Neil; editing stays in Vault. Personal Vault AI actions are set up separately in Settings → Neil → Integrations.
Connection setup and permissions
The organisation library shares captured versions of selected steady-state documents with your chosen Seal groups. Optional text copying lets Neil read supported document content through @ references.
For actions exposed by Vault AI, connect your personal Vault account in Settings → Neil → Integrations. Your administrator enables the available agent actions and API access; each call requires approval.
Broader document and record operations can be implemented through a scoped Vault API integration. These are separate from the organisation library and depend on your Vault applications, permissions and configured actions.
Set up Veeva Vault
- Open Settings → Integrations → Veeva Vault. Test and connect using your Vault URL and an API access token for a dedicated integration account.
- Choose document types and preview the automatic collection. Select the Seal groups that may read it and decide whether to copy document text.
- Enable sync and wait for the complete collection to publish. New matching steady-state documents join automatically; check progress and connection health in Integrations. Original Vault links still require a Vault login.
2Connect in Seal.
Sign in to Seal and open Settings → Integrations. An organisation admin can review the connection and complete the guided setup.
3Custom Vault API implementation.
The following are examples to scope and set up per project using the Vault API, separate from the organisation library. Availability depends on your Vault applications and permissions; agree and test each read or write action before use.
- Find the relevant records
- Query permitted object records and document metadata with VQL. Collect the selected records, not an unrestricted copy of the Vault.
- Compare procedure versions
- Retrieve selected document versions and their text to draft an account of what changed and which work may be affected.
- Collect supporting evidence
- Retrieve accessible source files, renditions and attachments. Preserve document and version identifiers in the report.
- Follow the relationships
- Use configured document and object relationships to connect an event with its procedure, product and supporting evidence.
- Investigate deviations and CAPAs
- Read the permitted QMS objects and combine them with ERP, lab or manufacturing records to prepare an investigation draft.
- Review workflow progress
- Use accessible workflow information to identify outstanding work and assemble a follow-up brief.
- Inspect record history
- Retrieve the permitted document or object audit history to reconstruct changes around an event.
- Prepare documents and record updates
- Draft a report or proposed field changes. Where authorised write actions are implemented, create or update the selected records; lifecycle approvals and personal signatures remain separate.
4Connection questions
Does the organisation library include all Vault API operations?
No. The library shares selected steady-state document captures. Vault AI actions and custom API operations have their own configuration, permissions and approval requirements.
Can Neil investigate across Vault and our ERP or LIMS?
Yes, once the required connections and read permissions are configured. Define the record scope and matching identifiers, then ask Neil to assemble the evidence, identify gaps and draft a referenced report.
5Before it goes live.
Access
The organisation library reads only; it makes no changes in Veeva Vault. Define which records are shared and which Seal groups can read them.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.