# Configure Email to Safety Inbox Item To support _Inbox Item_ generation from email, you must configure Email to Vault. ## Prerequisites To configure sender-based email attachment handling, you must first enable Sender-Based Email Attachment Handling. ## Create Inbound Email Addresses You must create the applicable _Inbound Email Addresses_ to define the senders for which Vault generates _Inbox Items_. For more information, see Configuring Email to Vault. When creating the _Inbound Email Address_, you must specify certain fields as follows: * **Email Processor**: Select **Create Inbox Item from Email**. * **Allowed Senders**: Specify who can email the specified address _Email Address_. Vault ignores emails from any sender not in the selected group: * **All Users & Persons in this Vault**: Any email addresses associated with a _User_ or _Person_ record. * **All Users in this Vault**: Any email addresses associated with a _User_ record. * **Specific Groups**: Any email addresses associated with a _User_ record in any of the specified _Allowed Sender Groups_. If you select this option, you must populate the _Allowed Sender Groups_ field. * **Anyone**: This option is not available in Veeva Safety. You can continue to use an existing email address by setting up an auto-redirecting rule to a Vault-owned email in your email inbox. Or, specified _Allowed Senders_ can send emails directly to a Vault-owned email address. ## Use a Subaddress When you are sending an email to a Vault-owned email address, you have the option of adding a subaddress to the Vault-owned email address to specify the organization for CROs with multiple sponsor-type organizations in their Vaults. For example, in the email address `aer+organization__v=sponsor1__v@cro-abc.veevavault.com`, the subaddress is `organization__v=sponsor1__v`. If the subaddress matches the API name of a _Sponsor_ type of _Vault Customer_, Vault will use it to set the _Organization_ field for the _Inbox Item_ and all linked Vault documents when an _Allowed Sender_ sends an email to the specified _Email Address_. If the subaddress is unavailable, Vault populates this field using the _Organization_ associated with the _Vault Customer_. Vault will not use the sender's organization if it contains special characters, as this field only supports upper and lowercase text, numeric values, and underscores (`_`).
## Manage Transmission Profiles To generate _Inbox Items_ for email intake, you must create or update the applicable _Inbound Email_ types of _Transmission Profile_, populate all applicable fields, and add _Email Persons_ for senders.