# Configuring Export Binder as Merged PDF (Regulatory Documents)

[Regulatory Documents](/en/lr/484002/) provides users with the ability to export all document renditions in a binder as a [single merged PDF file](/en/lr/585085/). This allows users to easily generate a complete file to submit to authorities when registering new products and responding to customer requests for regulatory documents.

## Configuration Overview {#overview}

Configuring your Vault to export a binder as merged PDF involves the following steps:

1. [Configure binders][1]
2. [Configure the _Export Binder as Merged PDF_ action][2]
3. [Configure user permissions][3]

<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>: Depending on your Vault’s creation date and which features are currently enabled and configured, some of the steps described in this article may be unavailable or already complete in your Vault.</p>
    </div>
  </div>
</div>



## Configuring Binders {#binders}

Ensure you complete the [binder configuration](/en/lr/4486/) so users can create binders. In [Registration & Dossier Management](/en/lr/71498/) Vaults, you can also [configure Dossier Binders](/en/lr/76894/) so users can export a merged PDF for Dossier Binders containing up to 100 documents.

## Configuring the Export Binder as Merged PDF Action {#actions}

You must [configure](/en/lr/12399/) the _Export Binder as Merged PDF_ user action on the applicable document lifecycle states. To do this:

1. Navigate to **Admin > Configuration > Document Lifecycles > [Document Lifecycle] > States > [State] > User Actions**.
2. Click **Edit**.
3. Click **Add Action** for an existing rule or **Create Rule** to add a new rule.
4. Optional: [Define conditions](/en/lr/12399/#conditions).
5. In the _Allow the following actions_ section, select **Export Binder as Merged PDF**.
6. Enter an **Action Label**.
7. Click **Save**.

When users run the action action, Vault creates a new [instance](/en/lr/24762/) of the _Export Binder as Merged PDF Job_. When the job completes, Vault: 

* Generates a ZIP file containing the generated PDF file containing all the documents the user has [permission][3] to view. Only the user that ran the action can access the ZIP file, which expires in 14 days. If the file expires, users must run the action to generate a new file.
* Notifies the user that the merged PDF is ready for download.
* Creates a system-managed _File Download Results_ record, which includes details about when the file expires and can no longer be accessed, the binder on which the action ran, and the user that ran the action. Do not modify the _File Download Results_ object layout.

Vault automatically terminates _Export Binder as Merged PDF Job_ instances that do not initiate within 16 hours of users running the action.

## Configuring User Permissions {#user-permissions}

You must ensure users have the appropriate read and create [permissions](/en/lr/22824/) to access the appropriate documents and binders in addition to the following permissions and [document roles](/en/lr/2572/):

* Assign the _Security Profile: Application: Document: Download Rendition_ permission to include document renditions in a merged PDF.
* Assign the _View Document_ and _View Content_ permissions to the appropriate document roles on the applicable lifecycle states to view and export document renditions in a binder.
* If your Vault uses [Atomic Security for Documents](/en/lr/62043/) on lifecycle states, assign _Export Binder as Merged PDF: Execute_ permission to the appropriate document roles on the applicable lifecycle states.

## Related Permissions {#related-permissions}

You can complete all the steps in this article with the standard _System Administrator_ or _Vault Owner_ security profile. If your Vault uses custom security profiles, your profile must grant the following [permissions](/en/lr/22824/):

<table>
  <tr>
    <th><strong>Type</strong></th>
    <th><strong>Permission</strong></th>
    <th><strong>Controls</strong></th>
  </tr>
    <tr>
    <td>Security Profile</td>
    <td>Admin: Configuration: Document Lifecycles: Edit</td>
    <td>Ability to modify document lifecycles.</td>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Admin: Security: Permission Sets: Edit</td>
    <td>Ability to modify permission sets for users.</td>
  </tr>
</table>

[1]: #binders
[2]: #actions
[3]: #user-permissions
[4]: #related-permissions