# Configuring Dossier Binders (Registration & Dossier Management)

<a href="/en/gr/71498/">Registration & Dossier Management</a>
 allows users to <a href="/en/gr/76898/">create and export a Dossier Binder</a>
 for a specific requirement that includes a list of all expected documents needed for a submission. Vault organizes the documents in nested hierarchical sections that match the _Requirement_ hierarchy structure.

## Configuration Overview {#overview}

Configuring your Vault to use Dossier Binders involves the following steps:

1. [Enable binder export][7] in your Vault so users can export Dossier Binders
2. [Set up EDL in your Vault][1] to automatically add expected documents to Dossier Binders
3. Optional: [Configure _Requirement_ object types][12]
4. [Configure a document lifecycle][13] for Dossier Binders
5. Optional: [Configure DAC for documents][14] to define how Vault assigns users to document roles for documents in Dossier Binders
6. [Configure a document type][2] for generated Dossier Binders
7. [Configure object actions][8] so users can create and export Dossier Binders
8. [Configure the _Requirement_ object layout][4]
9. [Configure user permissions][11]

<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>



## Enabling Binder Export {#enable}

You must enable the binder export feature on the **Admin > Settings > General Settings** page for users to export Dossier Binders. See <a href="/en/gr/4486/">Binder Administration</a>
 for more details.

You can also configure your Vault to export a Dossier Binder with less than 100 documents as a single <a href="/en/gr/585087/">merged PDF file</a>
 with the <a href="/en/gr/484002/">Regulatory Documents</a>
  application.

## Setting up EDL {#edl}

You must <a href="/en/gr/33316/">set up EDL</a>
 in order for Vault to automatically match and add documents to the Dossier Binder sections based on the _EDLs_ in a _Requirement_ hierarchy. When users trigger Dossier Binder creation, Vault adds the documents to the relevant binder section for every _EDL Item_ related to each _Requirement_.

## Configuring Requirement Object Types {#object-types}

You can configure custom object types for the _Requirement_ object. If you do this, you must <a href="/en/gr/32857/#assign">assign</a>
 the _Binder_ field to all object types. If you do not assign the field to all object types, the [_Create Binder_][3] and [_Create and Export Binder_][9] actions will fail.

## Configuring a Document Lifecycle {#lc}

When users run the _Create Binder_ and _Create and Export Binder_ actions, Vault applies a specified lifecycle to generated Dossier Binders. Ensure that a <a href="/en/gr/2306/">document lifecycle</a>
 is configured, which you will assign to the appropriate [document type][2], and then specify in the _Binder Lifecycle_ field when [configuring the actions][8].

## Configuring DAC for Documents {#dac}

If you want Vault to assign users to specific document roles on documents in generated Dossier Binders, you must configure <a href="/en/gr/31824/">DAC for documents</a>
 for the [appropriate lifecycle][13].

 <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>: Vault does not assign any configured <a href="/en/gr/2662/">document lifecycle roles</a>
 to Dossier Binders generated by the <a href="#create"><em>Create Binder</em></a> and <a href="#create-export"><em>Create and Export Binder</em></a> actions.</p>
    </div>
  </div>
</div>



## Configuring a Document Type {#document-types}

When users run the [_Create Binder_][3] and [_Create and Export Binder_][9] actions, Vault applies a specified document type and lifecycle to generated Dossier Binders. You can specify any childless document type, subtype, or classification in the _Binder Type_ field after completing the following:

* Add the _Requirement_ <a href="/en/gr/4884/#use-shared-field">shared field</a>
 to the appropriate document type, subtype, or classification. When users trigger Dossier Binder creation, Vault populates this field with the name of the parent record on which they triggered the action.
* Add the [applicable lifecycle][13] to the <a href="/en/gr/618/#EditingDocTypes">_Available Lifecycles_ field</a>
 on the _General_ tab of the appropriate document type, subtype, or classification.

## Configuring Dossier Binders Object Actions {#actions}

You can configure the following actions on the _Requirement_ object so users can create and export Dossier Binders <a href="/en/gr/76898/#about-creation">with the appropriate sections and documents</a>
:

* [_Create Binder_][3]
* [_Create and Export Binder_][9]
* [_Export Binder_][10]

If you configured [object types][12] on the _Requirement_ object, <a href="/en/gr/32857/#how-to-assign-user-actions">assign the actions to all applicable object types</a>
. If you add any of these actions as <a href="/en/gr/43127/">record actions</a>
, do not select the _Available in All Lifecycle States_ checkbox.

### Configuring the Create Binder Action {#create}

The _Create Binder_ action allows users to create a Dossier Binder based on all related _Requirement_ records in the hierarchy, their related _EDL Items_, and applicable matched documents.

Depending on your business needs, you can:

* Add this action as an <a href="/en/gr/59885/#entry-actions">entry action</a>
 on any _Requirement_ lifecycle state.
* Add this action as a <a href="/en/gr/59885/#user-actions">user action</a>
 on any _Requirement_ lifecycle state.
* Add this action as a <a href="/en/gr/43127/#assign-actions">record action</a>
 on the _Requirement_ object.

When configuring the action on a specific lifecycle state, you must define the following fields:

* **Binder Type**: The name of an active document type, subtype, or classification Vault applies to generated Dossier Binders. Do not enter a document type with child subtypes or a subtype with child classifications.
  * To reference a subtype or classification, you must include the appropriate hierarchical parents in dot-separated format. For example, to reference the `formulation__c` subtype of the `dossier__c` document type, you'd enter `dossier__c.formulation__c`, and to reference the `safety_data_sheet__c` classification of the `formulation__c` subtype and `dossier__c` document type, you'd enter `dossier__c.formulation__c.safety_data_sheet__c`.
* **Binder Lifecycle**: The name of an active document lifecycle Vault applies to generated Dossier Binders. The lifecycle must be [available][2] for the document type, subtype, or classification you entered in the _Binder Type_ field.

### Configuring the Create and Export Binder Action {#create-export}

The _Create and Export Binder_ action allows users to create a Dossier Binder based on all related _Requirement_ records in the hierarchy, their related _EDL Items_, and applicable matched documents, and then export the Dossier Binder as a ZIP file. The exported Dossier Binder maintains the requirement hierarchy as nested folders in the export.
Depending on your business needs, you can:

* Add this action as a <a href="/en/gr/59885/#user-actions">user action</a>
 on any _Requirement_ lifecycle state.
* Add this action as a <a href="/en/gr/43127/#assign-actions">record action</a>
 on the _Requirement_ object.

When configuring the action on a specific lifecycle state, you must define the following fields:

* **Binder Type**: The name of an active document type, subtype, or classification Vault applies to generated Dossier Binders. Do not enter a document type with child subtypes or a subtype with child classifications.
  * To reference a subtype or classification, you must include the appropriate hierarchical parents in dot-separated format. For example, to reference the `formulation__c` subtype of the `dossier__c` document type, you'd enter `dossier__c.formulation__c`, and to reference the `safety_data_sheet__c` classification of the `formulation__c` subtype and `dossier__c` document type, you'd enter `dossier__c.formulation__c.safety_data_sheet__c`.
* **Binder Lifecycle**: The name of an active document lifecycle Vault applies to generated Dossier Binders. The lifecycle must be [available][2] for the document type, subtype, or classification you entered in the _Binder Type_ field.

### Configuring the Export Binder Action {#export}

The _Export Binder_ action allows users to export a previously-created Dossier Binder as a ZIP file, which maintains the requirement hierarchy as nested folders in the export.

Depending on your business needs, you can:

* Add this action as a <a href="/en/gr/59885/#user-actions">user action</a>
 on any _Requirement_ lifecycle state.
* Add this action as a <a href="/en/gr/43127/#assign-actions">record action</a>
 on the _Requirement_ object.

### Limitations {#action-limits}
Vault does not support _Binder Types_ for document types with child subtypes or subtypes with child classifications. If you enter a parent document type or subtype in the _Binder Type_ field when configuring the [_Create Binder_][3] and [_Create and Export Binder_][9] actions on a _Requirement_ lifecycle state, Vault will display an error that the document type does not exist or is not active.

## Configuring the Requirement Object Layout {#ri-page-layout}

You must add the following fields to the _Requirement_ <a href="/en/gr/26387/">object layout</a>
 on all object types:

* **Binder**: Vault populates this field when it creates a Dossier Binder.
* **Dossier Folder**: Users can populate this field to determine if the requirement will be a section in the Dossier Binder. You can <a href="/en/gr/42778/">configure defaults for this field</a>
 so that users do not have to manually populate this field on all applicable _Requirement_ records.
* **Exclude from Binde**r: Users can select this checkbox to exclude a _Requirement_ (and the supporting documents) from a generated binder.

## Configuring User Permissions {#user-permissions}
You must ensure users have the appropriate read and create permissions to access the appropriate objects and object fields in addition to the permissions outlined below:

### Export Dossier Binders

* For the _Requirement_ object: _Read_ permission on the _Binder_ field.
* Users must have the _Security Profile: Application: Document: Download Rendition_ permission. Without this permission, the exported ZIP file will not include any folders or documents.
* Users must have the _View Content_ and _View Document_ <a href="/en/gr/2572/">document roles</a>
 on all documents in a Dossier Binder for those documents to be included in the export. If you configured the _Create Binder_ and _Create and Export Binder_ actions on specific lifecycle states, users must also have these permissions 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 <a href="/en/gr/22824/">permissions</a>
:

<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 Types: Edit</td>
    <td>Ability to modify document types.</td>
  </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: Configuration: Objects: Create, Edit</td>
    <td>Ability to create and modify Vault objects.</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]: #edl
[2]: #document-types
[3]: #create
[4]: #ri-page-layout
[5]: #user-permissions
[6]: #related-permissions
[7]: #enable
[8]: #actions
[9]: #create-export
[10]: #export
[11]: #user-permissions
[12]: #object-types
[13]: #lc
[14]: #dac