You might also want to specify [approved domains for notifications](./settings.md#approved-domains-for-notifications).
Here you'll set:
## Google Apps
-**SMTP HOST**: The address of the SMTP server that handles your emails.
-**SMTP PORT**: The port your SMTP server uses for outgoing emails.
-**SMTP SECURITY**:
- None
- SSL
- TLS
- STARTTLS
-**SMTP Username**.
-**SMTP Password**.
You'll also need to specify your:
-**From address**: The email address you want to use for the sender of emails.
-**Reply-to address**: The email address you want the replies to go to, if different from the from address.
### Recommended email settings
- SSL is strongly recommended because it’s more secure and gives your account extra protection from threats.
- If your email service has a whitelist of email addresses that are allowed to send email, be sure to whitelist the email address that you put in the **From Address** field to ensure you and your teammates receive all emails from Metabase.
## Notes for common email services
-[Google Apps](#google-apps)
-[Amazon SES](#amazon-ses)
-[Mandrill](#mandrill)
### Google Apps
1. In the **SMTP host** field, enter smtp.gmail.com
2. Fill in 465 for the **SMTP port** field
3. For the **SMTP Security** field, enter **SSL**
4. In the **SMTP username** field, enter your Google Apps email address (e.g. hello@yourdomain.com)
5. Enter your Google Apps password in the **SMTP password** field
6. Enter the email address you would like to be used as the sender of system notifications in the **From Address* field.
6. Enter the email address you would like to be used as the sender of system notifications in the \*_From Address_ field.
## Amazon SES
### Amazon SES
1. Log on to [https://console.aws.amazon.com/ses](https://console.aws.amazon.com/ses).
2. Click **SMTP Settings** from the navigation pane.
...
...
@@ -47,21 +73,44 @@ You might also want to specify [approved domains for notifications](./settings.m
5. Next, select **Show User SMTP Credentials** to view the user's SMTP credentials.
6. Go back to the Metabase Admin Panel form and enter the info there.
**Note**
Check if [email quotas](https://docs.aws.amazon.com/ses/latest/dg/quotas.html) apply to your Amazon SES server. You may want to manage your email recipients using groups instead.
## Mandrill
### Mandrill
1. Log in to your Mandrill account and locate your credentials from the **SMTP & API Info** page there.
2. Your SMTP password is any active API key for your account — *not* your Mandrill password.
2. Your SMTP password is any active API key for your account — _not_ your Mandrill password.
3. Although Mandrill lists **port 587**, [any port supported by Mandrill](https://mailchimp.com/developer/transactional/docs/smtp-integration/#the-basics) will work for SMTP email.
4. Now you can go back to the Metabase Admin Panel form and enter the info there.
## Recommended settings
## Approved domains for notifications
{% include plans-blockquote.html feature="Approved domains for notifications" %}
Allowed email address domain(s) for new [dashboard subscriptions](../dashboards/subscriptions.md) and [alerts](../questions/sharing/alerts.md).
Adding approved domains allows you to restrict which email addresses people can send alerts and subscriptions to. This restriction only applies to sending email to people who lack an account with that Metabase. People with accounts in a Metabase who aren't [sandboxed](../permissions/data-sandboxes.md) will be able to email any other person with an account in that same Metabase.
* SSL is strongly recommended because it’s more secure and gives your account extra protection from threats.
* If your email service has a whitelist of email addresses that are allowed to send email, be sure to whitelist the email address that you put in the **From Address** field to ensure you and your teammates receive all emails from Metabase.
To allow all domains, leave the field empty (allowing all domains is the default).
To specify multiple domains, separate each domain with a comma, with no space in between (e.g., "domain1,domain2").
You can also set this property using the environment variable [`MB_SUBSCRIPTION_ALLOWED_DOMAINS`](../configuring-metabase/environment-variables.md#mb_subscription_allowed_domains).
> This setting doesn't affect existing subscriptions and alerts.
## Suggest recipients on dashboard subscriptions and alerts
{% include plans-blockquote.html feature="Approved domains for notifications" %}
Control which recipients people can see when they create a new [dashboard subscription](../dashboards/subscriptions.md) or [alert](../questions/sharing/alerts.md). For example, you may want to restrict people to viewing potential recipients that belong to the same [groups](../people-and-groups/managing.md#groups) they are a member of.
Options include:
- Suggest all users
- Only suggest users in the same groups
- Don't show suggestions
People who are sandboxed won't see suggestions.
## Further reading
...
...
@@ -70,4 +119,3 @@ Check if [email quotas](https://docs.aws.amazon.com/ses/latest/dg/quotas.html) a
@@ -38,22 +38,6 @@ For example, say you enable HTTPS redirect for a Metabase instance at the site U
This email address will be displayed in various messages throughout Metabase when users encounter a scenario where they need assistance from an admin, such as a password reset request.
## Approved domains for notifications
{% include plans-blockquote.html feature="Approved domains for notifications" %}
Allowed email address domain(s) for new [dashboard subscriptions](../dashboards/subscriptions.md) and [alerts](../questions/sharing/alerts.md).
Adding approved domains allows you to restrict which email addresses people can send alerts and subscriptions to. This restriction only applies to sending email to people who lack an account with that Metabase. People with accounts in a Metabase who aren't [sandboxed](../permissions/data-sandboxes.md) will be able to email any other person with an account in that same Metabase.
To allow all domains, leave the field empty (allowing all domains is the default).
To specify multiple domains, separate each domain with a comma, with no space in between (e.g., "domain1,domain2").
You can also set this property using the environment variable [`MB_SUBSCRIPTION_ALLOWED_DOMAINS`](../configuring-metabase/environment-variables.md#mb_subscription_allowed_domains).
> This setting doesn't affect existing subscriptions and alerts.
## Anonymous tracking
This option turns determines whether or not you allow [anonymous data about your usage of Metabase](../installation-and-operation/information-collection.md) to be sent back to us to help us improve the product. [Your database’s data is never tracked or sent](https://www.metabase.com/security).
Send different groups of people the contents of the dashboard with different filters applied. You only need to maintain one dashboard, which you can use to send results relevant to each subscriber.
### Custom filter values
Send different groups of people the contents of a dashboard with different filters applied. You only need to maintain one dashboard, which you can use to send results relevant to each subscriber.
-[Customizing filter values for each dashboard subscription](../dashboards/subscriptions.md)
## Restrict which domains people can send alerts and subscriptions to
### Restrict which domains people can send alerts and subscriptions to
As an additional security layer, you can whitelist domains, which restricts people from sending alerts and subscriptions to email addresses that don't use an approved domain.
-[Approved domains for notifications](../configuring-metabase/settings.md#approved-domains-for-notifications)
-[Approved domains for notifications](../configuring-metabase/email.md#approved-domains-for-notifications)
### Suggest recipients on dashboard subscriptions and alerts
You can also control which recipients Metabase suggests when people create dashboard subscriptions and alert.
