# SiteVault What's New in 24R3 Source: https://sites.veevavault.help/gr/sitevault/release-notes/previous-releases/sv-24r3-whats-new/ ## SiteVault Release Highlights ![](https://fast.wistia.com/embed/medias/040mxm3n6y/swatch) * * * ## Veeva eISF ### Study Archival #### Study Archival in SiteVault This feature introduces a [study archival action](/gr/sitevault/studies/archive-initiate/) to assist sites with confirming readiness, capturing key information and dates, and completing the [archival process](/gr/sitevault/studies/archive-overview/). Administrators can select the **Archive Study** action to initiate a series of system-managed archive readiness checks against the study’s documents and related records. Once the archive readiness checks have passed and before the archival is complete, administrators are prompted to attest to several statements regarding the archival process. Once a study is archived, the study cannot be moved to any other state. Administrators can still [add newly found documents to an archived study](/gr/sitevault/studies/archive-add-doc/). The **Archive Study** action is available on any study in the Active state. [![Study Archive Action](/gr/uploads/sitevault/images/help/sv-archive-study-action.gif) ](/gr/uploads/sitevault/images/help/sv-archive-study-action.gif) ### Digital Delegation #### Close Digital Delegation Log This feature introduces the [**Start Delegation Log Closure**](/gr/sitevault/digital-delegation/closure/) action, which speeds up the process of closing out a study with Digital Delegation. When Start Delegation Log Closure is initiated, the following actions occur: - Study team assignments/delegations for users who never fully approved (do not have a date in the Start Date field) are deleted. - Active study team assignments/delegations are moved from Active to Make Inactive - PI Approval Needed. - The Investigator’s End Date field is populated on the final Digital Delegation document. - The user who initiated the log closure receives a notification when the process is complete. When the log closure preparation is finished, a Site Administrator initiates the final Principal Investigator approval. Once approved, all users who are not Site Administrators are removed from the study. ### Site Documents #### Site eBinder: Approval Needed Subtab and Bulk Approval This feature introduces the ability to [approve site documents in bulk](/gr/sitevault/eisf-ebinder/site-ebinder-finalize-copy-certify/) from the Site eBinder. When the **Approval Needed** tab is selected, users with the appropriate permissions can select one or multiple documents to approve. Once the action to approve is selected, users are prompted to complete any required fields. A notification banner advises when the process is complete. ### Reporting #### Monitoring: Updated Dashboards and Reports The Monitoring Dashboard enhancements focus on actionable information, such as outstanding issues and monitoring review history. Monitoring reports now include **Reviewed By** and **Reviewed Date** columns, which are automatically populated when a monitor updates a monitoring status. #### User Access Reporting - Current & Historical This feature enables Research Organization Administrators to generate reports on the system access assigned to current active users or the history of access changes for all users. The **Current User Access Report** includes the option to filter by Site(s), System Roles, and Add-on permissions. The **User Access History Report** offers filters for user type (Staff or Monitor/External) and date range. Both reports allow administrators to choose the output file format and whether or not to include Study Assignment details. #### Expired and Expiring Documents Dashboard This feature introduces the **Expired and Expiring Documents Dashboard** , which replaces the existing **Expiring Documents Dashboard**. Documents related to inactive Staff, inactive Organizations, and canceled or archived Studies are excluded from the Expired and Expiring Documents Dashboard. #### Read and Understand History Report Refresh The **Read and Understand History Report** has been updated with new formatting and columns, as well as the inclusion of Site Documents. The report also includes the **Version Sent** column to assist users with identifying which major version of the document was issued for review. This report remains accessible from a document’s Actions menu. #### View Name of Inactive Users This feature enables site users to view the name of a user who was inactivated (left the organization) after the 24R3 release. The **Created By** and **Last Modified By** fields now display the full names of inactive users. Revealing the user’s name provides helpful visibility into an inactive user’s past access and actions. ### Documents, Workflows, and Notification Enhancements Several standard eISF tools and processes are updated with usability and productivity enhancements: #### New Document Types - **Source Template (Blank)** - **Investigator Brochure (IB) Summary of Changes** For more information, see the [Document Types](/gr/sitevault/eisf-ebinder/doc-types/) and [eISF Reference Model](/gr/sitevault/eisf-ebinder/eisf-model/) spreadsheets. #### Edit-Protected Viewable Renditions This feature ensures that viewable renditions downloaded from SiteVault cannot be edited. #### eSignature Workflow Enhancements - **Document Date** - **Source Documents** - **Multiple Investigator Signatories** #### Notification Enhancements - **Hyperlinks in Digital Delegation Notifications** - **Monitor Notifications** ### Enhancements to Study Components and Tools #### Create Participants and Patients This feature streamlines the [creation of Participants and Patients](/gr/sitevault/studies/participant-create/) into a single step. When creating a Participant, site users have the option to simultaneously create a Patient to associate with the Participant. If an email address is provided on the Patient record, SiteVault will review for existing records with a matching email address. The existing information will display alongside the newly entered information allowing the site user to compare and then select which set of Patient information to associate with the Participant. When the study includes eConsent, users are _required_ to create a new or select an existing Patient to associate with the Participant record. [![Create Participant and Patient](/gr/uploads/sitevault/images/help/sv-create-part-patient.gif) ](/gr/uploads/sitevault/images/help/sv-create-part-patient.gif) #### Tab Alerts The Team, Monitor & Auditors, Responsibilities, and Organizations tabs display an orange dot as an alert that they may require attention. Only administrators can see and dismiss alerts. The exception is the Team tab alert, which remains visible until the needed action has been completed. #### Participant and Team Column Selection This feature enhances the user experience on the Participant and Team pages within a study. Site users can select the table columns to include the preferred set of data, display in the preferred order, and resize as needed. The selected settings are retained until additional changes are made. #### Participant Tab - Participant Status The Participant tab’s **Participant Status** column changes from a display field to a button where all statuses are available for selection. #### Staff & Participant Button Labels The **+ Assign** and **+ Create Participants** buttons are relabeled to **+ Add Staff** and **+ Add Participant** on the Team and Participant tabs, respectively. ### Veeva Mobile Applications #### Vault Mobile App Site Selector SiteVault users using the [Vault Mobile App](/gr/sitevault/getting-started/vault-mobile/) can toggle between sites using the Site Selector dropdown field at the top center of the app screen. [![Vault Mobile App](/gr/uploads/sitevault/images/help/sv-vault-mobile-site-selector.png) ](/gr/uploads/sitevault/images/help/sv-vault-mobile-site-selector.png) #### Aligned Regions between SiteVault and MyVeeva for Patients This feature enhances the connection between SiteVault and MyVeeva for Patients to ensure the alignment of geographic settings maintained within each application. ## Veeva eConsent ### eConsent Multi-Signature Enhancements When editing eConsent forms, site users can specify a Second Guardian and/or Second Caregiver on signature and question blocks. This enhancement facilitates gathering unique responses from each Guardian or Caregiver. Sites can assign any number of Guardians, Caregivers, and Witnesses to a Participant. When [**Start Consent**](/gr/sitevault/econsent/consenting-participants/) is initiated, a maximum of two of the Participant’s Guardians, Caregivers, or Witnesses can be selected per role. eConsent forms created before the 24R3 release that include a Guardian signature will require a Second Guardian Signature block added post-release if two Guardian signatures are required. Note _Existing Witness, Guardian, and Caregiver questions_ will be associated with the base Witness, Guardian, and Caregiver signatures post-release. For example, the first Guardian to receive and sign the eConsent form may not be the base Guardian and thus not assigned to any questions.