Sisense emailing mechanism is based on Mandrills' services and Mandrill is an email infrastructure service. Out of the box, Sisense provides the infrastructure to send emails under a shared Sisense account.

Some organizations choose to have use and have access to their own own Mandrill account. This allows organizations to:

• Monitor the emailing status (sent, sending, never recieved)
• How many emails have been sent
• Whether the emails have delivered or opened
• Change the displayed "from" email
  • Out of the box, the email indicates to users that the email has been sent via Mandrill.
  • This can be customized within your mandrill account,to learn more check out Mandrill settings.

This post will describe how you can link your organization's Mandrill account with your Sisense instance.

On Sisense 7.2 and later:

1. Obtain your organization's Mandrill credentials, you'll need the following:
   • API Key - provided by Mandrill when an account is created
   • Sender Email - the "from" email address for the Sisense emails
   • Sender Name - the display name of email sender
2. On your organization's Sisense webserver, navigate to the Configuration Manager (localhost:3030) and click on the Sisense logo 5+ times
3. Navigate to Base Configuration > locate the email section
   
4. Enter the API Key, Sender Email, and Sender Name
5. Click the Save Base button at the top right corner

On Sisense 7.1 and earlier:

Mandrill's Emailing settings can be found in the deafult.yaml file under C:\Program Files\Sisense\PrismWeb\vnext\config\default.yaml

Within the default.yaml file, please find the Email section and enter the "senderEmail" and "senderName" you want to use instead of "sisense-admin", and enter your own Mandrill key under "api_key" (provided by Mandrill)

Note: This does not support re-configuring to a non-Mandrill service.

Important notes

After reconfiguring please restart your IIS and the service called "Sisense.Repository".

Please note that this setting overrides the default.yaml component, when upgrading or re-installing Sisense you will need to re-configure this.