# Email to Inbox Item

Vault generates _Inbox Items_ from emails sent to a specified inbound email address based on the _Attachment Handling Method_ specified for the sender's associated <a href="/en/lr/01202/">_Transmission Profile_</a>:

* [**Separate**][1]: Vault generates one _Inbox Item_ per attachment, prepopulated with E2B data <a href="/en/lr/01135/#e2b-import">imported</a> from the XML or ZIP attachment.
* [**Single-File Import**][2]: Vault generates one _Inbox Item_ per email, prepopulated with E2B data <a href="/en/lr/01135/#e2b-import">imported</a> from the XML or ZIP attachment.
* [**Manual** or blank][3]: Vault generates one blank _Inbox Item_ per email for manual intake. This also applies to the following scenarios:
  * The sender is not associated with a _Transmission Profile_.
  * The _Attachment Handling Method_ of a sender's _Transmission Profile_ is unspecified.
  * The _Attachment Handling Method_ of a sender's _Transmission Profile_ is _Single-File Import_ but the email attachment is not a valid E2B XML or ZIP format.

Based on the sender's email, Vault populates <a href="/en/lr/907890/">_Inbound Transmissions_</a>. When <a href="/en/lr/715460/#r243">configured</a> by your Admin, Vault populates the _Country_ and _Report Type_ fields based on the _Transmission Profile_ associated with the sender. Vault sends a notification to all users with the _Intake_ role, which alerts them to the success or failure of _Inbox Item_ generation.

<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>: If the <em>Sender Email</em> section of an <em>Inbound Email</em> type <em>Transmission Profile</em> has two or more <em>Email Person</em> records with the same <em>Email</em>, Vault selects the most recently created <em>Email Person</em> record to populate the details of the <em>Inbound Transmission</em>. We do not recommend having multiple <em>Email Person</em> records with the same <em>Email</em> in your Vault.</p>
    </div>
  </div>
</div>



Vault classifies generated files depending on the _Email Body Classification_ value of the sender's associated _Transmission Profile_:

* **Case > Source > Adverse Event Report**: The email body is the source of the _Inbox Item_ and the generated document is classified as _Case > Source > Adverse Event Report_. The generated files for non-E2B email attachments are classified as _Case > Source > Non Re-Transmittable Document_.
* **Case > Source > Non Re-Transmittable Document**: The email attachment is the source of the _Inbox Item_ and the generated document is classified as _Case > Source > Adverse Event Report_. The generated file for the email body is classified as _Case > Source > Non Re-Transmittable Document_.

## Prerequisites

To allow _Inbox Item_ generation from emails, your Admin must complete the following:

* <a href="/en/lr/715460/">Enable Sender-Based Email Attachment Handling</a>.
* <a href="/en/lr/01200/">Configure Email to Vault Safety Inbox Item</a>.
* Optional: <a href="/en/lr/860508/">Enable Automated Acknowledgement of Email to Inbox</a>.
* Optional: <a href="/en/lr/01320/">Enable Automated Case Promotion</a> on _Transmission Profiles_.
* Optional: Control access to _Inbox Items_ from email intake based on the sender's email address. For more information about assigning _Case_ access by local PV email, see <a href="/en/lr/01182/">Manage Case Access Group Security</a>.

## Automatic Inbox Items from Emails {#auto}

You can receive emails directly in your Vault and generate _Inbox Items_ from an email source with E2B data populated based on the _Attachment Handling Method_ of the sender's _Transmission Profile_.

### Separate {#separate}

When the _Attachment Handling Method_ of the sender's _Transmission Profile_ is _Separate_, Vault creates one document for the email source, linked to all _Inbox Items_ generated from the email. For each email attachment, Vault also creates:

* One document, linked to the _Inbox Item_ generated from the email.
* One _Inbox Item_ with _Intake Method_ set as _Email_.
  * For all supported single- and multi-E2B XML and ZIP file attachments, Vault imports the data into the generated _Inbox Item_ and sets the _Intake Format_ field to _E2B_
  * For unsupported attachments, Vault generates a blank _Inbox Item_ for manual intake and sets the _Intake Format_ field to _Document_.

### Single-File Import {#single-file}

When the _Attachment Handling Method_ of the sender's _Transmission Profile_ is _Single-File Import_, Vault creates the following for the first XML attachment:

* One document, linked to the _Inbox Item_ generated from the email.
* One _Inbox Item_ with _Intake Method_ set as _Email_.
  * For all supported single- and multi-E2B XML and ZIP file attachments, Vault imports the data into the generated _Inbox Item_ and sets the _Intake Format_ field to _E2B_.
  * For unsupported attachments, Vault generates a blank _Inbox Item_ for manual intake and sets the _Intake Format_ field to _Document_.

## Manual Intake from Emails {#manual}

You can receive emails directly in your Vault and generate _Inbox Items_ from an email source for <a href="/en/lr/01133/">manual intake</a>. When the _Attachment Handling Method_ of the sender's _Transmission Profile_ is _Manual_ or blank, or if the sender is not associated with a _Transmission Profile_, Vault creates:

* One classified as _Adverse Event Report_ document for the email source
* One classified as _Attachment_ document for each email attachment
* One blank _Inbox Item_ containing the email file document and the attachment

<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 create an <em>Inbox Item</em> if the email file document or attachment document fails to generate during email processing.</p>
    </div>
  </div>
</div>



## Limitations

Vault enforces a <a href="/en/lr/74285/#size-limitations">size limitation</a> for inbound emails, including attachments. 

[1]: #separate
[2]: #single-file
[3]: #manual
[4]: #intake-agent