things are mostly working + copy all of latest

Author: escherize

_config.yml

@@ -19,14 +19,19 @@
 # in the templates via {{ site.myvariable }}.
 
 title: Metabase Docs
+
 email: info@metabase.com
+
 description: >- # this means to ignore newlines until "baseurl:"
-  Write an awesome description for your new site here. You can edit this
-  line in _config.yml. It will appear in your document head meta (for
-  Google search results) and in your feed.xml site description.
-baseurl: "" # the subpath of your site, e.g. /blog
-url: "" # the base hostname & protocol for your site, e.g. http://example.com
+  Metabase Documentation: your comprehensive guide to mastering business
+  intelligence, dashboards, and data visualization. Dive into detailed guides,
+  step-by-step tutorials, and best practices that empower you to leverage open
+  source, no SQL tools for uncovering insights and transforming data.
+
+url: "https://docs.metabase.com"
+
 twitter_username: metabase
+
 github_username: metabase
 
 highlighter: rogue
@@ -41,15 +46,6 @@ whitelist:
 
 markdown: kramdown
 
-# Exclude from processing.
-# The following items will not be processed, by default.
-# Any item listed under the `exclude:` key here will be automatically added to
-# the internal "default list".
-#
-# Excluded items can be processed by explicitly listing the directories or
-# their entries' file path in the `include:` list.
-#
-
 exclude:
   - .sass-cache/
   - .jekyll-cache/
@@ -75,4 +71,4 @@ defaults:
     values:
       layout: new-docs
       version: "latest"
-      permalink: "/:path/"
+      permalink: ":collection/:path"

_docs/latest/cloud/accounts-and-billing.md

@@ -0,0 +1,150 @@
+---
+title: Accounts and billing
+version: latest
+has_magic_breadcrumbs: true
+show_category_breadcrumb: true
+show_title_breadcrumb: true
+category: Cloud
+layout: new-docs
+latest: true
+---
+
+# Accounts and billing
+
+Managing billing and accounts in the Metabase Store.
+
+## Try out a free 14-day trial of Pro
+
+If you're on a [Starter](/product/starter) cloud plan, you can try out [all the features of Metabase Pro](/product/pro) for free for 14 days with no commitment.
+
+If you want to stick with Pro, you'll have the chance to upgrade. Otherwise, your plan will automatically switch back to Starter.
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. In the **Instances** section, select your instance.
+3. Click on **Try a free 14-day trial of Pro**.
+
+Once selected, the Store will display the status of your trial, along with a trial end date. We'll also send you an email with details about the trial.
+
+If you like the Pro features and want to upgrade, you'll need to upgrade your instance, either by clicking on the **Upgrade to Pro** button, or by managing your plan (see the next section).
+
+## Upgrade to Pro (or downgrade to Starter)
+
+If you'd like to switch plans:
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. In the **Instances** section, select the instance you want to change.
+3. Click on **Manage plan**.
+4. Select the plan you want.
+5. Click **Change plan**.
+
+## Add people to manage your Metabase Store account
+
+You can add people to your account to allow them to manage your Metabase Store account (not your Metabase instance).
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Go to **Settings**.
+3. Scroll to **Managers**.
+4. Enter email address of the person(s) you'd like to invite.
+5. The Store will send them an email prompting them to create a Metabase Store account.
+
+## Add people to receive billing and/or technical notifications
+
+You can include contacts to receive billing notifications, as well as technical notifications, like info about new Metabase releases.
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Go to **Settings**.
+3. Scroll to **Contacts**.
+4. Enter email address of the person(s) you'd like to invite.
+5. The Store will send them an email notifying them that they've been added to Metabase's contact list.
+
+## Cancel a subscription or trial
+
+To cancel a Starter or Pro plan directly in the Metabase Store:
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Go to **Instances**.
+3. Under the instance with the subscription that you want to cancel, click **Cancel subscription and delete instance**. If you're on an Enterprise plan, you'll need to [contact support](/help-premium).
+
+## Update payment information
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Billing**.
+3. Click on the payment method that you want to update.
+4. Enter new credit card information.
+5. Click on **Update**.
+
+If your Metabase was suspended due to a failed payment, the Store will automatically restore your Metabase upon a successful payment.
+
+## Switch to annual billing
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Go to **Instances**.
+3. Navigate to the instance you want to switch to annual billing.
+4. Click on **Manage plan** next to the plan name.
+5. Confirm the plan selection and toggle on **Switch to annual billing**.
+6. Click on **Switch plan**.
+
+Note that you cannot switch back to monthly billing until your annual cycle has completed.
+
+## Download past invoices
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Go to **Billing**.
+3. Scroll down to **Invoices** to view past or open invoices.
+
+## W-9 form requests
+
+See Metabase's updated [W9 form](/docs/w9).
+
+## Update your Tax ID
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Go to on **Billing**.
+3. Click on **Invoice Tax IDs**.
+4. Enter your country and Tax ID.
+5. Click **Save**.
+
+## Change the company name on invoices/receipts
+
+The primary account holder should request a name change by emailing [billing@metabase.com](mailto:billing@metabase.com).
+
+## Reset your Admin password
+
+If you need to reset your Admin password, [contact support](/help-premium).
+
+## Change your company name
+
+1. Navigate to your Metabase Store.
+2. Go to **Settings**.
+3. Click **Change company name**.
+
+## Change your billing address
+
+1. Navigate to your Metabase Store.
+2. Go to **Billing**.
+3. Click on **Billing address**.
+4. Update your billing address.
+5. Click **Save**.
+
+### Add or change your shipping address
+
+1. Navigate to your Metabase Store.
+2. Go to **Billing**.
+3. Click on **Shipping address**.
+4. Add or update your shipping address.
+5. Click **Save**.
+
+## Change the primary account holder
+
+If you need to change your primary account holder, for example if your primary account holder left your company:
+
+- If another person at your company holds a Metabase Store account, work with them to add you to your company's Metabase Store account.
+- If there is no other account holder, email [billing@metabase.com](mailto:billing@metabase.com) to request access to your company's Metabase Store account. Please note that if the primary account holder is unavailable, there is a 48-hour waiting period to process changes to Metabase Store accounts.
+
+## Move from Metabase Cloud to self-hosting Metabase
+
+If you're on Metabase Cloud but need to switch to hosting Metabase yourself, [contact us](/help-premium) and we'll give you a backup of your application database that you can use to restore Metabase on your own infrastructure.
+
+## Further reading
+
+- [How billing works](./how-billing-works)

_docs/latest/cloud/change-region.md

@@ -0,0 +1,48 @@
+---
+title: Changing which region your Metabase is hosted in
+version: latest
+has_magic_breadcrumbs: true
+show_category_breadcrumb: true
+show_title_breadcrumb: true
+category: Cloud
+layout: new-docs
+latest: true
+---
+
+# Changing which region your Metabase is hosted in
+
+You may want to change which region your Metabase is hosted in to bring it closer to the people using it
+
+- [Plan for some down time](#plan-for-some-down-time)
+- [Select a region](#select-a-region)
+- [Add the relevant IP addresses to your whitelist](#add-the-relevant-ip-addresses-to-your-whitelist)
+- [If your Metabase uses a custom domain, update your CNAMES](#if-your-metabase-uses-a-custom-domain-update-your-cnames)
+
+## Plan for some down time
+
+Most region switches should take less than 30 minutes. Your Metabase will be offline and unavailable while it changes regions, so plan for some down time.
+
+If you're using a [custom domain](./custom-domain), that region change could take longer, maybe up to 24 hours. That delay is due to DNS propagation (which is out of our hands).
+
+## Select a region
+
+To change regions, go to your [Metabase Store page](https://store.metabase.com/) and click on **Instances**. In the **Hosting regions** section, select the region you want to choose from:
+
+- US East (North Virginia)
+- Europe (Frankfurt)
+- Asia Pacific (Singapore)
+- South America (São Paulo)
+
+## Add the relevant IP addresses to your whitelist
+
+If you're using a security group or firewall rules, you should add the relevant [IP addresses](./ip-addresses-to-whitelist) to your whitelist.
+
+## If your Metabase uses a custom domain, update your CNAMES
+
+If your Metabase uses a [custom domain](./custom-domain), you'll need to update your CNAMES. DNS switches are generally fast these days, but it'll take some time to sign a new certificate for that domain once it's updated (up to 24 hours).
+
+We recommend switching regions during a time when people are less likely to use your Metabase.
+
+## Need help?
+
+No need to worry about backups (we have you covered), but if you run into any issues, contact support at [help@metabase.com](mailto:help@metabase.com).

_docs/latest/cloud/cloud-vs-self-hosting.md

@@ -0,0 +1,53 @@
+---
+title: Metabase Cloud versus self-hosting
+version: latest
+has_magic_breadcrumbs: true
+show_category_breadcrumb: true
+show_title_breadcrumb: true
+category: Cloud
+layout: new-docs
+latest: true
+---
+
+# Metabase Cloud versus self-hosting
+
+We have a post that goes into more depth on [why Metabase Cloud might be right for you](/blog/why-metabase-cloud), but here's a (nonexhaustive) table listing some of the differences between Metabase Cloud and self-hosting Metabase.
+
+|                                | Self-hosted OSS                     | Metabase Cloud     |
+| ------------------------------ | ----------------------------------- | ------------------ |
+| High availability servers      | ~\$48+/month                        | ✅                 |
+| Load balancer                  | ~\$12+/month                        | ✅                 |
+| Managed database               | ~\$40-60+/month                     | ✅                 |
+| SMTP server                    | ~\$12+/month                        | ✅                 |
+| Support                        | Forum only (paid plans get support) | Email with SLA     |
+| Up and running in minutes      | Manual                              | ✅                 |
+| Upgrades                       | Manual                              | ✅                 |
+| Multi-zone availability        | Manual                              | ✅                 |
+| Backups                        | Manual                              | ✅                 |
+| Monitoring                     | Manual                              | ✅                 |
+| Keep your own fork of the code | ✅                                  | ❌                 |
+| SoC2 Type 2 security auditing  | Manual                              | ✅                 |
+| SSL certificate                | Manual                              | ✅                 |
+| Where your money goes          | 3rd-party companies                 | Improving Metabase |
+
+Infrastructure costs are tricky to estimate, so keep in mind that the above self-hosting prices are ballpark estimates for a comparable setup with other cloud providers. If you _really_ know what you're doing, you can price out a cheaper setup, but then the services aren't managed and you don't get official support (which alone might make Cloud the better choice). We're just trying to provide an anchor to compare against for a similar production-grade setup, and anyway, you can always start out with Cloud and move to self-hosting whenever.
+
+## When _should_ you self-host?
+
+There are some cases where you _should_ self-host.
+
+- You need an [air-gapped environment](/product/air-gapping), usually for regulatory compliance, or if you’re running your own three-letter-agency… If you’re not sure if you need an air-gapped environment, you don’t need an air-gapped environment. If you do need an air-gap, we have an [air-gap offering as well](/talk-to-a-person/) (just not for Cloud, obviously).
+- You have some regulations that stipulate how you run your software (like HIPAA).
+- You want to run a custom build of Metabase. That is, you’re running a fork of Metabase (OSS or the Enterprise/Pro version) so you can add your own customizations to the software, and you have the engineering resources to tank that level of overhead.
+- You want to use a community or custom driver. We only support [official (1st-party) and partner drivers](/docs/latest/databases/connecting#connecting-to-supported-databases) on Metabase Cloud, because we need to be able to vouch for their quality and help you with problems in a production context.
+
+Otherwise, you're better off having us handle all of the overhead so you can focus on your business. The official support alone is probably worth it.
+
+## Metabase Pro and Enterprise
+
+Metabase also has a paid version that ships with all of the bells and whistles (SSO, row-level permissions, customization, and a lot more). Plans with this version include:
+
+- [Metabase Pro](/product/pro)
+- [Metabase Enterprise](/product/enterprise)
+
+You can self-host this paid version, or have have us host it for you on Metabase Cloud for no additional cost. We don't charge more because we believe you'll have such a better experience that it'll be easier for us to support you.

_docs/latest/cloud/custom-domain.md

@@ -0,0 +1,62 @@
+---
+title: Changing your domain name
+version: latest
+has_magic_breadcrumbs: true
+show_category_breadcrumb: true
+show_title_breadcrumb: true
+category: Cloud
+layout: new-docs
+redirect_from:
+  - /cloud/docs/custom-domain
+latest: true
+---
+
+# Changing your domain name
+
+By default, Metabase will automatically provision a domain name for your Metabase that ends in metabaseapp.com (e.g., yourcompany.metabaseapp.com).
+
+[Pro and Enterprise](/pricing/) plans allow you to add a custom domain. Setting a custom domain will update your instance's [Site URL](/docs/latest/configuring-metabase/settings#site-url). The Site URL is used for things like creating links in emails, auth redirects, and in some embedding scenarios.
+
+## How to add a custom domain to your Metabase
+
+1. Log in to your [Metabase Store account](https://store.metabase.com/).
+
+2. Find the Metabase instance that you want to add the custom domain to, and select **Manage** on the bottom right of the instance's card. Then click on the **Domains** tab.
+
+   You'll see something like this:
+
+   ![Metabase instance domains tab](./images/domains-tab.png)
+
+3. In the custom domain field (the input prefixed with `https://` in the Metabase Store), enter your custom domain (e.g., your.custom.domain).
+4. Talk to whoever manages your Domain Name System (DNS) records, and have them add a CNAME to wherever you manage your DNS records. Point that CNAME to this URL:
+
+   ```url
+   us-1.cd.metabaseapp.com
+   ```
+
+   So your CNAME record would look something like:
+
+   ```domain
+   CNAME    your.custom.domain    us-1.cd.metabaseapp.com
+   ```
+
+   Just to be clear: you don't enter this record in the Metabase Store; you enter it in wherever you manage your DNS records.
+
+5. If you've already set up SSO (like SAML or LDAP) for your Metabase, you'll need to update the return URL in your identity provider configuration to include this new custom domain.
+
+That's it. You may need to wait a bit for the CNAME to update (this delay is specific to how DNS works, and not something Metabase has control over). Metabase will take care of the rest: we'll make sure that:
+
+- the URL directs people to your Metabase,
+- your domain has SSL certificates set up to serve your instance over HTTPS to the new domain,
+- and that your [metabase.com/cloud/login](/cloud/login) works as expected.
+
+You'll still be able to access your original, automatically provisioned domain (e.g., yourcompany.metabaseapp.com), so existing embedded links should continue to work.
+
+## Why you'd want to use a custom domain
+
+- **White-labeling polish**: If you're white labeling Metabase, a custom domain adds another bit of polish that abstracts Metabase away from the experience you deliver to your customers.
+- **Consistency**: you may have several internal tools that follow a pattern, e.g., crm.yourcompany.com, ops.yourcompany.com, etc., and you want something like stats.yourcompany.com for your Metabase.
+
+## Change the name of your Metabase (your DNS alias)
+
+Log in to your Metabase Store account and go to **Instances** > **DNS Alias**, where you can update your alias.