diff --git a/_data/shared_chrome.json b/_data/shared_chrome.json
index 52a6c8b899..788502209d 100644
--- a/_data/shared_chrome.json
+++ b/_data/shared_chrome.json
@@ -1,7 +1,7 @@
{
"$schema": "https://www.metabase.com/shared/chrome.schema.json",
"version": 1,
- "generated_at": "2026-06-03T19:12:22+00:00",
+ "generated_at": "2026-06-04T19:06:53+00:00",
"origin": "https://www.metabase.com",
"stylesheets": [
{
diff --git a/_docs/latest/cloud/accounts-and-billing.md b/_docs/latest/cloud/accounts-and-billing.md
index 38c1793dbb..d4f3a1e3a7 100644
--- a/_docs/latest/cloud/accounts-and-billing.md
+++ b/_docs/latest/cloud/accounts-and-billing.md
@@ -15,57 +15,50 @@ latest: true
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:
+To switch your plan:
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**.
+3. Click **Manage plan**.
4. Select the plan you want.
5. Click **Change plan**.
-## Add people to manage your Metabase Store account
+## Add managers
-You can add people to your account to allow them to manage your Metabase Store account (not your Metabase instance).
+To invite users to manage your Metabase Store account:
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.
+2. Navigate to **Settings**.
+3. Find the **Managers** section.
+4. In the **Invite managers** field, enter the email address of each user you want to invite.
+5. Metabase sends them an email prompting them to create a Metabase Store account.
+
+> This action adds each invited user as a manager of your Metabase Store account only, not as a user of your Metabase instance.
-## Add people to receive billing and/or technical notifications
+## Add contacts to receive billing or technical notifications
-You can include contacts to receive billing notifications, as well as technical notifications, like info about new Metabase releases.
+To add contacts who receive billing or technical notifications:
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.
+2. Navigate to **Settings**.
+3. Find the **Contacts** section.
+4. In the **Add contacts** field, enter the email address of each contact you want to add.
+5. In the **Email type** dropdown, choose between **All**, **Billing**, and **Technical**.
+6. Click **Add**.
+7. Metabase sends each contact an email notifying them that they've been added to your contact list.
## Cancel a subscription or trial
-To cancel a Starter or Pro plan directly in the Metabase Store:
+To cancel a Starter or Pro plan:
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).
+2. Navigate to **Instances**.
+3. In the instance you want to cancel, click **Settings**.
+4. Click **Cancel subscription and delete instance**. If you have an Enterprise plan, [contact support](/help-premium).
+5. Optional: let us know why you're cancelling so we can improve Metabase. Click **Share feedback**, or click **Skip**.
+6. To confirm, click **Yes, cancel**.
## Update payment information
@@ -79,14 +72,15 @@ If your Metabase was suspended due to a failed payment, the Store will automatic
## Switch to annual billing
+To 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**.
+2. Navigate to **Instances**.
+3. In the instance you want to switch, click **Manage plan**.
+4. Enable the **Switch to annual billing** toggle.
+5. Click **Change plan**.
-Note that you cannot switch back to monthly billing until your annual cycle has completed.
+> You can't switch back to monthly billing until your annual cycle has completed.
## Download past invoices
@@ -101,9 +95,9 @@ See Metabase's updated [W9 form](/files/2024_W9_signed.pdf).
## Update your Tax ID
1. Log in to your Metabase [Store account](https://store.metabase.com).
-2. Go to **Billing**.
-3. Click on **Invoice Tax IDs**.
-4. Enter your country and Tax ID.
+2. Navigate to **Billing**.
+3. Find the **Payment details** section.
+4. In the **Invoice Tax IDs** field, select your country from the drop-down and enter your Tax ID.
5. Click **Save**.
## Change the company name on invoices/receipts
@@ -116,24 +110,26 @@ 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**.
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Settings**.
+3. Find the **Company name** section.
+4. In the **Change company name** field, enter a new company name.
+5. Click **Update**.
## Change your billing address
-1. Navigate to your Metabase Store.
-2. Go to **Billing**.
-3. Click on **Billing address**.
-4. Update your billing address.
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Billing**.
+3. Find the **Payment details** section.
+4. In the **Billing address** field, enter your new billing address.
5. Click **Save**.
-### Add or change your shipping address
+## 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.
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Billing**.
+3. Find the **Payment details** section.
+4. In the **Shipping address** field, add or update your shipping address.
5. Click **Save**.
## Change the primary account holder
diff --git a/_docs/latest/cloud/change-region.md b/_docs/latest/cloud/change-region.md
index ee170133e3..560921169a 100644
--- a/_docs/latest/cloud/change-region.md
+++ b/_docs/latest/cloud/change-region.md
@@ -27,13 +27,16 @@ If you're using a [custom domain](./custom-domain), that region change could tak
## 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)
-- Asia Pacific (Sydney)
-- South America (São Paulo)
+To change which region your Metabase is hosted in:
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Instances**.
+3. In the instance you want to change, click **Settings**.
+4. Find the **Hosting region** section.
+5. Select the region you want:
+ - US West (Oregon)
+ - Europe (Frankfurt)
+6. Click **Change region**.
## Add the relevant IP addresses to your whitelist
diff --git a/_docs/latest/cloud/custom-domain.md b/_docs/latest/cloud/custom-domain.md
index 26eb427cfc..f04124e3f8 100644
--- a/_docs/latest/cloud/custom-domain.md
+++ b/_docs/latest/cloud/custom-domain.md
@@ -18,40 +18,39 @@ By default, Metabase will automatically provision a domain name for your Metabas
[Pro and Enterprise](/pricing/) plans allow you to add a custom domain. Setting a custom domain will update your instance's [Site URL](../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
+## Add a custom domain to your Metabase
-1. Log in to your [Metabase Store account](https://store.metabase.com/).
+To add a custom domain to your Metabase:
-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.
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Instances**.
+3. In the instance you want to add the custom domain to, click **Settings**.
+4. Find the **Custom domain** section.
+5. Enter your custom domain (e.g., `your.custom.domain`).
+6. Click **Update**.
+7. Ask the manager of your Domain Name System (DNS) records to add a CNAME pointing to:
- You'll see something like this:
-
- 
-
-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.
+ > Enter this record where you manage your DNS records, not in the Metabase Store
-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.
+8. If you've already set up SSO (like SAML or LDAP) for your Metabase, update the return URL in your identity provider configuration to include the 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:
+You may need to wait for the CNAME to update (this delay is specific to how DNS works, not something Metabase has control over). Metabase takes care of the rest, making 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.
+- The URL directs users to your Metabase.
+- Your domain has SSL certificates set up to serve your instance over HTTPS to the new domain.
+- 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.
+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
@@ -60,7 +59,13 @@ You'll still be able to access your original, automatically provisioned domain (
## 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.
+To change your DNS alias:
+
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Instances**.
+3. Find the **DNS Alias** section.
+4. Enter your new alias.
+5. Click **Update**.
## Custom SMTP server
diff --git a/_docs/latest/cloud/google-sheets.md b/_docs/latest/cloud/google-sheets.md
index 872db84a19..4226609e34 100644
--- a/_docs/latest/cloud/google-sheets.md
+++ b/_docs/latest/cloud/google-sheets.md
@@ -102,4 +102,4 @@ To check how much storage you're using:
The quota numbers update every 6 hours, so there might be a slight delay. Once you hit your quota limit, you won't be able to upload/sync more data until you either free up some space or increase your storage.
-To store more rows, see [increasing Metabase Cloud storage](./storage#increasing-metabase-cloud-storage).
+To store more rows, see [increase Metabase Cloud storage](./storage#increase-metabase-cloud-storage).
diff --git a/_docs/latest/cloud/storage.md b/_docs/latest/cloud/storage.md
index 6b686f0857..071baa0fdf 100644
--- a/_docs/latest/cloud/storage.md
+++ b/_docs/latest/cloud/storage.md
@@ -44,44 +44,47 @@ New customers can sign up for a [Metabase Cloud instance with storage](https://s
### Existing cloud customers
-Current customers can add storage through the Metabase Store:
+To add storage to an existing instance, use the following steps.
-1. Log in to the [Metabase Store](https://store.metabase.com/).
-2. In the **Instances** section, click **Add Storage** for the instance you'd like to add storage to.
-3. Choose how much storage you would like to add. You can start with 500K stored rows per month and add more storage later.
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Instances**.
+3. In the instance you want to add storage to, click **Manage plan**.
+4. Find the **Manage add-ons** section.
+5. In the **Storage** field, click **Enable**.
+6. Use the slider to select the number of stored rows you want to add.
+7. Click **Add storage**.
## Metabase Cloud Storage pricing
Pricing depends on how much data you need to store. See the Storage section on our [pricing page](/pricing/).
-## Increasing Metabase Cloud Storage
+### Increase Metabase Cloud Storage
-To increase the number of rows you can store:
+To increase the number of stored rows, use the following steps:
-1. Log in to your [Metabase Store account](https://store.metabase.com/)
-2. In the **Instances** tab, navigate to the relevant instance.
-3. Click on **Manage storage**.
-4. Click **Edit**.
-5. Click **Add storage**.
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Instances**.
+3. In the instance you want to increase storage for, click **Manage plan**.
+4. Find the **Manage add-ons** section.
+5. In the **Storage** field, click **Manage**.
+6. Click **Edit**.
+7. Use the slider to increase the number of stored rows.
+8. Click **Add storage**.
-You can select from the following row counts:
+## Delete Metabase Cloud Storage
-- 500K
-- 1M
-- 5M
-- 10M
-- 20M
+> **WARNING:** This action permanently erases all data in your Metabase Cloud Storage.
-## Deleting Metabase Cloud Storage
+To remove Metabase Cloud Storage, use the following steps:
-To remove Metabase Cloud Storage (which will _permanently_ erase all its data):
-
-1. Log in to your [Metabase Store account](https://store.metabase.com/)
-2. In the **Instances** tab, navigate to the relevant instance.
-3. Click **Manage storage**.
-4. Click **Edit**.
-5. Click **Disable storage**.
-6. Click **Erase all data**, which---**WARNING**--will erase _all of its data_. We won't be able to recover the data, so only do this if you're certain you no longer need the storage and its data.
+1. Log in to your Metabase [Store account](https://store.metabase.com).
+2. Navigate to **Instances**.
+3. In the instance you want to delete storage from, click **Manage plan**.
+4. Find the **Manage add-ons** section.
+5. In the **Storage** field, click **Manage**.
+6. Click **Edit**.
+7. Click **Disable storage**.
+8. To confirm, click **Erase all data**.
## Syncing Google Sheets with Metabase
diff --git a/_docs/latest/data-studio/transforms/addons.md b/_docs/latest/data-studio/transforms/addons.md
index 9df72c4017..e61c504b23 100644
--- a/_docs/latest/data-studio/transforms/addons.md
+++ b/_docs/latest/data-studio/transforms/addons.md
@@ -49,7 +49,7 @@ With basic transforms, you can:
- **Metabase Cloud**: Basic transform functionality on Metabase Cloud - Starter, Pro, or Enterprise - comes with an additional small fee per successful transform run, see [Pricing](/pricing).
- Only people logged in with an email of a [Metabase Store admins](../../cloud/accounts-and-billing#add-people-to-manage-your-metabase-store-account) (not just Metabase _instance_ admins) can enable basic transforms. To enable Basic transforms on Metabase Cloud, see [Enable transforms](./transforms-overview#enable-transforms).
+ Only people logged in with an email of a [Metabase Store admin](../../cloud/accounts-and-billing#add-managers) (not just Metabase _instance_ admins) can [enable basic transforms](./transforms-overview#enable-transforms).
### Cancel basic transforms
@@ -81,7 +81,7 @@ There are two ways to enable Advanced transforms:
- **From your Metabase instance**: you can navigate to a feature requiring advanced transforms (like Python transforms or transform inspector), and follow the prompts to upgrade.
- To enable Advanced transforms from your Metabase instance, you need to be logged into the instance with the same email as a [Metabase Store admin](../../cloud/accounts-and-billing#add-people-to-manage-your-metabase-store-account), because Advanced transform incur an additional charge.
+ To enable Advanced transforms from your Metabase instance, you need to be logged into the instance with the same email as a [Metabase Store admin](../../cloud/accounts-and-billing#add-managers), because Advanced transform incur an additional charge.
- **From [Metabase Store](https://store.metabase.com)**:
diff --git a/_docs/latest/data-studio/transforms/transforms-overview.md b/_docs/latest/data-studio/transforms/transforms-overview.md
index 15eb7ffc0a..7fe9dcd715 100644
--- a/_docs/latest/data-studio/transforms/transforms-overview.md
+++ b/_docs/latest/data-studio/transforms/transforms-overview.md
@@ -71,7 +71,7 @@ Permission configuration for transform depends on your plan.
Before you can start writing transforms, you'll need to enable transforms in your Metabase instance.
-If you are on a Metabase Cloud plan, only people logged in with an email of a [Metabase Store admins](../../cloud/accounts-and-billing#add-people-to-manage-your-metabase-store-account) (not just Metabase _instance_ admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.
+If you're on a Metabase Cloud plan, only people logged in with an email of a [Metabase Store admin](../../cloud/accounts-and-billing#add-managers) (not just Metabase _instance_ admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.
To enable transforms:
diff --git a/_docs/latest/questions/images/drill-through-column-header-menu.png b/_docs/latest/questions/images/drill-through-column-header-menu.png
new file mode 100644
index 0000000000..58d0607cd3
Binary files /dev/null and b/_docs/latest/questions/images/drill-through-column-header-menu.png differ
diff --git a/_docs/latest/questions/visualizations/drill-through.md b/_docs/latest/questions/visualizations/drill-through.md
new file mode 100644
index 0000000000..41898845a7
--- /dev/null
+++ b/_docs/latest/questions/visualizations/drill-through.md
@@ -0,0 +1,170 @@
+---
+version: v0.61
+has_magic_breadcrumbs: true
+show_category_breadcrumb: true
+show_title_breadcrumb: true
+category: Questions
+title: Drill-through
+source_url: >-
+ https://github.com/metabase/metabase/blob/master/docs/questions/visualizations/drill-through.md
+layout: new-docs
+summary: >-
+ Click on charts, column headers, and table cells to filter, zoom in, see
+ underlying records, and break out by time, location, or category.
+latest: true
+---
+
+# Drill-through
+
+Drill-through lets you explore data in your Metabase by clicking a chart, a column header, or a table cell. Each click opens a menu with options like **Filter by this value**, **See these records**, **Break out by**, and **Zoom in**. Selecting one of these options generates a new query and visualizes the result.
+
+
+
+## How drill-through works
+
+Every drill-through action creates a new query and visualizes the result. Metabase takes the original query and modifies it based on what you click. Switch to the editor to see and edit the new query.
+
+For example, say a bar chart shows order counts summarized by product category and month. Click the April bar in the Widgets series, then select **See these orders**. Metabase creates a new question that filters the orders to Widgets in April.
+
+Some things to keep in mind:
+
+- **Drill-through requires query-building permissions.** You must have permission to create queries on the underlying data to see the drill-through menu.
+- **The drill-through does not modify the original question.** Drill-through creates a new question without overwriting or modifying your original question.
+- **The menu options depend on the type of data you click.** Different options appear in the action menu depending on whether you click a chart, a column header, a table cell, or a point on a map.
+
+## Drill-through types
+
+There are two types of drill-through:
+
+- **Results-based drill-through:** Metabase takes the data in the query result and filters, distributes, or otherwise transforms it. Example options include **Filter by this value**, **Distribution**, and **Sort**. You can perform results-based drill-through on questions built with the query builder or native SQL.
+- **Query-rewriting drill-through:** Metabase modifies your query. Example options include **See these records**, **Break out by**, and **Zoom in**. You can only perform query-rewriting drill-through on questions built with the query builder.
+
+## Drill-through options
+
+The drill-through menu options depend on what you click and on the underlying data.
+
+### Tables
+
+To drill-through a table, click either:
+
+* Column headers
+* Table cells
+
+#### Column headers
+
+
+
+| Option | When it appears |
+| --------------------------------------------------- | ------------------------------------------------------------------------ |
+| **Filter by this column** | Any column |
+| **Sort** | Any column except JSON |
+| **Distribution** | Any column except primary keys, JSON, or description and comment fields |
+| **Sum / Average** | Numeric columns when the query isn't summarized |
+| **Distinct values** | Any column when the query isn't summarized |
+| **Sum over time** | Numeric columns when the query has a date column and isn't summarized |
+| **Extract domain, host…** / **Extract day, month…** | URL, email, and date columns |
+| **Combine columns** | Text columns |
+
+#### Table cells
+
+| Option | When it appears |
+| --------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| **Filter by this value** | Any column except primary keys and foreign keys |
+| **View details** | Rows that have a primary key |
+| **View this [related record]** | Foreign key values |
+| **View these [related rows]** | Foreign key values |
+| **View these records** | Aggregated values |
+| **Break out by [time / location / category]** | Aggregated values |
+| **Automatic insights** | Summarized queries, when [X-rays](../../exploration-and-organization/x-rays) are enabled |
+
+### Charts
+
+To drill-through a chart, click either:
+
+* Data points
+* Legend items
+
+> [Pivoted tables](./table#pivoted-tables) behave like charts. Cells in pivoted tables offer the same options as data points. This is different from the [pivot table visualization](./pivot-table), which offers a smaller subset of drill-through options.
+
+#### Data points
+
+| Option | When it appears |
+| --------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| **Filter by this value** | Any column except primary keys and foreign keys |
+| **View these records** | Aggregated values |
+| **Break out by [time / location / category]** | Aggregated values |
+| **Automatic insights** | Summarized queries, when [X-rays](../../exploration-and-organization/x-rays) are enabled |
+| **Zoom in** | Histograms, binned charts, and maps |
+| **See this [period] by [smaller period]** | Time series |
+
+On a time series or other chart with a continuous axis, click and drag across a range to filter the question to those values. This works like **Filter by this value**, but for a range of data instead of a single data point.
+
+#### Legend items
+
+Clicking the colored circle on a legend item toggles the series on or off. Clicking the label on the legend item opens the drill-through menu.
+
+Drill-through on a legend item applies to the entire series, not just one data point. For example, clicking **View these records** on a legend item shows all the rows for that series across the whole chart.
+
+| Option | When it appears |
+| --------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| **View these records** | Aggregated values |
+| **Break out by [time / location / category]** | Aggregated values |
+| **Automatic insights** | Summarized queries, when [X-rays](../../exploration-and-organization/x-rays) are enabled |
+| **Zoom in** | Histograms, binned charts, and maps |
+| **See this [period] by [smaller period]** | Time series |
+
+## Drill-through and native SQL
+
+When you create a query with the query builder, Metabase can read and modify your query for any drill-through action.
+
+When you write a query with the native SQL editor, Metabase runs your query but doesn't parse it. It can modify the results, but it can't modify the query itself. This means you can use results-based drill-through, but not query-rewriting drill-through. For example:
+
+| Works on native SQL questions | Doesn't work on native SQL questions |
+| ----------------------------- | ------------------------------------ |
+| **Filter by this value** | **See these records** |
+| **Distribution** | **Break out by** |
+| **Sort** | **Zoom in** |
+
+> To use drill-through on a native SQL question, you must save the question.
+
+For more information, see [drill-through types](#drill-through-types).
+
+### Make native SQL questions interactive
+
+Drill-through can't rewrite a native SQL query, but you can still make a native SQL chart interactive using [custom click behavior](../../dashboards/interactive#customizing-click-behavior). Add the question to a dashboard, and set a click behavior on the card.
+
+A custom click behavior replaces the drill-through menu with an action you define. It can send you to another question, dashboard, external URL, or update a filter on the current dashboard. Set a [dashboard filter](../../dashboards/filters) to the clicked value to scope the destination.
+
+### Combine native SQL with full drill-through
+
+If you need native SQL but also want to use the full drill-through menu, write your SQL query as a [transform](../../data-studio/transforms/transforms-overview) and build the user-facing question with the query builder.
+
+Write the transform's SQL to return the individual records, not summarized results. Build questions on the transform's table with the query builder. These questions support the full drill-through menu.
+
+Drill-through actions can only reach data that the transform's table contains.
+
+> To create transforms, you must have transform permissions. If you use Metabase Cloud, you must also have the [transform add-on](../../data-studio/transforms/addons).
+
+## Drill-through and embedding
+
+Drill-through behavior depends on the [embedding type](../../embedding/start), because drill-through requires a Metabase user with query permissions.
+
+| Embedding type | Drill-through |
+| ----------------------------------- | ----------------------------------------------------- |
+| **Authenticated modular embedding** | Full drill-through, scoped to the user's permissions |
+| **Guest modular embeds** | No drill-through |
+| **Full app embedding** | Full drill-through |
+| **Public embeds** | No drill-through |
+
+To turn off drill-through in modular embedding, use the **Allow people to drill through on data points** setting when you create the embed. In a dashboard, override drill-through on a single card with [custom click behavior](../../dashboards/interactive).
+
+Use [modular embedding SDK plugins](../../embedding/sdk/introduction) to customize some drill-through menu options and click behavior in embedded apps.
+
+## Alternatives to drill-through
+
+On a dashboard, you can replace drill-through with a different click action:
+
+- **[Custom click behavior](../../dashboards/interactive#customizing-click-behavior):** Send users to another question, dashboard, external URL, or update a filter on the current dashboard
+- **[Cross-filtering](../../dashboards/interactive#use-a-chart-to-filter-a-dashboard):** Update a filter on cards across a dashboard
+
+Setting one of these alternatives on a card replaces the drill-through menu for that card.
diff --git a/_docs/v0.61/data-studio/transforms/addons.md b/_docs/v0.61/data-studio/transforms/addons.md
index efd75366ee..c78c65424d 100644
--- a/_docs/v0.61/data-studio/transforms/addons.md
+++ b/_docs/v0.61/data-studio/transforms/addons.md
@@ -44,7 +44,7 @@ With basic transforms, you can:
- **Metabase Cloud**: Basic transform functionality on Metabase Cloud - Starter, Pro, or Enterprise - comes with an additional small fee per successful transform run, see [Pricing](/pricing).
- Only people logged in with an email of a [Metabase Store admins](../../cloud/accounts-and-billing#add-people-to-manage-your-metabase-store-account) (not just Metabase _instance_ admins) can enable basic transforms. To enable Basic transforms on Metabase Cloud, see [Enable transforms](./transforms-overview#enable-transforms).
+ Only people logged in with an email of a [Metabase Store admin](../../cloud/accounts-and-billing#add-managers) (not just Metabase _instance_ admins) can [enable basic transforms](./transforms-overview#enable-transforms).
### Cancel basic transforms
@@ -76,7 +76,7 @@ There are two ways to enable Advanced transforms:
- **From your Metabase instance**: you can navigate to a feature requiring advanced transforms (like Python transforms or transform inspector), and follow the prompts to upgrade.
- To enable Advanced transforms from your Metabase instance, you need to be logged into the instance with the same email as a [Metabase Store admin](../../cloud/accounts-and-billing#add-people-to-manage-your-metabase-store-account), because Advanced transform incur an additional charge.
+ To enable Advanced transforms from your Metabase instance, you need to be logged into the instance with the same email as a [Metabase Store admin](../../cloud/accounts-and-billing#add-managers), because Advanced transform incur an additional charge.
- **From [Metabase Store](https://store.metabase.com)**:
diff --git a/_docs/v0.61/data-studio/transforms/transforms-overview.md b/_docs/v0.61/data-studio/transforms/transforms-overview.md
index 6877e3bf8b..4b244cb277 100644
--- a/_docs/v0.61/data-studio/transforms/transforms-overview.md
+++ b/_docs/v0.61/data-studio/transforms/transforms-overview.md
@@ -67,7 +67,7 @@ Permission configuration for transform depends on your plan.
Before you can start writing transforms, you'll need to enable transforms in your Metabase instance.
-If you are on a Metabase Cloud plan, only people logged in with an email of a [Metabase Store admins](../../cloud/accounts-and-billing#add-people-to-manage-your-metabase-store-account) (not just Metabase _instance_ admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.
+If you're on a Metabase Cloud plan, only people logged in with an email of a [Metabase Store admin](../../cloud/accounts-and-billing#add-managers) (not just Metabase _instance_ admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.
To enable transforms:
diff --git a/_docs/v0.61/questions/images/drill-through-column-header-menu.png b/_docs/v0.61/questions/images/drill-through-column-header-menu.png
new file mode 100644
index 0000000000..58d0607cd3
Binary files /dev/null and b/_docs/v0.61/questions/images/drill-through-column-header-menu.png differ
diff --git a/_docs/v0.61/questions/visualizations/drill-through.md b/_docs/v0.61/questions/visualizations/drill-through.md
new file mode 100644
index 0000000000..84d59bc4a7
--- /dev/null
+++ b/_docs/v0.61/questions/visualizations/drill-through.md
@@ -0,0 +1,166 @@
+---
+version: v0.61
+has_magic_breadcrumbs: true
+show_category_breadcrumb: true
+show_title_breadcrumb: true
+category: Questions
+title: Drill-through
+source_url: 'https://github.com/metabase/metabase/blob/master/docs/questions/visualizations/drill-through.md'
+layout: new-docs
+summary: 'Click on charts, column headers, and table cells to filter, zoom in, see underlying records, and break out by time, location, or category.'
+---
+
+# Drill-through
+
+Drill-through lets you explore data in your Metabase by clicking a chart, a column header, or a table cell. Each click opens a menu with options like **Filter by this value**, **See these records**, **Break out by**, and **Zoom in**. Selecting one of these options generates a new query and visualizes the result.
+
+
+
+## How drill-through works
+
+Every drill-through action creates a new query and visualizes the result. Metabase takes the original query and modifies it based on what you click. Switch to the editor to see and edit the new query.
+
+For example, say a bar chart shows order counts summarized by product category and month. Click the April bar in the Widgets series, then select **See these orders**. Metabase creates a new question that filters the orders to Widgets in April.
+
+Some things to keep in mind:
+
+- **Drill-through requires query-building permissions.** You must have permission to create queries on the underlying data to see the drill-through menu.
+- **The drill-through does not modify the original question.** Drill-through creates a new question without overwriting or modifying your original question.
+- **The menu options depend on the type of data you click.** Different options appear in the action menu depending on whether you click a chart, a column header, a table cell, or a point on a map.
+
+## Drill-through types
+
+There are two types of drill-through:
+
+- **Results-based drill-through:** Metabase takes the data in the query result and filters, distributes, or otherwise transforms it. Example options include **Filter by this value**, **Distribution**, and **Sort**. You can perform results-based drill-through on questions built with the query builder or native SQL.
+- **Query-rewriting drill-through:** Metabase modifies your query. Example options include **See these records**, **Break out by**, and **Zoom in**. You can only perform query-rewriting drill-through on questions built with the query builder.
+
+## Drill-through options
+
+The drill-through menu options depend on what you click and on the underlying data.
+
+### Tables
+
+To drill-through a table, click either:
+
+* Column headers
+* Table cells
+
+#### Column headers
+
+
+
+| Option | When it appears |
+| --------------------------------------------------- | ------------------------------------------------------------------------ |
+| **Filter by this column** | Any column |
+| **Sort** | Any column except JSON |
+| **Distribution** | Any column except primary keys, JSON, or description and comment fields |
+| **Sum / Average** | Numeric columns when the query isn't summarized |
+| **Distinct values** | Any column when the query isn't summarized |
+| **Sum over time** | Numeric columns when the query has a date column and isn't summarized |
+| **Extract domain, host…** / **Extract day, month…** | URL, email, and date columns |
+| **Combine columns** | Text columns |
+
+#### Table cells
+
+| Option | When it appears |
+| --------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| **Filter by this value** | Any column except primary keys and foreign keys |
+| **View details** | Rows that have a primary key |
+| **View this [related record]** | Foreign key values |
+| **View these [related rows]** | Foreign key values |
+| **View these records** | Aggregated values |
+| **Break out by [time / location / category]** | Aggregated values |
+| **Automatic insights** | Summarized queries, when [X-rays](../../exploration-and-organization/x-rays) are enabled |
+
+### Charts
+
+To drill-through a chart, click either:
+
+* Data points
+* Legend items
+
+> [Pivoted tables](./table#pivoted-tables) behave like charts. Cells in pivoted tables offer the same options as data points. This is different from the [pivot table visualization](./pivot-table), which offers a smaller subset of drill-through options.
+
+#### Data points
+
+| Option | When it appears |
+| --------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| **Filter by this value** | Any column except primary keys and foreign keys |
+| **View these records** | Aggregated values |
+| **Break out by [time / location / category]** | Aggregated values |
+| **Automatic insights** | Summarized queries, when [X-rays](../../exploration-and-organization/x-rays) are enabled |
+| **Zoom in** | Histograms, binned charts, and maps |
+| **See this [period] by [smaller period]** | Time series |
+
+On a time series or other chart with a continuous axis, click and drag across a range to filter the question to those values. This works like **Filter by this value**, but for a range of data instead of a single data point.
+
+#### Legend items
+
+Clicking the colored circle on a legend item toggles the series on or off. Clicking the label on the legend item opens the drill-through menu.
+
+Drill-through on a legend item applies to the entire series, not just one data point. For example, clicking **View these records** on a legend item shows all the rows for that series across the whole chart.
+
+| Option | When it appears |
+| --------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| **View these records** | Aggregated values |
+| **Break out by [time / location / category]** | Aggregated values |
+| **Automatic insights** | Summarized queries, when [X-rays](../../exploration-and-organization/x-rays) are enabled |
+| **Zoom in** | Histograms, binned charts, and maps |
+| **See this [period] by [smaller period]** | Time series |
+
+## Drill-through and native SQL
+
+When you create a query with the query builder, Metabase can read and modify your query for any drill-through action.
+
+When you write a query with the native SQL editor, Metabase runs your query but doesn't parse it. It can modify the results, but it can't modify the query itself. This means you can use results-based drill-through, but not query-rewriting drill-through. For example:
+
+| Works on native SQL questions | Doesn't work on native SQL questions |
+| ----------------------------- | ------------------------------------ |
+| **Filter by this value** | **See these records** |
+| **Distribution** | **Break out by** |
+| **Sort** | **Zoom in** |
+
+> To use drill-through on a native SQL question, you must save the question.
+
+For more information, see [drill-through types](#drill-through-types).
+
+### Make native SQL questions interactive
+
+Drill-through can't rewrite a native SQL query, but you can still make a native SQL chart interactive using [custom click behavior](../../dashboards/interactive#customizing-click-behavior). Add the question to a dashboard, and set a click behavior on the card.
+
+A custom click behavior replaces the drill-through menu with an action you define. It can send you to another question, dashboard, external URL, or update a filter on the current dashboard. Set a [dashboard filter](../../dashboards/filters) to the clicked value to scope the destination.
+
+### Combine native SQL with full drill-through
+
+If you need native SQL but also want to use the full drill-through menu, write your SQL query as a [transform](../../data-studio/transforms/transforms-overview) and build the user-facing question with the query builder.
+
+Write the transform's SQL to return the individual records, not summarized results. Build questions on the transform's table with the query builder. These questions support the full drill-through menu.
+
+Drill-through actions can only reach data that the transform's table contains.
+
+> To create transforms, you must have transform permissions. If you use Metabase Cloud, you must also have the [transform add-on](../../data-studio/transforms/addons).
+
+## Drill-through and embedding
+
+Drill-through behavior depends on the [embedding type](../../embedding/start), because drill-through requires a Metabase user with query permissions.
+
+| Embedding type | Drill-through |
+| ----------------------------------- | ----------------------------------------------------- |
+| **Authenticated modular embedding** | Full drill-through, scoped to the user's permissions |
+| **Guest modular embeds** | No drill-through |
+| **Full app embedding** | Full drill-through |
+| **Public embeds** | No drill-through |
+
+To turn off drill-through in modular embedding, use the **Allow people to drill through on data points** setting when you create the embed. In a dashboard, override drill-through on a single card with [custom click behavior](../../dashboards/interactive).
+
+Use [modular embedding SDK plugins](../../embedding/sdk/introduction) to customize some drill-through menu options and click behavior in embedded apps.
+
+## Alternatives to drill-through
+
+On a dashboard, you can replace drill-through with a different click action:
+
+- **[Custom click behavior](../../dashboards/interactive#customizing-click-behavior):** Send users to another question, dashboard, external URL, or update a filter on the current dashboard
+- **[Cross-filtering](../../dashboards/interactive#use-a-chart-to-filter-a-dashboard):** Update a filter on cards across a dashboard
+
+Setting one of these alternatives on a card replaces the drill-through menu for that card.
diff --git a/_site/docs/latest/cloud/accounts-and-billing.html b/_site/docs/latest/cloud/accounts-and-billing.html
index 8fc97414ae..067243b995 100644
--- a/_site/docs/latest/cloud/accounts-and-billing.html
+++ b/_site/docs/latest/cloud/accounts-and-billing.html
@@ -57,7 +57,7 @@
-
+
@@ -67,7 +67,7 @@
-
+
@@ -6200,66 +6200,59 @@
Accounts and billing
Managing billing and accounts in the Metabase Store.
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).
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.
+
Navigate to Instances.
+
In the instance you want to cancel, click Settings.
+
Click Cancel subscription and delete instance. If you have an Enterprise plan, contact support.
+
Optional: let us know why you’re cancelling so we can improve Metabase. Click Share feedback, or click Skip.
Pro and Enterprise plans allow you to add a custom domain. Setting a custom domain will update your instance’s Site URL. The Site URL is used for things like creating links in emails, auth redirects, and in some embedding scenarios.
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:
+
To add a custom domain to your Metabase:
-
-
-
In the custom domain field (the input prefixed with https:// in the Metabase Store), enter your custom domain (e.g., your.custom.domain).
In the instance you want to add the custom domain to, click Settings.
+
Find the Custom domain section.
+
Enter your custom domain (e.g., your.custom.domain).
+
Click Update.
-
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:
+
Ask the manager of your Domain Name System (DNS) records to add a CNAME pointing to:
Just to be clear: you don’t enter this record in the Metabase Store; you enter it in wherever you manage your DNS records.
+
+
Enter this record where you manage your DNS records, not in the Metabase Store
+
-
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.
+
If you’ve already set up SSO (like SAML or LDAP) for your Metabase, update the return URL in your identity provider configuration to include the 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:
+
You may need to wait for the CNAME to update (this delay is specific to how DNS works, not something Metabase has control over). Metabase takes care of the rest, making 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,
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.
+
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
@@ -6251,7 +6250,15 @@
Why you’d want to use a custom d
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.
The quota numbers update every 6 hours, so there might be a slight delay. Once you hit your quota limit, you won’t be able to upload/sync more data until you either free up some space or increase your storage.
In the instance you want to delete storage from, click Manage plan.
+
Find the Manage add-ons section.
+
In the Storage field, click Manage.
Click Edit.
Click Disable storage.
-
Click Erase all data, which—WARNING–will erase all of its data. We won’t be able to recover the data, so only do this if you’re certain you no longer need the storage and its data.
Metabase Cloud: Basic transform functionality on Metabase Cloud - Starter, Pro, or Enterprise - comes with an additional small fee per successful transform run, see Pricing.
-
Only people logged in with an email of a Metabase Store admins (not just Metabase instance admins) can enable basic transforms. To enable Basic transforms on Metabase Cloud, see Enable transforms.
From your Metabase instance: you can navigate to a feature requiring advanced transforms (like Python transforms or transform inspector), and follow the prompts to upgrade.
-
To enable Advanced transforms from your Metabase instance, you need to be logged into the instance with the same email as a Metabase Store admin, because Advanced transform incur an additional charge.
+
To enable Advanced transforms from your Metabase instance, you need to be logged into the instance with the same email as a Metabase Store admin, because Advanced transform incur an additional charge.
Before you can start writing transforms, you’ll need to enable transforms in your Metabase instance.
-
If you are on a Metabase Cloud plan, only people logged in with an email of a Metabase Store admins (not just Metabase instance admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.
+
If you’re on a Metabase Cloud plan, only people logged in with an email of a Metabase Store admin (not just Metabase instance admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.
+ New
+ Metabase 61: AI governance - access controls, token limits, Metabot customization, build dashboards with MCP, and more.
+
+ Read the announcement
+
+
Drill-through lets you explore data in your Metabase by clicking a chart, a column header, or a table cell. Each click opens a menu with options like Filter by this value, See these records, Break out by, and Zoom in. Selecting one of these options generates a new query and visualizes the result.
+
+
+
+
How drill-through works
+
+
Every drill-through action creates a new query and visualizes the result. Metabase takes the original query and modifies it based on what you click. Switch to the editor to see and edit the new query.
+
+
For example, say a bar chart shows order counts summarized by product category and month. Click the April bar in the Widgets series, then select See these orders. Metabase creates a new question that filters the orders to Widgets in April.
+
+
Some things to keep in mind:
+
+
+
Drill-through requires query-building permissions. You must have permission to create queries on the underlying data to see the drill-through menu.
+
The drill-through does not modify the original question. Drill-through creates a new question without overwriting or modifying your original question.
+
The menu options depend on the type of data you click. Different options appear in the action menu depending on whether you click a chart, a column header, a table cell, or a point on a map.
+
+
+
Drill-through types
+
+
There are two types of drill-through:
+
+
+
Results-based drill-through: Metabase takes the data in the query result and filters, distributes, or otherwise transforms it. Example options include Filter by this value, Distribution, and Sort. You can perform results-based drill-through on questions built with the query builder or native SQL.
+
Query-rewriting drill-through: Metabase modifies your query. Example options include See these records, Break out by, and Zoom in. You can only perform query-rewriting drill-through on questions built with the query builder.
+
+
+
Drill-through options
+
+
The drill-through menu options depend on what you click and on the underlying data.
+
+
Tables
+
+
To drill-through a table, click either:
+
+
+
Column headers
+
Table cells
+
+
+
Column headers
+
+
+
+
+
+
+
Option
+
When it appears
+
+
+
+
+
Filter by this column
+
Any column
+
+
+
Sort
+
Any column except JSON
+
+
+
Distribution
+
Any column except primary keys, JSON, or description and comment fields
+
+
+
Sum / Average
+
Numeric columns when the query isn’t summarized
+
+
+
Distinct values
+
Any column when the query isn’t summarized
+
+
+
Sum over time
+
Numeric columns when the query has a date column and isn’t summarized
Pivoted tables behave like charts. Cells in pivoted tables offer the same options as data points. This is different from the pivot table visualization, which offers a smaller subset of drill-through options.
On a time series or other chart with a continuous axis, click and drag across a range to filter the question to those values. This works like Filter by this value, but for a range of data instead of a single data point.
+
+
Legend items
+
+
Clicking the colored circle on a legend item toggles the series on or off. Clicking the label on the legend item opens the drill-through menu.
+
+
Drill-through on a legend item applies to the entire series, not just one data point. For example, clicking View these records on a legend item shows all the rows for that series across the whole chart.
When you create a query with the query builder, Metabase can read and modify your query for any drill-through action.
+
+
When you write a query with the native SQL editor, Metabase runs your query but doesn’t parse it. It can modify the results, but it can’t modify the query itself. This means you can use results-based drill-through, but not query-rewriting drill-through. For example:
+
+
+
+
+
Works on native SQL questions
+
Doesn’t work on native SQL questions
+
+
+
+
+
Filter by this value
+
See these records
+
+
+
Distribution
+
Break out by
+
+
+
Sort
+
Zoom in
+
+
+
+
+
+
To use drill-through on a native SQL question, you must save the question.
Drill-through can’t rewrite a native SQL query, but you can still make a native SQL chart interactive using custom click behavior. Add the question to a dashboard, and set a click behavior on the card.
+
+
A custom click behavior replaces the drill-through menu with an action you define. It can send you to another question, dashboard, external URL, or update a filter on the current dashboard. Set a dashboard filter to the clicked value to scope the destination.
+
+
Combine native SQL with full drill-through
+
+
If you need native SQL but also want to use the full drill-through menu, write your SQL query as a transform and build the user-facing question with the query builder.
+
+
Write the transform’s SQL to return the individual records, not summarized results. Build questions on the transform’s table with the query builder. These questions support the full drill-through menu.
+
+
Drill-through actions can only reach data that the transform’s table contains.
+
+
+
To create transforms, you must have transform permissions. If you use Metabase Cloud, you must also have the transform add-on.
+
+
+
Drill-through and embedding
+
+
Drill-through behavior depends on the embedding type, because drill-through requires a Metabase user with query permissions.
+
+
+
+
+
Embedding type
+
Drill-through
+
+
+
+
+
Authenticated modular embedding
+
Full drill-through, scoped to the user’s permissions
+
+
+
Guest modular embeds
+
No drill-through
+
+
+
Full app embedding
+
Full drill-through
+
+
+
Public embeds
+
No drill-through
+
+
+
+
+
To turn off drill-through in modular embedding, use the Allow people to drill through on data points setting when you create the embed. In a dashboard, override drill-through on a single card with custom click behavior.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/_site/docs/v0.61/data-studio/transforms/addons.html b/_site/docs/v0.61/data-studio/transforms/addons.html
index cb7c3226ec..db634e61e4 100644
--- a/_site/docs/v0.61/data-studio/transforms/addons.html
+++ b/_site/docs/v0.61/data-studio/transforms/addons.html
@@ -6231,7 +6231,7 @@
Enable basic transforms
Metabase Cloud: Basic transform functionality on Metabase Cloud - Starter, Pro, or Enterprise - comes with an additional small fee per successful transform run, see Pricing.
-
Only people logged in with an email of a Metabase Store admins (not just Metabase instance admins) can enable basic transforms. To enable Basic transforms on Metabase Cloud, see Enable transforms.
From your Metabase instance: you can navigate to a feature requiring advanced transforms (like Python transforms or transform inspector), and follow the prompts to upgrade.
-
To enable Advanced transforms from your Metabase instance, you need to be logged into the instance with the same email as a Metabase Store admin, because Advanced transform incur an additional charge.
+
To enable Advanced transforms from your Metabase instance, you need to be logged into the instance with the same email as a Metabase Store admin, because Advanced transform incur an additional charge.
Before you can start writing transforms, you’ll need to enable transforms in your Metabase instance.
-
If you are on a Metabase Cloud plan, only people logged in with an email of a Metabase Store admins (not just Metabase instance admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.
+
If you’re on a Metabase Cloud plan, only people logged in with an email of a Metabase Store admin (not just Metabase instance admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.
+ New
+ Metabase 61: AI governance - access controls, token limits, Metabot customization, build dashboards with MCP, and more.
+
+ Read the announcement
+
+
Drill-through lets you explore data in your Metabase by clicking a chart, a column header, or a table cell. Each click opens a menu with options like Filter by this value, See these records, Break out by, and Zoom in. Selecting one of these options generates a new query and visualizes the result.
+
+
+
+
How drill-through works
+
+
Every drill-through action creates a new query and visualizes the result. Metabase takes the original query and modifies it based on what you click. Switch to the editor to see and edit the new query.
+
+
For example, say a bar chart shows order counts summarized by product category and month. Click the April bar in the Widgets series, then select See these orders. Metabase creates a new question that filters the orders to Widgets in April.
+
+
Some things to keep in mind:
+
+
+
Drill-through requires query-building permissions. You must have permission to create queries on the underlying data to see the drill-through menu.
+
The drill-through does not modify the original question. Drill-through creates a new question without overwriting or modifying your original question.
+
The menu options depend on the type of data you click. Different options appear in the action menu depending on whether you click a chart, a column header, a table cell, or a point on a map.
+
+
+
Drill-through types
+
+
There are two types of drill-through:
+
+
+
Results-based drill-through: Metabase takes the data in the query result and filters, distributes, or otherwise transforms it. Example options include Filter by this value, Distribution, and Sort. You can perform results-based drill-through on questions built with the query builder or native SQL.
+
Query-rewriting drill-through: Metabase modifies your query. Example options include See these records, Break out by, and Zoom in. You can only perform query-rewriting drill-through on questions built with the query builder.
+
+
+
Drill-through options
+
+
The drill-through menu options depend on what you click and on the underlying data.
+
+
Tables
+
+
To drill-through a table, click either:
+
+
+
Column headers
+
Table cells
+
+
+
Column headers
+
+
+
+
+
+
+
Option
+
When it appears
+
+
+
+
+
Filter by this column
+
Any column
+
+
+
Sort
+
Any column except JSON
+
+
+
Distribution
+
Any column except primary keys, JSON, or description and comment fields
+
+
+
Sum / Average
+
Numeric columns when the query isn’t summarized
+
+
+
Distinct values
+
Any column when the query isn’t summarized
+
+
+
Sum over time
+
Numeric columns when the query has a date column and isn’t summarized
Pivoted tables behave like charts. Cells in pivoted tables offer the same options as data points. This is different from the pivot table visualization, which offers a smaller subset of drill-through options.
On a time series or other chart with a continuous axis, click and drag across a range to filter the question to those values. This works like Filter by this value, but for a range of data instead of a single data point.
+
+
Legend items
+
+
Clicking the colored circle on a legend item toggles the series on or off. Clicking the label on the legend item opens the drill-through menu.
+
+
Drill-through on a legend item applies to the entire series, not just one data point. For example, clicking View these records on a legend item shows all the rows for that series across the whole chart.
When you create a query with the query builder, Metabase can read and modify your query for any drill-through action.
+
+
When you write a query with the native SQL editor, Metabase runs your query but doesn’t parse it. It can modify the results, but it can’t modify the query itself. This means you can use results-based drill-through, but not query-rewriting drill-through. For example:
+
+
+
+
+
Works on native SQL questions
+
Doesn’t work on native SQL questions
+
+
+
+
+
Filter by this value
+
See these records
+
+
+
Distribution
+
Break out by
+
+
+
Sort
+
Zoom in
+
+
+
+
+
+
To use drill-through on a native SQL question, you must save the question.
Drill-through can’t rewrite a native SQL query, but you can still make a native SQL chart interactive using custom click behavior. Add the question to a dashboard, and set a click behavior on the card.
+
+
A custom click behavior replaces the drill-through menu with an action you define. It can send you to another question, dashboard, external URL, or update a filter on the current dashboard. Set a dashboard filter to the clicked value to scope the destination.
+
+
Combine native SQL with full drill-through
+
+
If you need native SQL but also want to use the full drill-through menu, write your SQL query as a transform and build the user-facing question with the query builder.
+
+
Write the transform’s SQL to return the individual records, not summarized results. Build questions on the transform’s table with the query builder. These questions support the full drill-through menu.
+
+
Drill-through actions can only reach data that the transform’s table contains.
+
+
+
To create transforms, you must have transform permissions. If you use Metabase Cloud, you must also have the transform add-on.
+
+
+
Drill-through and embedding
+
+
Drill-through behavior depends on the embedding type, because drill-through requires a Metabase user with query permissions.
+
+
+
+
+
Embedding type
+
Drill-through
+
+
+
+
+
Authenticated modular embedding
+
Full drill-through, scoped to the user’s permissions
+
+
+
Guest modular embeds
+
No drill-through
+
+
+
Full app embedding
+
Full drill-through
+
+
+
Public embeds
+
No drill-through
+
+
+
+
+
To turn off drill-through in modular embedding, use the Allow people to drill through on data points setting when you create the embed. In a dashboard, override drill-through on a single card with custom click behavior.