[auto] adding content to poc-transform-table->master

Author: Metabase Docs bot

_docs/master/README.md

@@ -135,7 +135,7 @@ Metabase's reference documentation.
 - [Model persistence](./data-modeling/model-persistence)
 - [Metrics](./data-modeling/metrics)
 - [Table metadata admin settings](./data-modeling/metadata-editing)
-- [Field types](./data-modeling/semantic-types)
+- [Field types](./data-modeling/field-types)
 - [Formatting defaults](./data-modeling/formatting)
 - [Working with JSON](./data-modeling/json-unfolding)
 - [Segments](./data-modeling/segments)

_docs/master/configuring-metabase/config-template.md

@@ -266,6 +266,7 @@ config:
     surveys-enabled: true
     synchronous-batch-updates: false
     unaggregated-query-row-limit: null
+    update-channel: latest
     uploads-settings: null
     use-tenants: false
     user-visibility: all

_docs/master/configuring-metabase/email.md

@@ -7,73 +7,33 @@ category: 'Configuring Metabase'
 title: 'Set up email'
 source_url: 'https://github.com/metabase/metabase/blob/master/docs/configuring-metabase/email.md'
 layout: new-docs
-summary: 'Learn how to set up email in Metabase to enable dashboard subscriptions and alerts.'
 redirect_from:
     - /docs/master/administration-guide/02-setting-up-email
 ---
 
 # Set up email
 
-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)).
+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.
 
-## Email on Metabase Cloud
+To edit email settings:
 
-_Admin settings > Settings > Email_
+1. Click on the **gear** icon in the upper right.
+2. Select **Admin Settings**.
+3. From the default **Settings** tab, click on **Notification channels** in the left sidebar.
+4. Select **Email**.
 
-On Metabase Cloud, you can use the default SMTP server, or set up a custom server.
+## Metabase Cloud
 
-### Default SMTP server on Metabase Cloud
-
-By default, Metabase Cloud will manage an email server for you, so you don't need to set up email.
+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).
 
 If you like, you can still set up:
 
-- A display name for your Cloud email account (the "from" name). The email will still be sent from a Metabase address, however.
-- An email address to receive email replies (reply-to address).
-
-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.
-
-### Custom SMTP Server on Metabase Cloud
-
-{% include plans-blockquote.html feature="Custom SMTP server on Metabase Cloud" %}
-
-_Admin settings > Settings > Email > Set up a custom SMTP server_
-
-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.
-
-You may want to use your own SMTP server if you want to:
-
-- Customize the From domain (for example, if you're [white-labeling Metabase](./appearance)).
-- Avoid having emails pass through 3rd-party services.
-- Own IP reputation, logs, monitoring.
-- Own auditing.
-
-When setting up a custom SMTP server on Metabase Cloud, you'll configure these fields:
-
-- **SMTP HOST**: The address of the SMTP server that handles your emails (e.g., smtp.yourservice.com).
-- **SMTP PORT**: The port your SMTP server uses for outgoing emails. Only encrypted email ports are supported:
-  - 465 (SSL)
-  - 587 (TLS)
-  - 2525 (STARTTLS)
-- **SMTP SECURITY**: Choose the security protocol for your connection:
-  - SSL
-  - TLS
-  - STARTTLS
-- **SMTP USERNAME**: Your SMTP account username.
-- **SMTP PASSWORD**: Your SMTP account password.
-
-You'll also need to specify:
-
-- **From address**: The email address you want to use for the sender of emails.
-- **Reply-to address**: The email address you want replies to go to, if different from the From address.
-
-You can edit these settings at any time. You can also toggle between this custom SMTP server and the server managed by Metabase Cloud.
+- A name for your Cloud email account (from name)
+- An email address to receive email replies (reply-to address)
 
 ## Configuring your email account
 
-_Admin settings > Settings > Email_
-
-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.
+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.
 
 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.
 
@@ -90,22 +50,22 @@ Here you'll set:
   - SSL
   - TLS
   - STARTTLS
-- **SMTP USERNAME**: Your SMTP account username.
-- **SMTP PASSWORD**: Your SMTP account password.
+- **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 replies to go to, if different from the From address.
+- **Reply-to address**: The email address you want the replies to go to, if different from the from address.
 
 ## Add recipients as CC or BCC
 
 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.
 
 ### 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.
+- 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
 
@@ -115,12 +75,12 @@ By default, Metabase will hide email recipients by including them in the BCC lis
 
 ### 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. [email protected])
-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.
+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. [email protected])
+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.
 
 ### Amazon SES
 
@@ -146,7 +106,7 @@ Check if [email quotas](https://docs.aws.amazon.com/ses/latest/dg/quotas.html) a
 
 Allowed email address domain(s) for new [dashboard subscriptions](../dashboards/subscriptions) and [alerts](../questions/alerts).
 
-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.
+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.
 
 To allow all domains, leave the field empty (allowing all domains is the default).
 

_docs/master/configuring-metabase/environment-variables.md

@@ -1722,6 +1722,15 @@ Maximum number of rows to return specifically on :rows type queries via the API.
 
 Must be less than 1048575, and less than the number configured in MB_AGGREGATED_QUERY_ROW_LIMIT. See also MB_AGGREGATED_QUERY_ROW_LIMIT.
 
+### `MB_UPDATE_CHANNEL`
+
+- Type: string
+- Default: `latest`
+- [Exported as](../installation-and-operation/serialization): `update-channel`.
+- [Configuration file name](./config-file): `update-channel`
+
+We'll notify you here when there's a new version of this type of release.
+
 ### `MB_UPLOADS_DATABASE_ID [DEPRECATED]`
 
 > DEPRECATED: 0.50.0