# Enable Sender-Based Email Attachment Handling
With the 24R2 release, you can configure your Vault to generate _Inbox Items_ from emails sent to a specified inbound email address based on the _Attachment Handling Method_ specified for the sender's associated _Transmission Profile_. When applicable, Vault automatically imports E2B data from email attachments.
Once you have completed the enablement instructions on this page, see Configure Email to Vault Safety Inbox Item to configure this feature.
### 25R1 Update: Email to Inbox Item: Email Attachment Classification
With the 25R1 release, your Vault can use email bodies as source documents for _Inbox Items_, rather than attachments. See [Email to Inbox Item: Email Attachment Classification][3] to configure your Vault for the updated feature.
### 24R3 Update: Sender-Based Email Inbox Item Pre-Population {#r243}
With the 24R3 release, Vault populates certain _Inbox Item_ fields based on the sender's email. See [Sender-Based Email Inbox Item Pre-Population][1] to configure your Vault for the updated feature.
## Modify the Inbox Email Object Type Fields {#inbox-email-fields}
Follow the steps below to modify fields for the _Inbox Email_ type of the _Transmission Profile_ object:
1. Navigate to **Admin > Configuration > Objects > Transmission Profile > Object Types > Inbound Email**.
2. Select the **Organization** field.
3. Select **Edit**.
4. In the **Criteria VQL** field, enter: `object_type__vr.api_name__v = 'sponsor__v'`.
5. Select **Save**.
6. Go to **Admin > Configuration > Objects > Transmission Profile > Object Types > Inbound Email**.
7. Select the **Destination** field.
8. Select **Edit**.
9. In the **Default Value** field, enter: `organization__v`.
10. Go to **Admin > Configuration > Objects > Transmission Profile > Object Types > Inbound Email**.
11. Select the **Origin** field.
12. Select **Edit**.
13. In the **Default Value** field, enter: `organization__v`.
## Create the Inbox Email Object Layout {#inbox-email-layout}
Create an object layout for the _Transmission Profile_ object with the _Inbound Email_ object type:
1. Insert the _Transmission Profile Email > Person_ related object section. We suggest labeling this section `Sender Email`.
2. In the _Sender Email_ section, edit the default columns to include:
* _Email_
* _Access Group_
* _First Name_
* _Last Name_
3. In the _Details_ section, remove the following fields:
* _Name_
* _Organization_
* _Destination_
* _Origin_
4. Insert a _Detail Form_ section:
* **Section Label**: Enter `System`.
* **Section Layout**: Select **Detail Form - Two Columns**.
5. In the _System_ section, add the following fields:
* _Name_
* _Organization_
* _Destination_
* _Origin_
## Create Transmission Profiles {#transmission-profiles}
Vault can automatically generate _Inbox Items_ based on the specified _Attachment Handling Method_ of a sender's _Transmission Profile_:
* **Separate**: One (1) _Inbox Item_ per attachment, prepopulated with E2B data imported from the XML or ZIP attachment.
* **Single-File Import**: One (1) _Inbox Item_ per email, prepopulated with E2B data imported from the XML or ZIP attachment.
* **Manual**: One (1) blank _Inbox Item_ per email.
To support sender-based _Inbox Item_ generation from email attachments, you must create _Inbound Email_ types of _Transmission Profiles_. For more information about how to create _Transmission Profiles_ and add _Email Persons_ for senders, see Manage Transmission Profiles.
## (Optional) Enable Automated Case Promotion {#case-promotion}
You can enable automated _Case_ promotion for _Inbox Items_ generated from inbound email attachments. To do this, enable Automated Case Promotion for _Inbound Email_ types of _Transmission Profiles_.
## (25R1) Email to Inbox Item: Email Attachment Classification
Vault classifies non-E2B files generated from email bodies and attachments based on the _Email Body Classification_ value of the sender's _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_.
### Configure the Transmission Profile Object
Update the [_Inbox Email_ layout][2] of the _Transmission Profile_ object to include the _Email Body Classification_ field.
### Update Transmission Profiles
You can specify that the email body is the source by populating the _Email Body Classification_ field with _Case > Source > Adverse Event Report_ on the applicable _Inbound Email_ types of [_Transmission Profiles_][4]. If the _Email Body Classification_ value is _Case > Source > Non Re-Transmittable Document_ or blank, Vault classifies the attachment as the source document.
## (24R3) Sender-Based Email Inbox Item Pre-Population
Vault can populate the _Country_ and _Report Type_ fields on generated _Inbox Items_ based on the sender's associated _Transmission Profile_.
### Configure the Transmission Profile Object
You must update the [_Inbox Email_ layout][2] of the _Transmission Profile_ object to include a _Details_ section. We suggest labeling this section "Email Settings". Add the following fields:
* _Pre-Populate Country_
* _Pre-Populate Report Type_
### Update Transmission Profiles
Populate the _Pre-Populate Country_ and _Pre-Populate Report Type_ fields on the applicable _Inbound Email_ types of [_Transmission Profiles_][4]. Vault maps the values to _Inbox Items_ generated for all _Email Persons_ associated with the _Transmission Profile_.
[1]: #24r3
[2]: #inbox-email-layout
[3]: #25r1
[4]: #transmission-profiles