To enable Inbox Item generation from email, configure email to Vault.
Prerequisites
To support sender-based email attachment handling, you must follow the steps in Enable Sender-Based Email Attachment Handling.
Create Inbound Email Addresses
To allow Inbox Item generation from email, you must set up inbound email addresses.
The Email to Vault feature exists in both Vault and Vault Safety. See Configuring Email to Vault for more information about creating inbound email addresses. Note the following differences when completing the page:
- For the Allowed Senders field, the Anyone option does not exist in Vault Safety.
- For the Email Processor field, you must select Create Inbox Item from Email.
Result
After you complete the page, Allowed Senders can send emails to the specified inbound email address.
Note: The sender must match an email address in the Allowed Senders group you selected. Otherwise, Vault ignores the email and does not create an Inbox Item.
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, 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 record, 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_customer__v) record. 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 (_).
Note: The Organization specified in the subaddress must be of Sponsor-type. If you are not using a subaddress, the Vault Customer must be of Sponsor-type.