You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once you connect your database to Metabase, you'll want to configure an email account to send system notifications to your organization's users. Metabase uses email to reset passwords, onboard new users, and notify you when something happens.
17
+
Once you connect your database to Metabase, you'll want to configure an email account to send system notifications to your organization's users. Metabase uses email to reset passwords, onboard new users, and notify you when something happens (see [dashboard subscriptions](../dashboards/subscriptions) and [alerts](../questions/alerts)).
17
18
18
-
To edit email settings:
19
+
## Email on Metabase Cloud
19
20
20
-
1. Click on the **gear** icon in the upper right.
21
-
2. Select **Admin Settings**.
22
-
3. From the default **Settings** tab, click on **Notification channels** in the left sidebar.
23
-
4. Select **Email**.
21
+
_Admin settings > Settings > Email_
24
22
25
-
##Metabase Cloud
23
+
On Metabase Cloud, you can use the default SMTP server, or set up a custom server.
26
24
27
-
Metabase Cloud manages an email server for you, so you don't need to set up email (and you won't see SMTP settings in your Admin console).
25
+
### Default SMTP server on Metabase Cloud
26
+
27
+
By default, Metabase Cloud will manage an email server for you, so you don't need to set up email.
28
28
29
29
If you like, you can still set up:
30
30
31
-
- A name for your Cloud email account (from name)
32
-
- An email address to receive email replies (reply-to address)
31
+
- A display name for your Cloud email account (the "from" name). The email will still be sent from a Metabase address, however.
32
+
- An email address to receive email replies (reply-to address).
33
+
34
+
When Metabase manages the SMTP server, you can't change the from address. If you want Metabase to send emails from a different domain, you'll need to bring your own SMTP server. See below.
35
+
36
+
### Custom SMTP Server on Metabase Cloud
37
+
38
+
{% include plans-blockquote.html feature="Custom SMTP server on Metabase Cloud" %}
39
+
40
+
_Admin settings > Settings > Email > Set up a custom SMTP server_
41
+
42
+
By default, Metabase Cloud manages an SMTP server for you. But if you want to use your own SMTP server, you can bring your own.
43
+
44
+
You may want to use your own SMTP server if you want to:
45
+
46
+
- Customize the From domain (for example, if you're [white-labeling Metabase](./appearance)).
47
+
- Avoid having emails pass through 3rd-party services.
48
+
- Own IP reputation, logs, monitoring.
49
+
- Own auditing.
50
+
51
+
When setting up a custom SMTP server on Metabase Cloud, you'll configure these fields:
52
+
53
+
-**SMTP HOST**: The address of the SMTP server that handles your emails (e.g., smtp.yourservice.com).
54
+
-**SMTP PORT**: The port your SMTP server uses for outgoing emails. Only encrypted email ports are supported:
55
+
- 465 (SSL)
56
+
- 587 (TLS)
57
+
- 2525 (STARTTLS)
58
+
-**SMTP SECURITY**: Choose the security protocol for your connection:
59
+
- SSL
60
+
- TLS
61
+
- STARTTLS
62
+
-**SMTP USERNAME**: Your SMTP account username.
63
+
-**SMTP PASSWORD**: Your SMTP account password.
64
+
65
+
You'll also need to specify:
66
+
67
+
-**From address**: The email address you want to use for the sender of emails.
68
+
-**Reply-to address**: The email address you want replies to go to, if different from the From address.
69
+
70
+
You can edit these settings at any time. You can also toggle between this custom SMTP server and the server managed by Metabase Cloud.
33
71
34
72
## Configuring your email account
35
73
36
-
For Metabase to send messages to your organization's users, you'll need to set up an email account to send emails via **SMTP** (simple mail transfer protocol), which is an email standard that secures emails with SSL security protection.
74
+
_Admin settings > Settings > Email_
75
+
76
+
For Metabase to send messages to people, you'll need to set up an email account to send emails via **SMTP** (simple mail transfer protocol). SMTP is an email standard that, when combined with SSL/TLS, provides security protection for emails.
37
77
38
78
To start, go to the Admin Panel from the dropdown menu in the top right of Metabase, then from the Settings page, click on **Email** in the left menu.
39
79
@@ -50,22 +90,22 @@ Here you'll set:
50
90
- SSL
51
91
- TLS
52
92
- STARTTLS
53
-
-**SMTP Username**.
54
-
-**SMTP Password**.
93
+
-**SMTP USERNAME**: Your SMTP account username.
94
+
-**SMTP PASSWORD**: Your SMTP account password.
55
95
56
96
You'll also need to specify your:
57
97
58
98
-**From address**: The email address you want to use for the sender of emails.
59
-
-**Reply-to address**: The email address you want the replies to go to, if different from the from address.
99
+
-**Reply-to address**: The email address you want replies to go to, if different from the From address.
60
100
61
101
## Add recipients as CC or BCC
62
102
63
103
By default, Metabase will hide email recipients by including them in the BCC list (Blind Carbon Copy) of the email. But if you're having issues with your email provider blocking emails with BCC recipients, and you don't mind having people see who else has been copied on the email Metabase sends them, you can tell Metabase to CC (Carbon Copy) recipients instead.
64
104
65
105
### Recommended email settings
66
106
67
-
- SSL is strongly recommended because it’s more secure and gives your account extra protection from threats.
68
-
- 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.
107
+
- SSL is strongly recommended because it's more secure and gives your account extra protection from threats.
108
+
- 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.
69
109
70
110
## Notes for common email services
71
111
@@ -75,12 +115,12 @@ By default, Metabase will hide email recipients by including them in the BCC lis
75
115
76
116
### Google Apps
77
117
78
-
1. In the **SMTP host** field, enter smtp.gmail.com
79
-
2. Fill in 465 for the **SMTP port** field
80
-
3. For the **SMTP Security** field, enter **SSL**
81
-
4. In the **SMTP username** field, enter your Google Apps email address (e.g. [email protected])
82
-
5. Enter your Google Apps password in the **SMTP password** field
83
-
6. Enter the email address you would like to be used as the sender of system notifications in the \*_From Address_ field.
118
+
1. In the **SMTP HOST** field, enter smtp.gmail.com
119
+
2. Fill in 465 for the **SMTP PORT** field
120
+
3. For the **SMTP SECURITY** field, enter **SSL**
121
+
4. In the **SMTP USERNAME** field, enter your Google Apps email address (e.g. [email protected])
122
+
5. Enter your Google Apps password in the **SMTP PASSWORD** field
123
+
6. Enter the email address you would like to be used as the sender of system notifications in the **From address** field.
84
124
85
125
### Amazon SES
86
126
@@ -106,7 +146,7 @@ Check if [email quotas](https://docs.aws.amazon.com/ses/latest/dg/quotas.html) a
106
146
107
147
Allowed email address domain(s) for new [dashboard subscriptions](../dashboards/subscriptions) and [alerts](../questions/alerts).
108
148
109
-
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) will be able to email any other person with an account in that same Metabase.
149
+
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 Metabase accounts who aren't [sandboxed](../permissions/data-sandboxes) will be able to email any other person with an account in that same Metabase.
110
150
111
151
To allow all domains, leave the field empty (allowing all domains is the default).
0 commit comments