Veeva Vault

Connecting DASH to Veeva Vault archives a copy of each submitted certificate (and its documents) into your Vault, giving you a controlled, auditable record alongside your other GxP content. You set this up as a Storage channel (CHANNEL-003) with the connector type Veeva on the Material. Storage pushes happen automatically after a certificate is submitted.

Before you start

• You need the Materials permission and an active (non-trial) subscription — see Roles & permissions.
• Get your Vault URL, a service username and password, and the document metadata Vault expects (document type, subtype, lifecycle and classification) from your Vault administrator.
• The channel lives inside a Material — open Materials and choose one, or create a Material first.

What you need from your Vault administrator

Detail	Notes
Vault URL	The base address of your Vault instance
Username & password	A service account with permission to create documents (the password is masked as •••••••• after saving)
Document type / subtype	For example Operations / Certificate
Lifecycle	For example Draft to Approved
Classification	For example Internal
Folder path (optional)	Where uploaded certificates should land

Ask for a dedicated service account rather than a personal login — it keeps the archive working if a person leaves and keeps the audit trail clean.

Configure the Veeva Vault channel

1. Open the Material and go to the Data channels section.
2. Add a channel with direction Storage and connector type Veeva.
3. Name it clearly, for example Veeva Vault archive.
4. Enter the Vault URL, username and password.
5. Set the document type, subtype, lifecycle and classification to match your Vault’s configuration, plus a folder path if you use one.
6. Save the channel.

Storage is archival, not the destination

A storage channel keeps a copy for your records — it does not replace the submission channel that delivers the certificate to its recipient. You can add Veeva Vault alongside any submission channel on the same Material.

Test the connection

Use Test connection. DASH authenticates against Vault and reports:

• Pass — “Veeva Vault authentication successful.”
• Fail — “Missing Veeva Vault URL, username, or password.” means a field is blank; “Veeva Vault authentication failed — check vault URL and credentials.” means the URL or login is wrong.

Common pitfalls

• Trailing slash or wrong URL. Double-check the Vault URL — a small typo fails authentication.
• Password shows as •••••••• when editing. That’s expected. Leave the placeholder to keep the stored password; only overtype it to change it.
• Metadata mismatch. If the document type, subtype or lifecycle you enter doesn’t exist in Vault, the upload can fail even though the login worked. Confirm the exact values with your Vault admin.
• A storage push failing does not fail the submission. Storage pushes are best-effort — the certificate still submits, but the failed push is recorded. Check the certificate’s transmission detail if a copy doesn’t appear in Vault.

Related

• Storage channels
• Credentials & testing
• SharePoint
• AWS S3
• Data channel troubleshooting