# Sending Document Packages



<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The features described on this page are no longer available for new implementations and will be deprecated in the 27R3 release.  <a href="/en/lr/64233/">Veeva Site Connect</a> provides similar functionality, enabling sponsors and CROs on Clinical Operations Vaults to securely exchange documents, document requests, and data with sites on SiteVault Vaults.</p>
    </div>
  </div>
</div>




The **Send Document Package** action allows you to start workflows for multiple documents in a single process. This feature can help you to activate a trial site as quickly as possible. To use it, an Admin must first [enable the feature and configure default workflows](/en/lr/14311/) for each document type.

## Accessing Document Package Actions

You can access the **Send Document Package** action from the _Site_ object record listing page or a _Site_ record detail page.

Note that you must be an Admin to use document package functionality and you must have a security profile that grants the _Application: Workflow: Start_ permission and a document role that grants _View Document_ permission on each document to include it in a document package.

## How to Send Document Packages

To start multiple document workflows using the **Send Document Package** action:

  1. Open the actions menu for the _Site_ record for which you wish to start a package. Select **Send Document Package**.
  2. Use the checkboxes to select the documents on which to start workflows. See [below][2] to learn how Vault determines which documents are displayed and which can be selected.
  3. Click **Next**.
  4. For each different workflow, fill in the required parameters. If you were starting the workflow for a single document, these are the fields that would appear on the workflow start dialog. See [below][3] for details.
  5. Click **Send**.
  6. Vault begins all of the workflows simultaneously. Once workflows have started, you can manage them separately.

## About Workflow Parameters {#parameters}

When you use this action, all documents that are starting a specific workflow must use the same workflow start parameters. For example, if the _Review_ workflow requires that you add a due date in the workflow start dialog, every document that starts the _Review_ workflow as part of the same document package will use the same workflow due date. This behavior also applies to assigning users to roles for task completion.

Starting a shared workflow also means that users or groups selected for roles apply to all of the documents for that workflow and Vault will apply any [allowed user](/en/lr/6572/) override rules when you select users.

## Eligible Documents {#eligible}

In order for a document to appear in the list for inclusion in a document package, it must meet these criteria:

  * The document is not a binder.
  * The document's **Process Name** field includes _Set up Site(s)_.
  * The document's **Study** field includes the study for the selected site.
  * The document's **Study Country** field is blank or includes the site's study country.
  * The document's **Study Site** field is blank or includes the selected site.

The documents listed for inclusion in a document package are grouped into study-, study country-, and study site-level documents. Only documents in a steady state will appear in the study and study country groups.

When Vault lists the available documents for a package, the checkbox for some documents may unavailable, meaning that you cannot select and include those documents in the package. There are various reasons why Vault prevents you from including a document:

  * No [default workflow](/en/lr/14311/) is specified for the document type and lifecycle.
  * The default workflow for the document type is inactive.
  * Your permission set does not include the [_Application: Workflow: Start_](/en/lr/33553/#permissions) permission.
  * The start step for the document's default workflow has the setting **Set next state entry fields** enabled.
  * The start step for the document's default workflow requires you to provide an eSignature.
  * The document is already in an active, non-Read & Understood workflow.
  * The first workflow segment (before a workflow task occurs) includes a conditional decision.

 [2]: #eligible
 [3]: #parameters