Skip to content

Connecting to a Vault

The vault plugin's login skill signs Claude into a Vault, classifies the target as production or sandbox, and reads its application family and API version. Every other skill uses this information to answer accurately for your specific Vault.

Have the following in place before connecting Claude Plugins to a Vault:

  • The vault plugin is installed. See Installation.
  • The Vault CLI is recommended. See Installation. If not installed, the skill uses the documented Vault API directly.
  • You know your sign-in method for the target Vault (SSO, API access token, or password).

Tell Claude which Vault to connect to:

Sign in to my Vault. acme-quality.veevavault.com.

Claude will ask how you sign in to that Vault (SSO, API access token, or password) and give you the appropriate vault login command to run.

After sign-in, Claude:

  1. Reads the environment type from domain_type__v (PRODUCTION, SANDBOX, DEMO, TEST, or UNKNOWN).
  2. Reads the application family and applications with include_application=true.
  3. Reads the maximum API version from GET /api/.
  4. States the profile once. For example: "acme-quality.veevavault.com, SANDBOX, Quality".

Profile Persists Across the Session

Section link for Profile Persists Across the Session

The application family and applications never change for a Vault and Claude remembers them for the rest of the session. The environment type is re-read live before any write. The API version is re-read if a call is rejected for its version.

To switch to a different Vault, tell Claude the new DNS:

Connect to my production Vault. acme-quality-prod.veevavault.com.

Claude re-reads the classification and profile for the new Vault before any work continues.

With a Vault connected, the Plugin Reference lists all skills available across the Veeva Claude Plugin ecosystem.