Configuring Approved Email

Initial configuration includes the setup of all default functionality for Approved Email. Advanced functionality requires additional configuration.

Configuring Approved Email Admins and Integration Users – 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 – 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 for Offline Devices – Approved Email can be used in offline devices using VMOCs
Configuring Approved Email in Vault – After configuring Approved Email in CRM, the instance of Vault to be used in Approved Email must also be configured

Integrating CRM and Vault for Approved Email – Once both Vault and 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 – Before end users can send Approved Emails, an email Sending Domain must be defined
Viewing Approved Email License Usage – Admins can quickly see a list of users currently enabled to use Approved Email