Vault Owners

Vault Owners can access all areas of the application and perform Vault-level configuration tasks.

The topics below will help Vault Owners, and users in similar roles, get started using Vault :

Assigning Review Plans to Sites

With Targeted SDV (Source Data Verification) and DMR (Data Management Review), your organization can define SDV or DMR requirements for a subject in a Review Plan. Targeted SDV and DMR are extremely flexible and support varying review requirements across Items at the Form level. You can also configure Targeted SDV or DMR for some Forms to be very granular, drilling down to a specific Item Group and Item combination.

Managing Study User Access in EDC Tools

This article describes how to manage an EDC user’s access to Studies and study-related data.

About Studio

Vault EDC contains a study design and management interface, EDC Studio, to enhance the experience of clinical programmers as they design their studies. Using Studio, clinical programmers can quickly create studies and manage study amendments for their organizations.

Working with Casebook Versions in Studio

When you need to make changes to your study, for example, due to a study amendment or issue, you can use Vault EDC’s casebook versioning feature to manage changes. Vault EDC uses the most recent, published casebook version when you create a new subject casebook.

Comparing Casebook Versions

You can run a report to show the differences between two Casebook Definitions or two Casebook Definition versions. This illustrates added, removed, and changed design components. You can also compare two different versions across two different vaults.

Configuring Cycles (Repeating Event Groups)

Vault EDC supports repeating Event Groups, which you can use to implement cycles in your study design. Each new repeating Event Group is a sequence. Data entry users can create new sequences of a repeating Event Group (up to a configured Repeat Maximum) and enter data in the contained Forms.

Configuring Repeating Forms & Item Groups

Vault EDC supports repeating Forms and Item Groups, which you can use to collect the same set of data multiple times within a single Event. Each new repeating Form or Item Group is a sequence. Data entry users can create new sequences of repeating Forms and Item Groups (up to a configured Repeat Maximum) and enter data within.

Designing a Study in Studio

You can use EDC Studio to design and amend your study. In Studio, you can create both object definitions and your study’s schedule in a simple, drag and drop design interface.

Enabling Forms for Coding

You can easily identify coding Forms and configure them in Studio for clinical coders to code form data within Vault Coder.

About the Properties Panel

In EDC Studio, you can use the Properties panel to manage your object definitions. The fields available in the Properties panel depend on which type of object or definition you’re editing.

Publishing Validation Errors & Warnings

See the information below for help troubleshooting errors and warnings that occur when validating a casebook version:

Rule Design Properties

In EDC Studio, you can use the Properties panel to manage your object definitions. The fields available in the Properties panel depend on which type of object or definition you’re editing.

Defining Rules in Studio (V1)

You can create data validation rules by using the rules engine to validate data in Vault EDC. Vault can then perform certain tasks based on the evaluation of the rule:

Creating Rules in Studio

You can create data validation rules by using the rules engine to validate data in Vault EDC. Vault can then perform certain tasks based on the evaluation of the rule:

Managing Studies & Study Settings

When preparing to build your study design, you must first create an Organization and a Study. The Organization object record groups Studies within that organization together. A Study object record represents a single study. You’ll need to create a new Study object record for each Study you run in Vault CDMS. Note that your selections within Studio > Settings, including the Signature Definition, are not versioned.

Configuring Reasons for Change

You can specify the options for any dialog that uses a Reason for Change. Vault EDC stores these values in the Change Reason Configuration object (change_reason_config__v). Each Change Reason Configuration object record represents a value in the Reason for Change drop-down menu. Users select from the Reason for Change drop-down in the Intentionally Left Blank, Did Not Occur, and Change Reason dialogs.

Configuring Signature Definitions in Business Admin

In order for your Investigators to provide eSignatures, you must configure a Signature Definition object record related to your Study.

Creating a Review Plan

With Targeted SDV (Source Data Verification) and DMR (Data Management Review), you can define SDV or DMR requirements for a subject in a Review Plan. Targeted SDV and DMR are extremely flexible and support varying review requirements across Items at the Form level. You can also configure Targeted SDV or DMR for some Forms to be very granular, drilling down to a specific Item Group and Item combination.

Creating Review State Definitions for Event Dates

Vault uses Review State Definitions to map Event Dates to an SDV or DMR Review Plan, allow data entry users to provide electronic signatures for Event Dates, and allow data review users to freeze or lock Event Dates. To allow for these types of reviews on Event Dates, you must have one Review State Definition for each Study.

Creating Study Specifications

With Vault EDC Studio, you can easily generate study documentation at any point in the design process. In the current release, there are three types of study specifications available: an All CRF PDF, a Unique CRF PDF, and an SDS, or Study Design Specification (Excel™).

About Templates & Object Reuse

When designing a study in EDC Studio, you can use templates or existing Study definition objects.

Defining Default Units & Conversions

Vault EDC uses whichever Unit Definition Item  you select as the default for that particular unit. For all other Unit Definition Items  in that unit, you must define a Unit Conversion.

Study Update Restrictions

After you publish the initial version of your Casebook Definition, Vault prevents you from making certain changes in any later versions you may create. If you were to make these changes, it could cause errors during the casebook amendment process.

Clinical Data Transformation & Extraction

Vault EDC supports not only the collection of clinical data, but also the transformation and extraction of that data into a usable format. Vault EDC uses the view functionality set to support this use case.

Common View Configuration Details

This article contains explanations about some common View Definition configurations. With the “Mapping Adverse Events” example, you can see an overview of an end-to-end view configuration. Following that example, you can review explanations of different issues that may arise with referencing repeating Forms and Item Groups in your view.

Creating Views in Studio

From Studio, you can create View Definitions, which Vault EDC uses alongside the Data Export job to export Study data into a readable CSV format. View Set Definitions are groups of View Definitions. A “view” represents a dataset for export to an analytics system, or to use for reporting. Each View Definition is a CSV within the View Set Definition’s ZIP file.

Managing Views in Studio

View Sets are a method of preparing clinical data for export from Vault EDC. Vault EDC uses Views and View Sets alongside the Data Export job to export Study data into a readable CSV format. A “view” represents a data set for export for use in an external reporting or analytics system.

About Report Types

Report Type determines the “reporting objects” for the new report. For example, Product with Study means that your report looks at Product and Study records.

Configuring Report Types

Report types define what an individual ”record” is in a report, for example, a document, a product, or a specific instance of a workflow. The report type also affects what fields are available as report columns, filters, etc. When a user creates a new report, the first step is selecting a report type for it.

Managing Report Export Cover Pages

Vault auto-generates report export cover pages and attaches them to PDF exports of reports. By editing the default Report Export Cover Page template, you can change the information that appears on these pages.

Reporting Configuration & Permissions

In 18R1, we updated Vault’s reporting capabilities to make it easier for customers to organize reports across their vaults. Changes include:

Administration in Vault EDC

Vault EDC users with the Vault Owner security profile, or a custom security profile with the appropriate permissions, can leverage the Vault platform for configuration and user administration tasks. 

Formula Reference Guide (V1)

See the tables below for details about available functions and operators, date formats, and number formats in the Vault CDMS formula and expression grammar.

About Vault Provisioning

Your organization can submit a request to clone, refresh, or delete a vault by filing a Veeva Support ticket. Veeva responds to these requests within 24 hours from the time we receive the request, according to our SLA. We perform all provisioning using the Vault Management Console, which is a validated tool.

Configuring Custom Tabs

Custom tabs allow you to organize and expand the primary navigation bar, providing users with quick access to object records or external sites. 

Configuring Login Messages

Login messages appear in a dialog for every user who logs into Vault. A login message can be useful for displaying a corporate privacy policy, a “Safe Harbor” message, or other informative messages. You must be an Admin with the correct permissions to configure these messages.

Managing Custom Help & Support

The Help & Support page is available to every user from the menu in the upper right of Vault. Vault allows you to replace the Support information on this page to provide vault- and organization-specific information.

About Configuration Mode

Configuration Mode allows you to lock non-Admin users out of a vault in order to complete certain configurations. Users with the Vault Owner or System Admin security profile can continue to work in the vault through the UI and the API. This setting is ideal for deploying configuration migration packages or setting up Dynamic Access Control.

Component Types

Configuration Migration Packages and other Vault features refer to certain elements of a vault’s configuration as component types.

Configuration Migration Errors & Warnings

See the information below for help troubleshooting errors and warnings that occur when deploying configuration migration packages.

Generating Vault Configuration Reports

With Vault Configuration Reports, you can generate an Excel™ report containing configuration information, including the Configuration Migration Package components and reference data used by components, for a vault. This feature is useful for tracking and documenting a vault’s configuration before and after any configuration projects. 

Using Configuration Migration Packages

Using Configuration Migration Packages, you can migrate configuration changes between two vaults. This feature is particularly useful when your organization needs to configure and test in a sandbox vault, and then move those configurations into a production vault. In this example, you’d create and export an outbound package on the sandbox vault and then import, review, and deploy the package on the production vault.

Using Vault Compare

Vault Compare allows you to compare the configuration of two vaults. This can be helpful when building a configuration migration package or validating that environments are synchronized after package deployment.

About the Vault API

Veeva Vault provides a simple, powerful, and secure API (application programming interface) that allows software programmers to write scripts and programs to interact and integrate with Veeva Vault. Using Veeva Vault API, your organization can build tools to import, update, and retrieve documents or object records. Veeva Vault API respects all the same business and access control roles as the Vault UI.

Granting Veeva Support Access to your Vault

When you need assistance from Veeva Support, it can be useful for them to see your vault from your users’ perspective. This feature allows an Admin to grant access to a vault, through a specific user’s account, for a set period of time.

Managing Job Instances & Viewing Job Status

Vault allows you to monitor scheduled, in-progress, and completed job instances, and also to take various actions on scheduled and in-progress instances.

About Object Lifecycles

Object lifecycles are the sequences of states (In Review, Approved, etc.) that an object record can go through during its life. A lifecycle must have at least two states, but it can have more if needed. Not all objects use lifecycles. Objects without lifecycles simply have a status of Active or Inactive. For objects that do use lifecycles, each state is tied to one of these statuses.

About Object Workflows

A workflow is a series of steps configured in Vault to align with specific business processes. These steps are actions that occur on or in relation to an individual object record. The different step types offer a flexible way to organize a wide variety of processes for an object record: assigning tasks to users, sending notifications, and changing a record’s lifecycle state. Workflow tasks can serve several purposes: they allow users to choose verdicts (approve, reject, etc.), choose reasons for the verdicts, and update object field values.

Configuring Object Lifecycles

Object lifecycles are the sequences of states (In Review, Approved, etc.) that an object record can go through during its life. An object lifecycle must have at least two states but can have up to 100 if needed. Not all objects use lifecycles. Objects without lifecycles simply have a status of Active or Inactive. For objects that do use lifecycles, each state is tied to one of these statuses.

Configuring Object Workflows

Object workflows apply to a single object lifecycle and a single object. To set up an object workflow, you’ll need to complete several steps:

Adding & Managing Object Lifecycle Roles

When you create a new object lifecycle, you can add custom application roles to an object lifecycle as well as edit role permissions. Vault automatically associates the standard Editor, Consumer, and Owner roles with the object lifecycle. You don’t have to associate an object with a lifecycle to view or add roles.

Setting Fields with Formulas

You can set fields using formulas through the Update Record Field object lifecycle state entry action and object workflow step. These options enable you to set the value of an object field using an Excel™-like formula language. The language includes functions and operators that allow you to calculate dates and text strings, as well as numbers. 

Using Object Workflows

This article explains how to start a workflow, manage an in-progress workflow, and complete tasks as a workflow participant. 

About Language & Region Settings

Vault’s UI can appear in different languages based on an individual user’s preferred language. As part of supporting a UI language, Vault localizes all non-configurable, or static text that appears in the UI (menu items, error codes, etc.) Vault also provides tools for Admins to specify translations for any configurable object in the system (field labels, user messages, picklist values, etc.). Admins can enter translations individually through the Admin configuration pages or can add or update multiple translations at once using one of the bulk translation tools.

Managing Audit Export Cover Pages

Vault auto-generates audit export cover pages and attaches them to PDF exports for all audit logs. By modifying the default Audit Export Cover Page template, you can modify the information that appears on these pages.

Viewing Admin Logs

From the Logs area (Admin > Logs), you can view a history of actions within your vault. There are multiple pages in this area, each of which displays the history for a distinct type of action.

About User References

Although User is not an object like Product or Study, Vault allows Admins to create special object fields that reference User object. When selecting from these fields, you see all active users in the vault. Domain users who are not part of the current vault don’t appear in the selection menu.

About Vault EDC Objects

Vault “objects” are part of the application data model. The application data model is a critical part of what makes each Vault application unique. It provides contextual information that drives the business processes in each Vault application.

About Vault Objects

Vault “objects” are part of the application data model. It provides context information that drives the business processes in Vault.

Defining User Actions for Objects

Object user actions are configurable instances of a Vault Action that you can define for an object and object types. By defining user actions for an object, you allow users to perform those actions on that object. Once configured, object user actions appear in the Actions menu for the applicable object record.

Using Bulk Object Record Actions

You can use the bulk editing options to make changes on up to 1,000 object records at once. You can edit object record field values, delete object records, or change the state of object records that are in object lifecycles.

Configuring Custom Sharing Rules for Objects

Custom Sharing Rules is part of Dynamic Access Control for object records. When using Custom Sharing Rules (rather than Matching Sharing Rules) for an object, Vault manages users’ roles on specific object records by matching rule criteria to specific user assignments. For example, on Product records where the Product Family _is _Veepharm Products, Gladys is an Editor and Thomas is an Owner.

Configuring Object Page Layouts

Object page layouts control the information displayed in the object record detail page. The layout applies in create, edit, or view mode. Objects that include multiple object types can use a different layout for each type. 

Configuring Vault Objects

Vault allows you to easily customize and extend your application data model by modifying standard objects, creating custom objects, and configuring object relationships. 

Copying Object Records

Copying records provides significant time savings, allowing you to quickly create a large number of similar object records. When copying from objects with child or grandchild relationships, you can often choose to copy the entire hierarchy of records. Copying a single record is sometimes referred to as “shallow” copying, whereas copying a structure of related records is called “deep” copy.

Defining Web Actions

Admins may add web actions (formerly known as “custom actions”) to the object record Actions menu. Web actions can invoke context-sensitive business logic or integrate with external systems and web sites. For example, create a web action to:

Setting Object Field Defaults

You can use field defaults to set the value of an object field using an Excel™-like formula language. Field defaults calculate the field value based on a formula you create. Literal value defaults enter the exact value in the field. Vault either assigns the default value upon save (formula default) or upon record creation (literal value default). Some example uses include:

Configuring Formula Fields on Objects

A Formula field calculates field value based on a Formula entered during field configuration. This allows Admins to derive a field’s value based on other data automatically. Formula fields are never editable; they simply display the calculated value.

Using Inline Grid Editing

Inline editing allows you to update values in a grid much like you would in an Excel™ spreadsheet. In Vault, inline editing supports various keyboard shortcuts which allow you to quickly edit multiple records or multiple fields within a record.

Managing Object eSignatures

eSignatures provide a way for users to complete tasks and sign electronic records. You can enable eSignatures on an object to capture relevant details, including the Signature Name, Signature Time, and Signature Meaning, in a related list on the object record detail page. Vault captures these details when a user provides an eSignature through an object workflow.

Managing Object Records

Each vault has a data model consisting of objects, their fields, and their relationships. Object records are pieces of data within this model.

About Object Relationships

With Vault Objects, you can configure various relationships, including parent-child (hierarchical) and reference (non-hierarchical) relationships. Reference relationships can point to another object or back to the same object (self-referencing). Parent-child relationships are typically one-to-one or one-to-many, but you can create a many-to-many relationship by using a third object.

Setting Up Object Types

An object type is a collection of fields that are grouped to capture similar but not identical data within a single object. For example, the Product object could include two types: Pharmaceutical and Medical Device. These object types share fields like Abbreviation and Internal Name, but each also has data specific to its business purpose like Dosage for Pharmaceutical and Model No for Medical Device.

Creating Page Links

With page links, Admins can create links that navigate users to custom page destinations. Page links are useful when Admins or users want custom object details pages, as opposed to Vault’s standard object details page. For example, an Admin may want to create a custom user interface for simplifying data entry into a Vault object for tracking Events.

About System-Managed Object Record Names

You can configure Vault to automatically populate and manage the standard name__v field on any custom object.

Viewing Object Records

You can work with object records from Admin > Business Admin. Some vaults also include object tabs that allow access to records outside the Admin area.

Managing Picklists

The Picklists page allows you to manage the values that appear in your vault’s picklist fields and the order in which they appear.

Configuring Hide User Information

Hide User Information is a method of protecting your users’ identities. With Hide User Information, you can configure your vault to prevent unauthorized users from viewing user names and identifying details. This hide action only applies to users whose email address has a different domain. See About Hide User Information for details.

Configuring Matching Sharing Rules for Objects

Matching Sharing Rules are part of Dynamic Access Control for objects. These rules allow assignment of users to Auto Managed groups and dynamic assignment of those groups to roles on specific object records.

Configuring Single Sign-On

Only Domain Administrators with the SSO Settings: Read and SSO Settings: Edit permissions in their security profile can view and configure SSO settings for a domain. SSO enablement and configuration applies across all vaults in a multi-vault domain.

Configuring User Role Constraints

This feature supports large or global implementations of Dynamic Access Control, specifically where an organization wants to delegate maintenance of User Role Setup records to local users. In organizations without this setup, we recommend using Dynamic Access Control and Matching Sharing Rules without User Role Constraints. 

Creating & Managing Users

This article explains how to manage user accounts in a vault. Note that user accounts exist at the domain level, so in multi-vault domains, user details are shared across vaults.

Cross-Domain Users & Authentication

In Vault, user accounts exist within a single domain. By setting up cross-domain users, Admins can grant a user access to vaults on a different domain without creating a new user account. For example, Admins in VeePharm’s vault could set up CTMS users as cross-domain users. These users would exist in their CTMS vault, which would be on their “home” domain, but would also be able to access the CDMS vault on the VeePharm domain in order to view casebooks. For groups that work with many different companies, this saves users from having to manage several different Vault login accounts.

About Delegated Authentication

Delegated authentication is similar to single sign-on (SSO) in that it allows users to access multiple applications without having to log in separately to each one. Vault delegated authentication provides SSO functionality by allowing a user who has already logged in to a participating application to access Vault without logging in again. 

About Dynamic Access Control for Objects

Dynamic Access Control (DAC) is an access control model for object records, which automates the assignment of users to the records’ Viewer, Editor, and Owner roles through “Matching Sharing Rules” and/or “Custom Sharing Rules.” DAC provides object record-level security.

About Hide User Information

Many organizations need to prevent external or cross-domain users from viewing names and identifying details of other users. With Hide User Information, users will not see the name or other identifying details of any Vault user that does not share the same email domain. Note that this is based on the user’s email address domain, not the Vault user name domain. They also will not be able to delegate access to their vault. The user will be able to see their own information throughout Vault.

Creating & Managing Groups

Groups are key to managing user access in Vault. A group is simply a named list of users, but by defining groups that reflect the teams and roles in your company, and assigning those groups to document roles, you can manage document access more easily and efficiently.

Managing Security Profiles & Permission Sets

Security profiles are how Vault applies permission sets to individual users. Permission sets grant users the ability to view or edit certain Admin areas, or to access certain end user features. For more general information, see About License Types & Security Profiles and About Permission Sets. This article explains how to create and manage custom profiles and custom permission sets.

Managing Users Across Vaults

Some vaults belong to domains with other vaults. If you have the Domain Admin user setting, you’ll see the Domain Users page, rather than the standard Users page, when you navigate to Admin > Users & Groups > Users. From this page, you can filter the user list to see only members of specific vaults, cross-domain users, or all users including home-domains and cross-domains. Note that you only have access to vaults where you have the correct permissions

Configuring Network Access Rules

The Network Access Rules page allows you to limit the IP addresses from which specific users can log in, based on those users’ security policies. Each rule can apply to either a single IP address or an IP range. You cannot create a rule that would lock you out. For any security policy that is not part of a network access rule, users can log in from any IP address.

Configuring OAuth 2.0 / OpenID Connect Profiles

In order to configure SSO, you must first create a SAML profile. Then, you must provision users to use the profile. The following article walks through the creation of an OAuth 2.0 / OpenID Connect profile. 

Configuring Password Security Policies

The Security Policies page (Admin > Settings > Security Policies) allows you to create and manage password policies for users. These settings control password requirements, expiration period, reuse policy, security question policy, and delegated authentication via Salesforce.com.

About Permission Sets

In Vault, permission sets are a way to group permissions together. Security profiles then use the permission sets to grant or restrict users’ access to certain features, particularly system administration functions such as user management or object record creation. For example, the permission sets applied to the IT Administrator security profile allow users with that profile to manage users and groups, but not studies and sites.

Configuring SAML Profiles

In order to configure SSO, you must first create a SAML profile. Then, you must provision users to use the profile. Vault allows you to create multiple SAML profiles and associate each with a different identity provider. This allows users to authenticate with any IdP configured on the security policy to which they are assigned.

About License Types & Security Profiles

In Vault, each user has an assigned license type and security profile. Each security profile has one or more permission sets. The license type is the first level of access control that vault applies to a user. Permission sets, applied through the user’s security profile, are the second level of access control. Both the license type and permission set must grant access to a user in order for that user to access the functionality. Other access control for a user is based on Dynamic Access Control settings for individual object records.

About the Security Settings Page

The Security Settings page (Admin > Settings > Security Settings) allows you to view information about the vault. You must have a security profile that grants the Security Settings: Edit permission in order to modify this.

SSL Certificate

Veeva Vault utilizes an SSL certificate to secure data between Vault and your web browser. The SSL certificate is cryptographic key that activates the HTTPS protocol and padlock within the browser and web server, allowing for secure connections.

Single Sign-On Basics

Single Sign-On (SSO) is a process that allows users to access multiple authorized applications without having to log in separately to each application. SSO allows organizations to validate user names and passwords against a corporate user database (such as Active Directory), rather than having separate user credentials managed by Vault and other applications. In Vault, some users may be configured to use SSO, while others use traditional usernames and passwords, meaning that an organization could use SSO for internal users and not for external users.

Single Sign-On Details

When single sign-on (SSO) is enabled for a user, Vault does not validate that user’s password. Instead, Vault relies on an external identity provider to authenticate users and pass information (“assertions”) about the users in web browser requests. This article provides technical details of SSO in Vault. For basic information, see Single Sign-On Basics. For details on setting up SSO, see Configuring Single Sign-On.

Single Sign-On FAQ

Here you’ll find answers to some frequently asked questions about single-sign on and Vault.

About Strict Security Mode

In past releases, Vault provided two security modes for administrator access to documents, known as “strict” and “non-strict.” After V10, we will continue to support the non-strict mode for vaults that already use it, but new vaults and those currently using the strict mode cannot switch to non-strict mode.

Managing the User & Person Objects

This article explains how to create and modify users with the User and Person objects. Managing users with the flexibility of Vault objects allows you to create reports based on user data, create custom fields, and reference users directly from objects with lookup fields.

Veeva IP Addresses

If your organization wants to whitelist Veeva sites, we recommend doing so by domain:

About the General Settings Page

The General Settings page (Admin > Settings > General Settings) allows you to view vault details and enable or disable features.

Managing Branding Settings

The Branding Settings page allows you to configure your vault to display a custom email banner, rather than the default Veeva Vault banner, in Vault-generated emails. 

Using Tokens

Tokens are pieces of text with a specific format that Vault replaces with the values the token represents. They use the format ${tokenName}. For example, in a workflow notification, ${Object.name__v} inserts the object record’s Name value.

About Vault Loader

Vault Loader allows you to load data to your vault or extract data from your vault in bulk. Loader is particularly useful during migrations and on-boarding. Extracted information downloads to a CSV file, which you can load back into your vault or into other systems.

Accessing Your Vault's FTP Server

Each vault in your domain has its own FTP staging server. = The FTP server is a temporary storage area for files you’re uploading to or extracting from Vault. 

Using the Vault Loader Command Line Tool

The Vault Loader Command Line tool allows you to perform all bulk create, export, update, and delete actions from the terminal. 

Vault Loader: Create & Update Groups

Vault Loader allows you to perform bulk actions on groups in your vault. 

Vault Loader: Create, Update & Delete Object Records

Vault Loader allows you to perform bulk Create, Update, and Delete actions on object records within your vault. Loader also provides an Upsert action that lets you create new records and update existing records using a single CSV input. You can also create and update users with the User and Person objects.

Vault Loader: Create & Update Legacy Users

Vault Loader allows you to perform bulk actions on users in your vault. 

Vault Loader: Extracting Metadata

Vault Loader allows you to export object records, users, and groups in CSV format. Many users utilize these exports to create a template for CSV input files when creating, updating, or “upserting” Vault data. You can also use the extracts for detailed data analysis and processing in another application, or for migrating data into another vault.

Vault Usage & Performance Statistics

Each day, Vault automatically creates a new (non-editable) record in the Performance Statistics object. Fields on the record track key performance metrics for your vault. Admins can use this object to set up reports and dashboards to monitor performance and usage metrics.

About Veeva Vault Domains & Domain Settings

A company using Vault can have one or more domains and a domain can contain one or more vaults. Domains with more than one vault are often called “multi-vault domains.” With multiple vaults in a single domain, you can switch between vaults without logging out and logging in again, as long you have access to both vaults. In a typical setup, a customer has one domain that contains all of their production vaults and one domain that contains sandbox or training vaults. In each Vault user name, the domain is everything after the @ symbol. For example, the user tibanez@veevapharm.com is on the veevapharm.com domain.

Viewing Vault Java SDK Solutions

The Vault Java SDK is a powerful tool which allows developers to extend Vault and deliver custom capabilities. You can manage the Vault Java SDK solutions currently deployed in your vault from Admin > Configuration > Vault Java SDK. These pages are read-only.

Managing CDMS Study Roles

Vault CDMS offers a security model allowing users to have different roles in different studies. This model leverages the Application Role object to define user access at the object level (in this case, the Study object), instead of at the account level. Your Application Role extends your permissions granted by your Security Profile. These combined represent the Study Role, a permission grouping that you can manage from Tools > Role Management.

Vault Coder Security Profiles

In Vault, each user has an assigned license type and security profile. Each security profile has one or more permission sets. The license type, either Full User or Read-only User  is the first level of access control that vault applies to a user. Permission sets, applied through the user’s security profile, are the second level of access control. Both the license type and permission set must grant access to a user in order for that user to access the functionality.

Vault EDC Security Profiles

In Vault, each user has an assigned license type and security profile. Each security profile has one or more permission sets. The license type, either Full User or Read-only User  is the first level of access control that vault applies to a user. Permission sets, applied through the user’s security profile, are the second level of access control. Both the license type and permission set must grant access to a user in order for that user to access the functionality.

Study Access in Vault CDMS

Vault CDMS leverages the Vault Platform to control user access. In addition to configuring account-level access, User Administrators can manage user access at the Study level.