# Manage Safety Report Binders

After generating a document collection from a <a href="/en/lr/680212/">_Case Collection_</a>, Vault exports all forms to a binder and updates are version-controlled. This makes downloading and sharing collections quick and easy. For more information, see <a href="/en/lr/4386/"> Binders Overview</a>.

## Prerequisite

Your Admin must <a href="/en/lr/680214/#case-number">enable Create and Export Case and Safety Report Collections</a>.

## Working with Safety Report Binders

You can view a binder by selecting the link on the associated _Case Collection_. You can also find binders generated from _Case Collections_ in the _Library_. For more information, see <a href="/en/lr/442/">Searching Vault</a>.

Vault includes the following safety report binder document types, subtypes, and classifications:

* _Case Binder > Case Collection Binder > CIOMS Masked Case Collection_
* _Case Binder > Case Collection Binder > CIOMS Unmasked Case Collection_
* _Case Binder > Case Collection Binder > E2B Case Collection_

### Safety Report Versions

When generating safety reports for a _Case Collection_, Vault creates or updates document versions based on the _Case_ version's state and whether safety reports already exist in that format. Vault generates a report for the _Case_ version if one (1) does not already exist. The report is added to the binder and the _Case_.

### CIOMS I Masked Form Generation Considerations

Vault completes the following configuration when generating CIOMS I Masked forms:

* The _Redacted_ field is set to _Yes_.
* If the _Study Case_ version's _Blind Protection_ field is set to _On_, the expected study content is blinded.

### E2B(R3) Generation Report Considerations

Consider the following when generating E2B(R3) reports:

* The format for E2B(R3) reports is always ICH E2B(R3). Localized E2B(R3) reports cannot be generated from _Case Collections_.
* When generating ICH E2B(R3) reports for _Case Collections_, Vault populates some required data elements as outlined in the following table:

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>N.1.2 Batch Number</td>
            <td>Vault generates a batch number.</td>
        </tr>
        <tr>
            <td>N.1.3 Batch Sender Identifier</td>
            <td><code>SENDERID</code></td>
        </tr>
        <tr>
            <td>N.1.4 Batch Receiver Identifier</td>
            <td><code>RECEIVERID</code></td>
        </tr>
        <tr>
            <td>N.2.r.2 Message Sender Identifier</td>
            <td><code>SENDERID</code></td>
        </tr>
        <tr>
            <td>N.2.r.3 Message Receiver Identifier</td>
            <td><code>RECEIVERID</code></td>
        </tr>
    </tbody>
</table>