Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/InitialConfig/ConfiguringAE.htm

## Configuring Approved Email

### Configuring Vault CRM and Vault for Approved Email

* [Configuring Approved Email Admins and Integration Users](../ConfiguringAE/AEConfigAdmins.htm) – Admins, content admins, and integration users require highly similar permissions and must first be configured to use Approved Email before default functionality is available for use
* [Configuring Approved Email End Users](../ConfiguringAE/AEConfigEndUsers.htm) – End users must be enabled to use Approved Email before default functionality is available for use. This process also provisions Approved Email licenses to end users.
* [Configuring Approved Email in PromoMats / MedComms](https://commercial.veevavault.help/en/gr/12080/)– After configuring Approved Email in Vault CRM, the instance of PromoMats / MedComms to be used in Approved Email must also be configured

### Configuring the Integration Between Vault CRM and Vault

* [Integrating Vault CRM and PromoMats / MedComms for Approved Email](../ConfiguringAE/AECRMVaultIntegration.htm) – Once both PromoMats / MedComms and Vault CRM are configured to use Approved Email, a series of integrative processes must be performed to link the two platforms together and enable content to flow back and forth
* [Creating a Sending Domain](../ConfiguringAE/CreateSendingDomain.htm) – Before end users can send Approved Emails, an email Sending Domain must be defined