The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:
TypeScript analyticsbibusiness-intelligencebusinessintelligenceclojuredashboarddatadata-analysisdata-visualizationdatabasemetabasemysqlpostgrespostgresqlreportingslacksql-editorvisualization
docs: making semantic layer happen - org part (#82247)
Alex Yaroshf3685652d319
diff --git a/docs/README.md b/docs/README.mdindex cc6dcc4ebe4..625fc7ac8fa 100644--- a/docs/README.md+++ b/docs/README.md@@ -131,21 +131,21 @@ Metabase's reference documentation.### Data modeling- [Data modeling overview](./data-modeling/start.md)-- [Models](./data-modeling/models.md)-- [Model persistence](./data-modeling/model-persistence.md)-- [Metrics](./data-modeling/metrics.md)-- [Table metadata admin settings](./data-modeling/metadata-editing.md)-- [Field types](./data-modeling/semantic-types.md)-- [Formatting defaults](./data-modeling/formatting.md)-- [Working with JSON](./data-modeling/json-unfolding.md)-- [Segments](./data-modeling/segments.md)+- [Models](./data-modeling/models/models.md)+- [Model persistence](./data-modeling/models/model-persistence.md)+- [Metrics](./data-modeling/semantic-layer/metrics.md)+- [Table metadata admin settings](./data-modeling/metadata/metadata-editing.md)+- [Field types](./data-modeling/metadata/semantic-types.md)+- [Formatting defaults](./data-modeling/metadata/formatting.md)+- [Working with JSON](./data-modeling/metadata/json-unfolding.md)+- [Segments](./data-modeling/semantic-layer/segments.md)### Actions-- [Actions overview](./actions/start.md)-- [Introduction to actions](./actions/introduction.md)-- [Basic actions](./actions/basic.md)-- [Custom actions](./actions/custom.md)+- [Actions overview](./data-modeling/models/actions/start.md)+- [Introduction to actions](./data-modeling/models/actions/introduction.md)+- [Basic actions](./data-modeling/models/actions/basic.md)+- [Custom actions](./data-modeling/models/actions/custom.md)### AIdiff --git a/docs/ai/metabot.md b/docs/ai/metabot.mdindex fefcf375ad5..e7419bc8822 100644--- a/docs/ai/metabot.md+++ b/docs/ai/metabot.md@@ -23,7 +23,7 @@ Here's a non-exhaustive list of things Metabot can help with:- [Edit SQL directly in the native editor](#inline-sql-editing).- [Analyze a chart](#analyze-charts-with-metabot).- [Fix errors in SQL code](#have-metabot-fix-sql-queries).-- [Generate transforms](../data-studio/transforms/transforms-overview.md#use-metabot-to-generate-code-for-transforms)+- [Generate transforms](../data-modeling/transforms/transforms-overview.md#use-metabot-to-generate-code-for-transforms)- [Generate charts in documents](../documents/introduction.md)- [Answer questions from Slack](./metabot-slack.md).diff --git a/docs/ai/settings.md b/docs/ai/settings.mdindex 1ec964bed48..80c4686c741 100644--- a/docs/ai/settings.md+++ b/docs/ai/settings.md@@ -147,7 +147,7 @@ The **Enable Embedded Metabot** toggle turns embedded Metabot on or off. The tog_Available on both the Internal and Embedded tabs, configured independently._-Admins on Pro and Enterprise plans can tell Metabot to only work with [models](../data-modeling/models.md) and [metrics](../data-modeling/metrics.md) that have been [verified](../exploration-and-organization/content-verification.md).+Admins on Pro and Enterprise plans can tell Metabot to only work with [models](../data-modeling/models/models.md) and [metrics](../data-modeling/semantic-layer/metrics.md) that have been [verified](../exploration-and-organization/content-verification.md).Restricting Metabot to verified models and metrics (and only models and metrics) helps Metabot produce more reliable answers, since you know someone has at least vetted the data Metabot can use.@@ -169,7 +169,7 @@ If you're embedding the Metabot component in an app, you can point embedded MetaPicking **Our analytics** is the same as picking no collection at all, so pick something narrower if you want the scoping to do anything. And once you set a collection, tables drop out of embedded Metabot's search results, so pick a collection with the metrics and models you want people building on.-This setting narrows where embedded Metabot searches; it's _not_ a substitute for setting permissions. Embedded Metabot can still read and query anything the person using it has permissions for. Embedded Metabot can also see the items that person viewed recently, whichever collection those live in. Restricting Metabot to [verified content](#verified-content) narrows those recent items to verified, official, and [Library](../data-studio/library.md) content, but it doesn't confine them to the collection you picked. To control what data people can get to in an embed, set [data permissions](../permissions/embedding.md). See also [Set up AI chat in Metabase](../embedding/ai-chat.md#set-up-ai-chat-in-metabase).+This setting narrows where embedded Metabot searches; it's _not_ a substitute for setting permissions. Embedded Metabot can still read and query anything the person using it has permissions for. Embedded Metabot can also see the items that person viewed recently, whichever collection those live in. Restricting Metabot to [verified content](#verified-content) narrows those recent items to verified, official, and [Library](../data-modeling/semantic-layer/library.md) content, but it doesn't confine them to the collection you picked. To control what data people can get to in an embed, set [data permissions](../permissions/embedding.md). See also [Set up AI chat in Metabase](../embedding/ai-chat.md#set-up-ai-chat-in-metabase).### Prompt suggestions@@ -197,9 +197,9 @@ The best thing you can do to improve Metabot's performance is to prep your data### Add descriptions for your data and content-Add descriptions to your [models](../data-modeling/models.md#add-metadata-to-columns-in-a-model), [metrics](../data-modeling/metrics.md), [dashboards](../dashboards/introduction.md), and [questions](../questions/introduction.md). Write descriptions to provide context, define terms, and explain business logic.+Add descriptions to your [models](../data-modeling/models/models.md#add-metadata-to-columns-in-a-model), [metrics](../data-modeling/semantic-layer/metrics.md), [dashboards](../dashboards/introduction.md), and [questions](../questions/introduction.md). Write descriptions to provide context, define terms, and explain business logic.-Admins can also curate [table metadata](../data-modeling/metadata-editing.md) by adding descriptions for tables and their fields.+Admins can also curate [table metadata](../data-modeling/metadata/metadata-editing.md) by adding descriptions for tables and their fields.For example, here's a decent description for an ID field that provides additional context for the data:@@ -213,7 +213,7 @@ You can even ask Metabot to write descriptions for you. But Metabot will only haMake sure the semantic types for each field accurately describe the field's "meaning". For example, if you have a field like `created_at`, you'd want the column type to be Creation date.-Metabase will try to set semantic types automatically, but you should confirm that each field has the relevant semantic type. See [Data types and semantic types](../data-modeling/semantic-types.md). You can also set semantic types for [models](../data-modeling/models.md#add-metadata-to-columns-in-a-model).+Metabase will try to set semantic types automatically, but you should confirm that each field has the relevant semantic type. See [Data types and semantic types](../data-modeling/metadata/semantic-types.md). You can also set semantic types for [models](../data-modeling/models/models.md#add-metadata-to-columns-in-a-model).### Define domain-specific terms in the glossarydiff --git a/docs/ai/usage-auditing.md b/docs/ai/usage-auditing.mdindex 8c4329434fb..8499d082abc 100644--- a/docs/ai/usage-auditing.md+++ b/docs/ai/usage-auditing.md@@ -82,7 +82,7 @@ A profile is the configuration Metabot uses for a conversation: which prompt, wh| `SQL` | SQL writing only. Used by [inline SQL editing](./metabot.md#inline-sql-editing) and similar surfaces. || `Slackbot` | The persona behind [Metabot in Slack](./metabot-slack.md). || `Embedding` | The Metabot persona used inside [embedded Metabase](../embedding/start.md). |-| `Transforms codegen` | Generates [transform](../data-studio/transforms/transforms-overview.md), SQL, or Python. |+| `Transforms codegen` | Generates [transform](../data-modeling/transforms/transforms-overview.md), SQL, or Python. || `Documents` | Generates content inside [Documents](../documents/start.md). |## Conversationsdiff --git a/docs/configuring-metabase/appearance.md b/docs/configuring-metabase/appearance.mdindex 37a759bf3ce..7babe6c4440 100644--- a/docs/configuring-metabase/appearance.md+++ b/docs/configuring-metabase/appearance.md@@ -18,7 +18,7 @@ _Admin > Settings > Appearance_Appearance settings give admins the option to whitelabel Metabase to match your company’s branding.-If you're looking for date, time, number, or currency formatting, see [Formatting defaults](../data-modeling/formatting.md).+If you're looking for date, time, number, or currency formatting, see [Formatting defaults](../data-modeling/metadata/formatting.md).## Changing Metabase's appearancediff --git a/docs/configuring-metabase/caching.md b/docs/configuring-metabase/caching.mdindex 1700186a814..bafa998ba17 100644--- a/docs/configuring-metabase/caching.md+++ b/docs/configuring-metabase/caching.md@@ -178,4 +178,4 @@ If you're using Metabase Cloud, cached question results will be saved to Metabas## Further reading-- [Model persistence](../data-modeling/model-persistence.md)+- [Model persistence](../data-modeling/models/model-persistence.md)diff --git a/docs/configuring-metabase/localization.md b/docs/configuring-metabase/localization.mdindex e629a9bc1a9..eccda43c965 100644--- a/docs/configuring-metabase/localization.md+++ b/docs/configuring-metabase/localization.md@@ -16,7 +16,7 @@ Admins can update the localization settings for the instance:These localization settings allow you to set global language and formatting defaults for dates, times, numbers, and currencies.-People can also override these localization options for specific fields or questions. For more info, see [Formatting](../data-modeling/formatting.md).+People can also override these localization options for specific fields or questions. For more info, see [Formatting](../data-modeling/metadata/formatting.md).## Instance settings@@ -79,7 +79,7 @@ This setting doesn't affect [SQL queries](../questions/native-editor/writing-sqlYou can configure the default formatting for dates and times.-Note that people can also override these localization options for specific fields or questions. For more info, see [Formatting](../data-modeling/formatting.md).+Note that people can also override these localization options for specific fields or questions. For more info, see [Formatting](../data-modeling/metadata/formatting.md).To configure default date and time format settings:@@ -96,7 +96,7 @@ _Admin > Settings > Localization_Some people use commas to separate thousands places, and others use periods. You can configure which camp you belong to.-Note that people can also override these localization options for specific fields or questions. For more info, see [Formatting](../data-modeling/formatting.md).+Note that people can also override these localization options for specific fields or questions. For more info, see [Formatting](../data-modeling/metadata/formatting.md).To configure default separator settings:@@ -107,7 +107,7 @@ To configure default separator settings:_Admin > Settings > Localization_-You can choose how currency fields should be displayed by default (you can configure _which_ fields should be displayed as currency in table metadata or in question formatting setting, see [Formatting](../data-modeling/formatting.md))+You can choose how currency fields should be displayed by default (you can configure _which_ fields should be displayed as currency in table metadata or in question formatting setting, see [Formatting](../data-modeling/metadata/formatting.md))Note that people can also override these localization options for specific fields or questions.diff --git a/docs/configuring-metabase/settings.md b/docs/configuring-metabase/settings.mdindex 4237ec1198a..74dfe80a249 100644--- a/docs/configuring-metabase/settings.md+++ b/docs/configuring-metabase/settings.md@@ -61,7 +61,7 @@ By default, Metabase attempts to make field and table names more readable by chaIf you re-enable this setting, Metabase will run a [scan](../databases/sync-scan.md#how-database-scans-work) against your database to review your table and column names again.-To manually label field or table names in Metabase, check out the [Table Metadata](../data-modeling/metadata-editing.md) section in your admin panel. Metadata in the Table Metadata can be further curated in [models](../data-modeling/models.md).+To manually label field or table names in Metabase, check out the [Table Metadata](../data-modeling/metadata/metadata-editing.md) section in your admin panel. Metadata in the Table Metadata can be further curated in [models](../data-modeling/models/models.md).## Enable X-raysdiff --git a/docs/dashboards/actions.md b/docs/dashboards/actions.mdindex 4363f611238..e646fce69bc 100644--- a/docs/dashboards/actions.md+++ b/docs/dashboards/actions.md@@ -4,17 +4,17 @@ title: Actions on dashboards# Actions on dashboards-You can add buttons to dashboards to perform [actions](../actions/start.md) like creating or updating records, and combine them with dashboard [filters](./filters.md).+You can add buttons to dashboards to perform [actions](../data-modeling/models/actions/start.md) like creating or updating records, and combine them with dashboard [filters](./filters.md).## Create an action-To add an action button to a dashboard, you'll first need to create an action on a model. See [Model actions](../actions/introduction.md).+To add an action button to a dashboard, you'll first need to create an action on a model. See [Model actions](../data-modeling/models/actions/introduction.md).## Add an action button to a dashboard-Once you've [created an action](../actions/introduction.md), you can add a button to a dashboard to perform that action:+Once you've [created an action](../data-modeling/models/actions/introduction.md), you can add a button to a dashboard to perform that action:1. Visit a dashboard page and click the **pencil** icon to start editing the dashboard.2. Click on the **box with a mouse pointer** to add an action.@@ -54,9 +54,9 @@ To connect an action field to a filter on a dashboard:While you can add actions to dashboards and use them in your Metabase, actions won't work on dashboards accessed via [public links](./introduction.md#sharing-dashboards-with-public-links), or dashboards in guest embeds.-If you want people outside of your Metabase to use an action, you can create a [public form for an action](../actions/custom.md#make-public), or expose actions via [modular embedding](../embedding/modular-embedding.md) with SSO or [full app embedding](../embedding/full-app-embedding.md).+If you want people outside of your Metabase to use an action, you can create a [public form for an action](../data-modeling/models/actions/custom.md#make-public), or expose actions via [modular embedding](../embedding/modular-embedding.md) with SSO or [full app embedding](../embedding/full-app-embedding.md).## Further reading-- [Actions](../actions/start.md)+- [Actions](../data-modeling/models/actions/start.md)- [Editable tables](../data-modeling/editable-tables.md)diff --git a/docs/dashboards/filters.md b/docs/dashboards/filters.mdindex 341563f46ab..59842b78c81 100644--- a/docs/dashboards/filters.md+++ b/docs/dashboards/filters.md@@ -265,9 +265,9 @@ To change the operator for a dashboard filter:You can set a widget to display options as a dropdown menu, search box, or input box.-[Metadata settings](../data-modeling/metadata-editing.md#filtering) for the filtered column, including [variable settings in native queries](../questions/native-editor/filter-widgets.md#dropdown-menu-and-search), can also affect the filter's appearance.+[Metadata settings](../data-modeling/metadata/metadata-editing.md#filtering) for the filtered column, including [variable settings in native queries](../questions/native-editor/filter-widgets.md#dropdown-menu-and-search), can also affect the filter's appearance.-For example, if the column you're connecting a filter to is configured in the [metadata settings](../data-modeling/metadata-editing.md#filtering) to display a search box instead of a dropdown, that metadata setting will take precedence.+For example, if the column you're connecting a filter to is configured in the [metadata settings](../data-modeling/metadata/metadata-editing.md#filtering) to display a search box instead of a dropdown, that metadata setting will take precedence.To configure filter input type:@@ -284,8 +284,8 @@ A list of all the possible values in a column. People can use checkboxes to seleIf you're not seeing the **Dropdown list** option and your dashboard filter is based on a column from a:-- Table or model built with the query builder: an admin will need to [enable the dropdown widget](../data-modeling/metadata-editing.md#changing-a-search-box-filter-to-a-dropdown-filter) for that column from Metabase's **Admin settings**.-- Model built with a SQL query: go to your [model's metadata settings](../data-modeling/models.md#add-metadata-to-columns-in-a-model), find your column, and set the **Database column this maps to**.+- Table or model built with the query builder: an admin will need to [enable the dropdown widget](../data-modeling/metadata/metadata-editing.md#changing-a-search-box-filter-to-a-dropdown-filter) for that column from Metabase's **Admin settings**.+- Model built with a SQL query: go to your [model's metadata settings](../data-modeling/models/models.md#add-metadata-to-columns-in-a-model), find your column, and set the **Database column this maps to**.#### Search boxdiff --git a/docs/dashboards/introduction.md b/docs/dashboards/introduction.mdindex 34072927954..fc14c7d00c3 100644--- a/docs/dashboards/introduction.md+++ b/docs/dashboards/introduction.md@@ -356,7 +356,7 @@ There is one important limitation with the `fullscreen` option: for security rea## Dashboard version history-For [questions](../questions/start.md), dashboards, and [models](../data-modeling/models.md), Metabase keeps a version history for the previous fifteen versions of that item.+For [questions](../questions/start.md), dashboards, and [models](../data-modeling/models/models.md), Metabase keeps a version history for the previous fifteen versions of that item.See [History](../exploration-and-organization/history.md).diff --git a/docs/dashboards/linked-filters.md b/docs/dashboards/linked-filters.mdindex de8806641e0..e053155f8dc 100644--- a/docs/dashboards/linked-filters.md+++ b/docs/dashboards/linked-filters.md@@ -17,8 +17,8 @@ You can only link dashboard filters that are wired to database columns (not custFilters can only be linked when they're connected to columns that have an explicit relationship in the table metadata. By relationship, we mean that the columns should be either:- In the same table.-- In two different tables that have a foreign key relationship specified in the [table metadata](../data-modeling/metadata-editing.md).-- In two different tables that have foreign key relationships to one or more intermediate tables, as specified in the [table metadata](../data-modeling/metadata-editing.md).+- In two different tables that have a foreign key relationship specified in the [table metadata](../data-modeling/metadata/metadata-editing.md).+- In two different tables that have foreign key relationships to one or more intermediate tables, as specified in the [table metadata](../data-modeling/metadata/metadata-editing.md).diff --git a/docs/data-studio/overview.md b/docs/data-modeling/data-studio.mdsimilarity index 55%rename from docs/data-studio/overview.mdrename to docs/data-modeling/data-studio.mdindex 98965e5b6f6..efd08baab74 100644--- a/docs/data-studio/overview.md+++ b/docs/data-modeling/data-studio.md@@ -2,7 +2,9 @@title: Data studiosummary: Data Studio provides tools to shape and track your data so everyone can trust the numbers.redirect_from:+ - /docs/latest/data-studio/overview- /docs/latest/data-studio/start+ - /docs/latest/data-modeling/overview---# Data Studio@@ -17,13 +19,13 @@ Data Studio provides tools to shape and track your data so everyone can trust th## What's in Data Studio-- **[Library](./library.md)**\*: A curated space for your organization's most trusted analytics content—tables, metrics, and SQL snippets that your data team recommends.-- **[Managing tables](./managing-tables.md)**: Add table metadata to make tables easier to work with.- - **[Segments](./segments.md)**: Create saved filters on tables so people can use consistent definitions when building queries.- - **[Measures](./measures.md)**: Create saved aggregations on tables so people can use consistent calculations when building queries.-- **[Schema viewer](./schema-viewer.md)**\*: Visualize relationships between tables as an entity-relationship diagram (ERD).-- **[Dependency graph](./dependencies/graph.md)**\*: A visual map of how your content connects, so you can understand the impact of changes before you make them. To find content with broken dependencies, see [Dependency diagnostics](../monitor/dependency-diagnostics.md).- - **[Replace data sources](./dependencies/replace-data-sources.md)**\*: Swap out a table or model across all content that uses it, in one operation.+- **[Library](semantic-layer/library.md)**\*: A curated space for your organization's most trusted analytics content—tables, metrics, and SQL snippets that your data team recommends.+- **[Managing tables](./metadata/managing-tables.md)**: Add table metadata to make tables easier to work with.+ - **[Segments](./semantic-layer/segments.md)**: Create saved filters on tables so people can use consistent definitions when building queries.+ - **[Measures](semantic-layer/measures.md)**: Create saved aggregations on tables so people can use consistent calculations when building queries.+- **[Schema viewer](./tools/schema-viewer.md)**\*: Visualize relationships between tables as an entity-relationship diagram (ERD).+- **[Dependency graph](./tools/graph.md)**\*: A visual map of how your content connects, so you can understand the impact of changes before you make them. To find content with broken dependencies, see [Dependency diagnostics](../monitor/dependency-diagnostics.md).+ - **[Replace data sources](./tools/replace-data-sources.md)**\*: Swap out a table or model across all content that uses it, in one operation.- **[Transforms](./transforms/transforms-overview.md)**: Wrangle your data in Metabase, write the query results back to your database, and reuse them in Metabase as sources for new queries.- **[Glossary](../exploration-and-organization/data-model-reference.md#glossary)**: Define terms relevant to your business, both for people and agents trying to understand your data.diff --git a/docs/data-modeling/editable-tables.md b/docs/data-modeling/editable-tables.mdindex b7608ef6f4c..8ec7811b96f 100644--- a/docs/data-modeling/editable-tables.md+++ b/docs/data-modeling/editable-tables.md@@ -73,7 +73,7 @@ If you try to delete a row that has foreign key references from other tables, yo## Editable table data vs. actions-Metabase offers two ways to modify data in your database: **editable table data** and [actions](../actions/introduction.md).+Metabase offers two ways to modify data in your database: **editable table data** and [actions](../data-modeling/models/actions/introduction.md).### When to use editable tables@@ -94,4 +94,4 @@ Use actions to:- Give non-admins the ability to modify data.- Add a button to a dashboard to trigger a form or query.-See [actions](../actions/introduction.md).+See [actions](../data-modeling/models/actions/introduction.md).diff --git a/docs/data-studio/images/check-repalce-changes.png b/docs/data-modeling/images/check-repalce-changes.pngsimilarity index 100%rename from docs/data-studio/images/check-repalce-changes.pngrename to docs/data-modeling/images/check-repalce-changes.pngdiff --git a/docs/data-studio/images/compatibility-requirements.png b/docs/data-modeling/images/compatibility-requirements.pngsimilarity index 100%rename from docs/data-studio/images/compatibility-requirements.pngrename to docs/data-modeling/images/compatibility-requirements.pngdiff --git a/docs/data-studio/images/create-transform.png b/docs/data-modeling/images/create-transform.pngsimilarity index 100%rename from docs/data-studio/images/create-transform.pngrename to docs/data-modeling/images/create-transform.pngdiff --git a/docs/data-studio/images/data-structure-publish.png b/docs/data-modeling/images/data-structure-publish.pngsimilarity index 100%rename from docs/data-studio/images/data-structure-publish.pngrename to docs/data-modeling/images/data-structure-publish.pngdiff --git a/docs/data-studio/images/data-structure.png b/docs/data-modeling/images/data-structure.pngsimilarity index 100%rename from docs/data-studio/images/data-structure.pngrename to docs/data-modeling/images/data-structure.pngdiff --git a/docs/data-modeling/images/data-studio.png b/docs/data-modeling/images/data-studio.pngnew file mode 100644index 00000000000..400530b5520Binary files /dev/null and b/docs/data-modeling/images/data-studio.png differdiff --git a/docs/data-studio/images/dependency-graph.png b/docs/data-modeling/images/dependency-graph.pngsimilarity index 100%rename from docs/data-studio/images/dependency-graph.pngrename to docs/data-modeling/images/dependency-graph.pngdiff --git a/docs/data-studio/images/disable-all-jobs.png b/docs/data-modeling/images/disable-all-jobs.pngsimilarity index 100%rename from docs/data-studio/images/disable-all-jobs.pngrename to docs/data-modeling/images/disable-all-jobs.pngdiff --git a/docs/data-modeling/images/drill-lens.png b/docs/data-modeling/images/drill-lens.pngnew file mode 100644index 00000000000..5c143ebea46Binary files /dev/null and b/docs/data-modeling/images/drill-lens.png differdiff --git a/docs/data-studio/images/find-and-replace.png b/docs/data-modeling/images/find-and-replace.pngsimilarity index 100%rename from docs/data-studio/images/find-and-replace.pngrename to docs/data-modeling/images/find-and-replace.pngdiff --git a/docs/data-studio/images/jobs-schedule.png b/docs/data-modeling/images/jobs-schedule.pngsimilarity index 100%rename from docs/data-studio/images/jobs-schedule.pngrename to docs/data-modeling/images/jobs-schedule.pngdiff --git a/docs/data-studio/images/jobs.png b/docs/data-modeling/images/jobs.pngsimilarity index 100%rename from docs/data-studio/images/jobs.pngrename to docs/data-modeling/images/jobs.pngdiff --git a/docs/data-studio/images/join-problem.png b/docs/data-modeling/images/join-problem.pngsimilarity index 100%rename from docs/data-studio/images/join-problem.pngrename to docs/data-modeling/images/join-problem.pngdiff --git a/docs/data-modeling/images/metric-explorer.png b/docs/data-modeling/images/metric-explorer.pngdeleted file mode 100644index ff6361bc173..00000000000Binary files a/docs/data-modeling/images/metric-explorer.png and /dev/null differdiff --git a/docs/data-studio/images/new_transform.png b/docs/data-modeling/images/new_transform.pngsimilarity index 100%rename from docs/data-studio/images/new_transform.pngrename to docs/data-modeling/images/new_transform.pngdiff --git a/docs/data-studio/images/publish-table.png b/docs/data-modeling/images/publish-table.pngsimilarity index 100%rename from docs/data-studio/images/publish-table.pngrename to docs/data-modeling/images/publish-table.pngdiff --git a/docs/data-studio/images/runs.png b/docs/data-modeling/images/runs.pngsimilarity index 100%rename from docs/data-studio/images/runs.pngrename to docs/data-modeling/images/runs.pngdiff --git a/docs/data-studio/images/schema-viewer.png b/docs/data-modeling/images/schema-viewer.pngsimilarity index 100%rename from docs/data-studio/images/schema-viewer.pngrename to docs/data-modeling/images/schema-viewer.pngdiff --git a/docs/data-studio/images/sql-transform.png b/docs/data-modeling/images/sql-transform.pngsimilarity index 100%rename from docs/data-studio/images/sql-transform.pngrename to docs/data-modeling/images/sql-transform.pngdiff --git a/docs/data-studio/images/tags.png b/docs/data-modeling/images/tags.pngsimilarity index 100%rename from docs/data-studio/images/tags.pngrename to docs/data-modeling/images/tags.pngdiff --git a/docs/data-modeling/images/transform-codegen.png b/docs/data-modeling/images/transform-codegen.pngnew file mode 100644index 00000000000..b298b0dfa96Binary files /dev/null and b/docs/data-modeling/images/transform-codegen.png differdiff --git a/docs/data-studio/images/transform-dependencies.png b/docs/data-modeling/images/transform-dependencies.pngsimilarity index 100%rename from docs/data-studio/images/transform-dependencies.pngrename to docs/data-modeling/images/transform-dependencies.pngdiff --git a/docs/data-studio/images/transform-edit-settings.png b/docs/data-modeling/images/transform-edit-settings.pngsimilarity index 100%rename from docs/data-studio/images/transform-edit-settings.pngrename to docs/data-modeling/images/transform-edit-settings.pngdiff --git a/docs/data-studio/images/transform-inspector-analysis-warning.png b/docs/data-modeling/images/transform-inspector-analysis-warning.pngsimilarity index 100%rename from docs/data-studio/images/transform-inspector-analysis-warning.pngrename to docs/data-modeling/images/transform-inspector-analysis-warning.pngdiff --git a/docs/data-studio/images/transform-inspector.png b/docs/data-modeling/images/transform-inspector.pngsimilarity index 100%rename from docs/data-studio/images/transform-inspector.pngrename to docs/data-modeling/images/transform-inspector.pngdiff --git a/docs/data-studio/images/transform-settings.png b/docs/data-modeling/images/transform-settings.pngsimilarity index 100%rename from docs/data-studio/images/transform-settings.pngrename to docs/data-modeling/images/transform-settings.pngdiff --git a/docs/data-studio/images/transforms.png b/docs/data-modeling/images/transforms.pngsimilarity index 100%rename from docs/data-studio/images/transforms.pngrename to docs/data-modeling/images/transforms.pngdiff --git a/docs/data-modeling/images/use-metric-in-qb.png b/docs/data-modeling/images/use-metric-in-qb.pngdeleted file mode 100644index 3fefc30cff7..00000000000Binary files a/docs/data-modeling/images/use-metric-in-qb.png and /dev/null differdiff --git a/docs/data-studio/images/workspace-mapped-tables.png b/docs/data-modeling/images/workspace-mapped-tables.pngsimilarity index 100%rename from docs/data-studio/images/workspace-mapped-tables.pngrename to docs/data-modeling/images/workspace-mapped-tables.pngdiff --git a/docs/data-modeling/formatting.md b/docs/data-modeling/metadata/formatting.mdsimilarity index 84%rename from docs/data-modeling/formatting.mdrename to docs/data-modeling/metadata/formatting.mdindex 1884f3ab914..ac688490a2e 100644--- a/docs/data-modeling/formatting.md+++ b/docs/data-modeling/metadata/formatting.md@@ -3,13 +3,14 @@ title: Formatting defaultssummary: Configure how dates, numbers, currencies, and text display in Metabase at global, field, and question levels.redirect_from:- /docs/latest/administration-guide/19-formatting-settings+ - /docs/latest/data-modeling/formatting---# Formatting defaultsPeople all around the world use Metabase, and everyone has different preferences for how dates, times, numbers, and currencies should be formatted and displayed. Metabase lets you customize these formatting options at three different levels:-1. **Global**. Set global defaults in Admin -> Settings -> [Localization](../configuring-metabase/localization.md).+1. **Global**. Set global defaults in Admin -> Settings -> [Localization](../../configuring-metabase/localization.md).2. **Field**. Set field (column) defaults in Admin -> Table Metadata. Field defaults override global defaults.3. **Question**. Set formatting defaults for individual questions in the visualization settings of that question. Question defaults override global and field defaults.@@ -166,7 +167,7 @@ Lets you put a symbol, word, etc. after this number (e.g., "dollars", "%", "unitCurrency field formatting settings include all the same options as in the global formatting section, as well as all the options that Number fields have.-See [Currency formatting options](../questions/visualizations/table.md#currency-formatting-options).+See [Currency formatting options](../../questions/visualizations/table.md#currency-formatting-options).## Question-level formatting@@ -174,17 +175,17 @@ You can also override all formatting settings in any specific saved question orFormatting options vary depending on the type of visualization:-- [Combo chart](../questions/visualizations/line-bar-and-area-charts.md#combo-charts)-- [Detail](../questions/visualizations/detail.md)-- [Funnel](../questions/visualizations/funnel.md)-- [Gauge](../questions/visualizations/gauge.md)-- [Line, Bar, and area charts](../questions/visualizations/line-bar-and-area-charts.md)-- [Maps](../questions/visualizations/map.md)-- [Numbers](../questions/visualizations/numbers.md)-- [Pie or donut chart](../questions/visualizations/pie-or-donut-chart.md)-- [Pivot table](../questions/visualizations/pivot-table.md)-- [Progress bar](../questions/visualizations/progress-bar.md)-- [Scatter plot or bubble chart](../questions/visualizations/scatterplot-or-bubble-chart.md)-- [Tables](../questions/visualizations/table.md)-- [Trend](../questions/visualizations/trend.md)-- [Waterfall chart](../questions/visualizations/waterfall-chart.md)+- [Combo chart](../../questions/visualizations/line-bar-and-area-charts.md#combo-charts)+- [Detail](../../questions/visualizations/detail.md)+- [Funnel](../../questions/visualizations/funnel.md)+- [Gauge](../../questions/visualizations/gauge.md)+- [Line, Bar, and area charts](../../questions/visualizations/line-bar-and-area-charts.md)+- [Maps](../../questions/visualizations/map.md)+- [Numbers](../../questions/visualizations/numbers.md)+- [Pie or donut chart](../../questions/visualizations/pie-or-donut-chart.md)+- [Pivot table](../../questions/visualizations/pivot-table.md)+- [Progress bar](../../questions/visualizations/progress-bar.md)+- [Scatter plot or bubble chart](../../questions/visualizations/scatterplot-or-bubble-chart.md)+- [Tables](../../questions/visualizations/table.md)+- [Trend](../../questions/visualizations/trend.md)+- [Waterfall chart](../../questions/visualizations/waterfall-chart.md)diff --git a/docs/data-modeling/json-unfolding.md b/docs/data-modeling/metadata/json-unfolding.mdsimilarity index 79%rename from docs/data-modeling/json-unfolding.mdrename to docs/data-modeling/metadata/json-unfolding.mdindex fa99d4c5ffc..e8295f2c2e6 100644--- a/docs/data-modeling/json-unfolding.md+++ b/docs/data-modeling/metadata/json-unfolding.md@@ -1,6 +1,8 @@---title: Working with JSONsummary: Learn how to unfold JSON columns into separate fields that you can filter on in the query builder.+redirect_from:+ - /docs/latest/data-modeling/json-unfolding---# Working with JSON@@ -11,32 +13,32 @@ With [some databases](#databases-that-support-json-unfolding), Metabase can unfoHere is a table with a column that contains JSON.-+Metabase can unfold that JSON column so that each key in the JSON object gets its own column in the table. Here are the unfolded fields of the table with the JSON column pictured above:-+And here are the values as seen in the table:-+This unfolding allows you to filter for values found in the original JSON object.Metabase can also unfold nested JSON objects, but it doesn't unfold arrays. If a key contains an array, Metabase keeps that array as a single field.-Metabase will prefix the unfolded column names with the name of the original column that contained the JSON. You can change the column names in **Admin** > [Table metadata](metadata-editing.md), or by creating a [model](./models.md) and editing the column metadata.+Metabase will prefix the unfolded column names with the name of the original column that contained the JSON. You can change the column names in **Admin** > [Table metadata](./metadata-editing.md), or by creating a [model](../models/models.md) and editing the column metadata.## Databases that support JSON unfolding-- [BigQuery](../databases/connections/bigquery.md): automatically enabled, applies to `STRUCT` types only.+- [BigQuery](../../databases/connections/bigquery.md): automatically enabled, applies to `STRUCT` types only.If your data is stored in the [STRUCT data type](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#struct_type) in BigQuery, you can query the table's nested fields. This is enabled by default. However, Metabase won't unfold JSON stored in BigQuery as the `JSON` type. This is because in BigQuery, nested fields are _part of the table definition itself_, so when Metabase syncs with your BigQuery database, it'll be able to get metadata about any of your tables, including tables with nested fields. Querying nested fields, however, doesn't extend to arrays (REPEATED (STRUCT)) in BigQuery.-- [Druid (JDBC)](../databases/connections/druid.md)-- [MongoDB](../databases/connections/mongodb.md): automatically enabled for all nested fields.-- [MySQL](../databases/connections/mysql.md)-- [PostgreSQL](../databases/connections/postgresql.md)+- [Druid (JDBC)](../../databases/connections/druid.md)+- [MongoDB](../../databases/connections/mongodb.md): automatically enabled for all nested fields.+- [MySQL](../../databases/connections/mysql.md)+- [PostgreSQL](../../databases/connections/postgresql.md)## Toggling JSON unfolding for a database@@ -71,7 +73,7 @@ If performance degrades, or you'd rather keep the JSON contained in the original7. In the **Behavior** section, locate the **Unfold JSON** option and select **Yes** or **No**. If the column was unfolded, Metabase will have hidden this JSON column from view, so if you want the JSON column to be visible again, you'll need to change the column's visibility to **Everywhere**.8. Scroll to the top and click the **Filter values** button and select **Re-scan this field**.-+## For JSON unfolding to work, the column's data type must be JSON@@ -79,4 +81,4 @@ For example, if you upload a CSV with JSON in it, you might need to update the d## Filtering JSON-In the [query builder](../questions/query-builder/editor.md), Metabase can't parse JSON in columns, so you can only filter by "Is empty" or "Not empty".+In the [query builder](../../questions/query-builder/editor.md), Metabase can't parse JSON in columns, so you can only filter by "Is empty" or "Not empty".diff --git a/docs/data-studio/managing-tables.md b/docs/data-modeling/metadata/managing-tables.mdsimilarity index 75%rename from docs/data-studio/managing-tables.mdrename to docs/data-modeling/metadata/managing-tables.mdindex fc91265fad7..6b434e06756 100644--- a/docs/data-studio/managing-tables.md+++ b/docs/data-modeling/metadata/managing-tables.md@@ -2,14 +2,16 @@title: Managing tablessummary: See all the tables in your Metabase, edit and sync metadata, edit column types, set visibility, publish tables, and more.redirect_from:+ - /docs/latest/data-studio/managing-tables- /docs/latest/data-studio/data-structure+ - /docs/latest/data-modeling/managing-tables---# Managing tables_Data Studio > Tables_-+You can manage table settings metadata to make it easier for people to work with your data in **Data Studio > Tables**.@@ -40,23 +42,23 @@ You can search for table names, but the search will only match beginnings of worYou can also filter tables by attributes like owners, visibility, or source - for example, if you wanted to find all hidden tables, or all tables created from CSV uploads.-You can set [table attributes](#table-attributes), [edit metadata](#table-and-field-metadata), [publish the table](#publishing-and-unpublishing-tables) or create [segments](./segments.md) or [measures](./measures.md) on the table. You can also select tables in bulk to publish or assign attributes (including visibility) to multiple tables at once.+You can set [table attributes](#table-attributes), [edit metadata](#table-and-field-metadata), [publish the table](#publishing-and-unpublishing-tables) or create [segments](../semantic-layer/segments.md) or [measures](../semantic-layer/measures.md) on the table. You can also select tables in bulk to publish or assign attributes (including visibility) to multiple tables at once.## Publishing and unpublishing tables_Data Studio > Tables > Details_-+{% include plans-blockquote.html feature="Publishing tables to the Library" %}Once you select a table in **Data Studio > Tables**, you can publish the table to add it to the Library. The Library is a special collection that helps you create a source of truth for analytics by providing a centrally managed set of curated content.-See [Publishing tables](./library.md#publishing-tables) in the [Library docs](./library.md).+See [Publishing tables](../semantic-layer/library.md#publishing-tables) in the [Library docs](../semantic-layer/library.md).## Find and replace tables-You can replace every occurrence of a table as a data source with another table. See [Replace data sources](./dependencies/replace-data-sources.md).+You can replace every occurrence of a table as a data source with another table. See [Replace data sources](../tools/replace-data-sources.md).## Sync settings@@ -66,7 +68,7 @@ You can trigger manual re-sync of the table schema in **Data Studio > Tables** iYou can also re-scan field values for the table or discard cached field values, which is useful if you need to retrieve updated values for dropdown filters.-See [syncs and scans](../databases/sync-scan.md) for more information.+See [syncs and scans](../../databases/sync-scan.md) for more information.## Table attributes@@ -86,23 +88,23 @@ The **Visibility layer** attribute controls whether people in your Metabase canThe options are:-- **Hidden**: the table isn't available in the query builder and isn't [synced](../databases/sync-scan.md). People with SQL access can still query the table.+- **Hidden**: the table isn't available in the query builder and isn't [synced](../../databases/sync-scan.md). People with SQL access can still query the table.- **Internal**: table visible in the query builder and synced.- **Final**: table is visible in the query builder and synced.-Table visibility layer can be used as a tool to improve user experience of people working in your Metabase, and it should _not be used to control access_ - use [data permissions](../permissions/data.md) to control access instead.+Table visibility layer can be used as a tool to improve user experience of people working in your Metabase, and it should _not be used to control access_ - use [data permissions](../../permissions/data.md) to control access instead.### Entity typeYou can use **entity type** to tell people what kind of information is contained in the table, for example "Transaction" or "Event". Metabase will try to detect and automatically assign appropriate entity types (like entity type "Person" for a `Users` table"), but you can always change it later.-Outside Data Studio, entity type determines the record icons in the [details view](../exploration-and-organization/exploration.md#view-details-of-a-record).+Outside Data Studio, entity type determines the record icons in the [details view](../../exploration-and-organization/exploration.md#view-details-of-a-record).### Source**Source** describes where the data comes from. It can be useful when you want to identify tables that are, for example, ingested tables, or tables coming from CSV uploads.-Metabase will automatically assign the source "Metabase transforms" to tables created by [Metabase transforms](./transforms/transforms-overview.md), and source "Uploaded data" to tables created by new [CSV uploads](../databases/uploads.md) (CSV uploads that you created before getting Data Studio will not be automatically tagged).+Metabase will automatically assign the source "Metabase transforms" to tables created by [Metabase transforms](../transforms/transforms-overview.md), and source "Uploaded data" to tables created by new [CSV uploads](../../databases/uploads.md) (CSV uploads that you created before getting Data Studio will not be automatically tagged).## Table and field metadata@@ -110,19 +112,19 @@ _Data Studio > Tables > Fields_You can edit field descriptions, types, visibility settings, and formatting. For example, you can choose to display a filter on a field as a dropdown, or display days as `21.03.2026` instead of `03/21/2026`.-See [Table metadata editing](../data-modeling/metadata-editing.md).+See [Table metadata editing](./metadata-editing.md).## Segments-Segments are saved filters on a table that people can use in the query builder. See [Segments](./segments.md).+Segments are saved filters on a table that people can use in the query builder. See [Segments](../semantic-layer/segments.md).## Measures-Measures are saved aggregations on a table that people can use in the query builder. See [Measures](./measures.md).+Measures are saved aggregations on a table that people can use in the query builder. See [Measures](../semantic-layer/measures.md).## Further reading-- [Table metadata editing](../data-modeling/metadata-editing.md)-- [Segments](./segments.md)-- [Measures](./measures.md)-- [Schema viewer](./schema-viewer.md)+- [Table metadata editing](./metadata-editing.md)+- [Segments](../semantic-layer/segments.md)+- [Measures](../semantic-layer/measures.md)+- [Schema viewer](../tools/schema-viewer.md)diff --git a/docs/data-modeling/metadata-editing.md b/docs/data-modeling/metadata/metadata-editing.mdsimilarity index 75%rename from docs/data-modeling/metadata-editing.mdrename to docs/data-modeling/metadata/metadata-editing.mdindex d363bf5e0b2..a53614e03a3 100644--- a/docs/data-modeling/metadata-editing.md+++ b/docs/data-modeling/metadata/metadata-editing.md@@ -2,21 +2,22 @@title: "Table metadata editing"redirect_from:- /docs/latest/administration-guide/03-metadata-editing+ - /docs/latest/data-modeling/metadata-editing---# Table metadata editing-> Prefer using [Data Studio > Tables](../data-studio/managing-tables.md) for metadata editing. The page _Admin > Table Metadata_ will be removed in future versions of Metabase.+> Prefer using [Data Studio > Tables](./managing-tables.md) for metadata editing. The page _Admin > Table Metadata_ will be removed in future versions of Metabase._Admin > Table metadata_Metabase lets you add and edit metadata for your tables and columns.-+The **Table metadata settings only affect the way Metabase displays the data. None of the settings change the data in your database.**-Admins can grant access to these metadata settings to other groups. See [table metadata permissions](../permissions/data.md#manage-table-metadata-permissions).+Admins can grant access to these metadata settings to other groups. See [table metadata permissions](../../permissions/data.md#manage-table-metadata-permissions).## Table settings@@ -28,11 +29,11 @@ You can search for tables, or use the tree navigation to find each of your conneTo edit a table's display name or description in the table metadata tab, click into the box that contains the current table name or description and edit it. Changes will be saved automatically once you click out of the box.-Descriptions are displayed in Metabase's [data reference](../exploration-and-organization/data-model-reference.md) and tooltips when viewing the table. Descriptions help people find the right table for their use case.+Descriptions are displayed in Metabase's [data reference](../../exploration-and-organization/data-model-reference.md) and tooltips when viewing the table. Descriptions help people find the right table for their use case.### Table sync options-Actions you can take to refresh the schema or field values. For more, check out [syncs and scans](../databases/sync-scan.md).+Actions you can take to refresh the schema or field values. For more, check out [syncs and scans](../../databases/sync-scan.md).#### Sync table schema@@ -61,7 +62,7 @@ You can sort the fields in a table in different ways:You can toggle the visibility of a table by clicking on the **eye** icon next to the table name in the left sidebar navigation tree in the Table metadata tab.-**Hidden tables** won't show up in the [query builder](../questions/query-builder/editor.md) or [data reference](../exploration-and-organization/data-model-reference.md). **But this is not a permissions feature**: hidden tables can still be used in SQL questions if someone knows the name of the table. For example, `SELECT * FROM table_name` from the [SQL editor](../questions/native-editor/writing-sql.md) would return results. To prevent people from writing queries against specific tables, see [data permissions](../permissions/data.md).+**Hidden tables** won't show up in the [query builder](../../questions/query-builder/editor.md) or [data reference](../../exploration-and-organization/data-model-reference.md). **But this is not a permissions feature**: hidden tables can still be used in SQL questions if someone knows the name of the table. For example, `SELECT * FROM table_name` from the [SQL editor](../../questions/native-editor/writing-sql.md) would return results. To prevent people from writing queries against specific tables, see [data permissions](../../permissions/data.md).To hide **all of the tables in a database** (say, if you've migrated to a new database), click on the **eye** icon next to the database name in the sidebar.@@ -73,9 +74,9 @@ Fields are also known as Columns (see the [difference between fields and columns## Field name and description-To change the _global_ display name of a column in Metabase, click on the name of the column. For example, you could display "auth.user" as "User" to make the column more readable. People can also use [models](./models.md) to give columns a display name that's local to the model.+To change the _global_ display name of a column in Metabase, click on the name of the column. For example, you could display "auth.user" as "User" to make the column more readable. People can also use [models](../models/models.md) to give columns a display name that's local to the model.-To add a description, click into the box below the column name. Descriptions are displayed in the [data reference](../exploration-and-organization/data-model-reference.md) to help people interpret the column's values. You should consider adding a description if your column contains:+To add a description, click into the box below the column name. Descriptions are displayed in the [data reference](../../exploration-and-organization/data-model-reference.md) to help people interpret the column's values. You should consider adding a description if your column contains:- Abbreviations or codes- Zeroes, nulls, or blank values@@ -83,7 +84,7 @@ To add a description, click into the box below the column name. Descriptions are## Field preview-+Click the preview button to see sample data from that field.@@ -116,7 +117,7 @@ If you want Metabase to treat a text or number column as a datetime column, youFor example, say you have a "Created At" column with a string [data type](https://www.metabase.com/learn/grow-your-data-skills/data-fundamentals/data-types-overview) in your database. If you want to:- Create relative date filters, such as "Created At = Last week".-- Use "Created At" with formulas like [datetimeAdd](../questions/query-builder/expressions/datetimeadd.md).+- Use "Created At" with formulas like [datetimeAdd](../../questions/query-builder/expressions/datetimeadd.md).You can cast that string to a Date type.@@ -145,7 +146,7 @@ Casting options include:- Float->Integer- Datetime->Date-If Metabase doesn't support the casting option you need, you can [create a SQL question](../questions/native-editor/writing-sql.md#starting-a-new-sql-query) that casts the data and [save it as a model](./models.md#create-a-model-from-a-saved-question), or create a view directly in your database.+If Metabase doesn't support the casting option you need, you can [create a SQL question](../../questions/native-editor/writing-sql.md#starting-a-new-sql-query) that casts the data and [save it as a model](../models/models.md#create-a-model-from-a-saved-question), or create a view directly in your database.## Field metadata@@ -153,11 +154,11 @@ _Admin > Table Metadata > Database > Table > Field_### Semantic type-You can change the [semantic type](../data-modeling/semantic-types.md) to give people more context and enable additional functionality, such as displaying text as an image (if the text is an image URL). Another example: you could set an Integer as a "Score" so people have a better idea what those integers indicate.+You can change the [semantic type](./semantic-types.md) to give people more context and enable additional functionality, such as displaying text as an image (if the text is an image URL). Another example: you could set an Integer as a "Score" so people have a better idea what those integers indicate.The semantic types you can choose from depend on the data type. If none of the options describe the values in the column, you can set this setting to "No semantic type".-See [semantic types](../data-modeling/semantic-types.md).+See [semantic types](./semantic-types.md).## Field behavior@@ -167,23 +168,23 @@ _Admin > Table Metadata > Database > Table > Field_- **Everywhere**: By default, users can see all of the columns in a table.- **Only in detail views**: The detail view is the view you see when you expand a single row in a table. This will hide lengthy text from question results. This setting is applied by default if a column's values have an average length of more than 50 characters. For example, you could use this setting on a column like "Customer Comments" if you already have a column for "Customer Rating".-- **Do not include**: Columns won't show up in the query builder or data reference. You can set this option on sensitive columns (such as PII) or irrelevant columns. But this visibility option is a simple omit/hide option; **it's not a permissions feature**. These columns are still accessible for people with native query privileges; they can write `SELECT hidden_column FROM table` or `SELECT * FROM table` in the [SQL editor](../questions/native-editor/writing-sql.md) and they'll be able to view these fields and their values.+- **Do not include**: Columns won't show up in the query builder or data reference. You can set this option on sensitive columns (such as PII) or irrelevant columns. But this visibility option is a simple omit/hide option; **it's not a permissions feature**. These columns are still accessible for people with native query privileges; they can write `SELECT hidden_column FROM table` or `SELECT * FROM table` in the [SQL editor](../../questions/native-editor/writing-sql.md) and they'll be able to view these fields and their values.-To restrict what data people can view and query, see [data permissions](../permissions/data.md).+To restrict what data people can view and query, see [data permissions](../../permissions/data.md).### Filtering-The **Filtering** setting changes a column's default [filter widget](../dashboards/filters.md). Options include:+The **Filtering** setting changes a column's default [filter widget](../../dashboards/filters.md). Options include:- **Search box**: Display a search box and suggest autocompletions for values in that column that match the search term(s).- **A list of all values**: Display a search box, as well as a dropdown menu with checkboxes for values. If the number of distinct values exceeds 1000, however, Metabase will instead display a search box. See [Changing a search box filter to a dropdown filter](#changing-a-search-box-filter-to-a-dropdown-filter).- **Plain input box**: Display a search box, but don't suggest autocompletions.-The settings here will also affect dashboard filters. For example, if you set this to plain input box, you won't be able to set up a dashboard filter that has a dropdown menu. See [dropdown list](../dashboards/filters.md#dropdown-list).+The settings here will also affect dashboard filters. For example, if you set this to plain input box, you won't be able to set up a dashboard filter that has a dropdown menu. See [dropdown list](../../dashboards/filters.md#dropdown-list).#### Changing a search box filter to a dropdown filter-The dropdown filter widget can be finicky, because Metabase needs to run a [scan](../databases/sync-scan.md#how-database-scans-work) to get the list of values for the dropdown menu. If you're having trouble:+The dropdown filter widget can be finicky, because Metabase needs to run a [scan](../../databases/sync-scan.md#how-database-scans-work) to get the list of values for the dropdown menu. If you're having trouble:1. Set the [Semantic type](#semantic-type) to "Category".2. Set [Filtering](#filtering) to "A list of all values".diff --git a/docs/data-modeling/semantic-types.md b/docs/data-modeling/metadata/semantic-types.mdsimilarity index 81%rename from docs/data-modeling/semantic-types.mdrename to docs/data-modeling/metadata/semantic-types.mdindex 442e3cb72f8..dacb96f3d1e 100644--- a/docs/data-modeling/semantic-types.md+++ b/docs/data-modeling/metadata/semantic-types.md@@ -3,6 +3,7 @@ title: "Data types and semantic types"redirect_from:- /docs/latest/users-guide/field-types- /docs/latest/data-modeling/field-types+ - /docs/latest/data-modeling/semantic-typessummary: "Metabase uses both data and semantic types to understand how to format and visualize your data."---@@ -10,14 +11,14 @@ summary: "Metabase uses both data and semantic types to understand how to formatMetabase distinguishes between two types of column metadata: data types and field types.-- [**Data types**](#data-types) are the underlying column type as defined in your database, like `Date` or `Text`. Metabase reads the data types during the [database sync process](../databases/sync-scan.md).+- [**Data types**](#data-types) are the underlying column type as defined in your database, like `Date` or `Text`. Metabase reads the data types during the [database sync process](../../databases/sync-scan.md).- [**Semantic types**](#semantic-types), also called **field types**, are labels that describe how the data should be interpreted. For example, if you have a column with a data type of `Text` that you use to store emails, you can add a semantic type of `Email` to let people (and Metabase) know what kind of text the column stores.Data and semantic types determine how Metabase formats the data, which charts are available, how the filters work, and other functionality.## Data types-Data types are the underlying column types as defined in your database. Metabase reads the data types during the [database sync process](../databases/sync-scan.md). Because Metabase connects to many different databases, it uses its own type hierarchy under the hood, so that it can, for example, handle date fields in databases as different as PostgreSQL and MongoDB.+Data types are the underlying column types as defined in your database. Metabase reads the data types during the [database sync process](../../databases/sync-scan.md). Because Metabase connects to many different databases, it uses its own type hierarchy under the hood, so that it can, for example, handle date fields in databases as different as PostgreSQL and MongoDB.The main data types in Metabase:@@ -42,7 +43,7 @@ You can think of semantic types as adding meaning and context to a field to comm- **Entity key.** Used to indicate that the field uniquely identifies each row. Could be a Product ID, serial number, etc.-- **Foreign key.** Used to refer to an Entity key of another table to connect data from different tables that are related. For example, in a Products table, you might have a Customer ID field that points to a Customers table, where Customer ID is the Entity key. If you want to use [linked filters on dashboards](../dashboards/linked-filters.md), you must set up foreign key relationships.+- **Foreign key.** Used to refer to an Entity key of another table to connect data from different tables that are related. For example, in a Products table, you might have a Customer ID field that points to a Customers table, where Customer ID is the Entity key. If you want to use [linked filters on dashboards](../../dashboards/linked-filters.md), you must set up foreign key relationships.### Semantic types for numeric fields@@ -95,13 +96,13 @@ You can think of semantic types as adding meaning and context to a field to comm## Editing data and semantic types-Admins, and people with [permission to manage table metadata](../permissions/data.md#manage-table-metadata-permissions), can cast data types and edit semantic types in the Admin's Table Metadata tab.+Admins, and people with [permission to manage table metadata](../../permissions/data.md#manage-table-metadata-permissions), can cast data types and edit semantic types in the Admin's Table Metadata tab.### Cast data typesData types can't be edited in Metabase directly, but you can cast certain [data types to different types](./metadata-editing.md#cast-to-a-specific-data-type) so that, for example, Metabase will interpret a text data type as a date type.-Changes made in Table Metadata apply across your entire Metabase. However, if you build a query in the query builder, you can use type casting custom expressions like [`date()`](../questions/query-builder/expressions-list.md#date) or [`integer()`](../questions/query-builder/expressions-list.md#integer) to cast a string to a different type just in your query.+Changes made in Table Metadata apply across your entire Metabase. However, if you build a query in the query builder, you can use type casting custom expressions like [`date()`](../../questions/query-builder/expressions-list.md#date) or [`integer()`](../../questions/query-builder/expressions-list.md#integer) to cast a string to a different type just in your query.### Semantic types don't change the data types@@ -124,8 +125,8 @@ Formatting settings from Table Metadata settings will be applied across your Met| Latitude/Longitude | Displayed as coordinates, e.g., `0.00000000° N` || Email | Display as a `mailto` link || URL | Can format as a clickable link |-| Image URL | Can display as an image. See [table format settings](../questions/visualizations/table.md#display-as) |-| Avatar URL | Can display as avatar circle image. See [table format settings](../questions/visualizations/table.md#display-as) |+| Image URL | Can display as an image. See [table format settings](../../questions/visualizations/table.md#display-as) |+| Avatar URL | Can display as avatar circle image. See [table format settings](../../questions/visualizations/table.md#display-as) || Field containing JSON | In detail view, display as prettified JSON || Entity and Foreign key | Highlighted in table view |@@ -153,7 +154,7 @@ Additionally, if you use location semantic types:### Extract values from columns-For some fields, you can quickly extract values from columns using [shortcuts in table view](../questions/visualizations/table.md#extract-domain-subdomain-host-or-path) or in the [custom expression editor](../questions/query-builder/expressions.md) in the query builder:+For some fields, you can quickly extract values from columns using [shortcuts in table view](../../questions/visualizations/table.md#extract-domain-subdomain-host-or-path) or in the [custom expression editor](../../questions/query-builder/expressions.md) in the query builder:| Group by data type | Extract || ------------------- | --------------------------------------- |@@ -163,11 +164,11 @@ For some fields, you can quickly extract values from columns using [shortcuts in### X-rays-When you [X-ray](../exploration-and-organization/x-rays.md) a table, model, or entity, Metabase considers both the data type and the field type to display different charts that summarize that data.+When you [X-ray](../../exploration-and-organization/x-rays.md) a table, model, or entity, Metabase considers both the data type and the field type to display different charts that summarize that data.### Field Filters-Knowing what field types are and how they work is helpful when using [field filters](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/sql-in-metabase/field-filters), as you can only create field filters for [certain field types](../questions/native-editor/field-filters.md#when-to-use-a-field-filter-variable-vs-a-basic-variable).+Knowing what field types are and how they work is helpful when using [field filters](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/sql-in-metabase/field-filters), as you can only create field filters for [certain field types](../../questions/native-editor/field-filters.md#when-to-use-a-field-filter-variable-vs-a-basic-variable).### JSON unfolding@@ -175,12 +176,12 @@ See [Working with JSON](./json-unfolding.md).## Set semantic types in models to enable people to explore results with the query builder-You can set field types for [models](./models.md), which helps Metabase understand how to work with data in models built using SQL. If you set each column type in a SQL model, people will be able to explore that model using the query builder and drill-through menus.+You can set field types for [models](../models/models.md), which helps Metabase understand how to work with data in models built using SQL. If you set each column type in a SQL model, people will be able to explore that model using the query builder and drill-through menus.-With records that include integer entity keys, you can also configure text fields in models to [surface individual records in search](./models.md#surface-individual-records-in-search-by-matching-against-this-column).+With records that include integer entity keys, you can also configure text fields in models to [surface individual records in search](../models/models.md#surface-individual-records-in-search-by-matching-against-this-column).## Further Reading-- [Data reference](../exploration-and-organization/data-model-reference.md).+- [Data reference](../../exploration-and-organization/data-model-reference.md).- [The Table Metadata page: editing metadata](./metadata-editing.md).- [Field Filters: create smart filter widgets for SQL questions](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/sql-in-metabase/field-filters).diff --git a/docs/actions/basic.md b/docs/data-modeling/models/actions/basic.mdsimilarity index 93%rename from docs/actions/basic.mdrename to docs/data-modeling/models/actions/basic.mdindex 608ac8654cb..77f2b4c9ac4 100644--- a/docs/actions/basic.md+++ b/docs/data-modeling/models/actions/basic.md@@ -1,5 +1,7 @@---title: Basic actions+redirect_from:+ - /docs/latest/actions/basic---# Basic actions@@ -10,7 +12,7 @@ If you only want to give people the option to update a subset of columns, or upd## Creating basic actions-Once actions are enabled, you can create basic actions on a new or existing [model](../data-modeling/models.md) that only wraps a single database table.+Once actions are enabled, you can create basic actions on a new or existing [model](../../../data-modeling/models/models.md) that only wraps a single database table.1. Select a model and click on the **info** button, then click on **Model detail**.2. On the model detail page, click on the **Actions** tab.@@ -54,7 +56,7 @@ When setting up actions on a dashboard, you can either prompt the person to fillThe Update basic action requires you to pass a value for the entity key.-See [Actions in dashboards](../dashboards/actions.md).+See [Actions in dashboards](../../../dashboards/actions.md).## Archiving basic actions@@ -70,4 +72,4 @@ If you have basic actions enabled for a model, you can click on an individual re- [Introduction to actions](./introduction.md)- [Custom actions](./custom.md)-- [Actions in dashboards](../dashboards/actions.md)+- [Actions in dashboards](../../../dashboards/actions.md)diff --git a/docs/actions/custom.md b/docs/data-modeling/models/actions/custom.mdsimilarity index 96%rename from docs/actions/custom.mdrename to docs/data-modeling/models/actions/custom.mdindex 764197ae433..0eb1b18a941 100644--- a/docs/actions/custom.md+++ b/docs/data-modeling/models/actions/custom.md@@ -1,5 +1,7 @@---title: Custom actions+redirect_from:+ - /docs/latest/actions/custom---# Custom actions@@ -12,7 +14,7 @@ Write SQL to update records in your databases.> You must be in a group with Native query editing access to create an action.-1. First, [create a model](../data-modeling/models.md).+1. First, [create a model](../../../data-modeling/models/models.md).2. Visit the model and click on the **info** button.3. Click the **Actions** tab.@@ -155,4 +157,4 @@ FROM prospects;- [Introduction to actions](./introduction.md)- [Basic actions](./basic.md)-- [Actions in dashboards](../dashboards/actions.md)+- [Actions in dashboards](../../../dashboards/actions.md)diff --git a/docs/actions/images/appearance.png b/docs/data-modeling/models/actions/images/appearance.pngsimilarity index 100%rename from docs/actions/images/appearance.pngrename to docs/data-modeling/models/actions/images/appearance.pngdiff --git a/docs/actions/images/basic-actions.png b/docs/data-modeling/models/actions/images/basic-actions.pngsimilarity index 100%rename from docs/actions/images/basic-actions.pngrename to docs/data-modeling/models/actions/images/basic-actions.pngdiff --git a/docs/actions/images/custom-action.png b/docs/data-modeling/models/actions/images/custom-action.pngsimilarity index 100%rename from docs/actions/images/custom-action.pngrename to docs/data-modeling/models/actions/images/custom-action.pngdiff --git a/docs/actions/images/dashboard-action.gif b/docs/data-modeling/models/actions/images/dashboard-action.gifsimilarity index 100%rename from docs/actions/images/dashboard-action.gifrename to docs/data-modeling/models/actions/images/dashboard-action.gifdiff --git a/docs/actions/images/dropdown.png b/docs/data-modeling/models/actions/images/dropdown.pngsimilarity index 100%rename from docs/actions/images/dropdown.pngrename to docs/data-modeling/models/actions/images/dropdown.pngdiff --git a/docs/actions/images/example-action.png b/docs/data-modeling/models/actions/images/example-action.pngsimilarity index 100%rename from docs/actions/images/example-action.pngrename to docs/data-modeling/models/actions/images/example-action.pngdiff --git a/docs/actions/images/form.png b/docs/data-modeling/models/actions/images/form.pngsimilarity index 100%rename from docs/actions/images/form.pngrename to docs/data-modeling/models/actions/images/form.pngdiff --git a/docs/actions/images/public-form.png b/docs/data-modeling/models/actions/images/public-form.pngsimilarity index 100%rename from docs/actions/images/public-form.pngrename to docs/data-modeling/models/actions/images/public-form.pngdiff --git a/docs/actions/images/update-record.png b/docs/data-modeling/models/actions/images/update-record.pngsimilarity index 100%rename from docs/actions/images/update-record.pngrename to docs/data-modeling/models/actions/images/update-record.pngdiff --git a/docs/actions/introduction.md b/docs/data-modeling/models/actions/introduction.mdsimilarity index 74%rename from docs/actions/introduction.mdrename to docs/data-modeling/models/actions/introduction.mdindex 2bf05ccc994..1b518c4ac8d 100644--- a/docs/actions/introduction.md+++ b/docs/data-modeling/models/actions/introduction.md@@ -1,5 +1,7 @@---title: Introduction to actions+redirect_from:+ - /docs/latest/actions/introduction---# Introduction to actions@@ -12,7 +14,7 @@ title: Introduction to actions**Actions** are entities in Metabase that let you build custom forms and business logic.-Actions let you write parameterized SQL that writes back to your database. Actions can be attached to [buttons on dashboards](../dashboards/actions.md) to create custom workflows. You can even publicly share the parameterized forms that actions generate to collect data.+Actions let you write parameterized SQL that writes back to your database. Actions can be attached to [buttons on dashboards](../../../dashboards/actions.md) to create custom workflows. You can even publicly share the parameterized forms that actions generate to collect data.Here are a few ideas for what you can do with actions:@@ -20,20 +22,20 @@ Here are a few ideas for what you can do with actions:- Let team members remove redundant data.- Create a customer feedback form and embed it on your website.-Actions must be added to a [model](../data-modeling/models.md), but actions only run on the raw tables that back those models (so actions will never edit your [model definition](../data-modeling/models.md#edit-a-models-query)).+Actions must be added to a [model](../../../data-modeling/models/models.md), but actions only run on the raw tables that back those models (so actions will never edit your [model definition](../../../data-modeling/models/models.md#edit-a-models-query)).-If you're an admin who just wants to edit data in your tables, check out [Editable table data](../data-modeling/editable-tables.md).+If you're an admin who just wants to edit data in your tables, check out [Editable table data](../../../data-modeling/editable-tables.md).## Enabling actions for a databaseFor actions to work, you'll first need to do the following two things:-1. **Enable model actions for the database connection**. To enable actions for a database connection, admins should click on the **grid** icon in the upper right and navigate to **Admin** > **Databases**, then click on the database you want to create actions for. On the right side of the connection settings form, toggle the **Model actions** option. For actions to work, the database user account (the account you're using to connect to the database) must have [write permissions](../databases/users-roles-privileges.md#privileges-to-enable-actions-and-editable-table-data). And for now, actions are only supported on PostgreSQL and MySQL databases.+1. **Enable model actions for the database connection**. To enable actions for a database connection, admins should click on the **grid** icon in the upper right and navigate to **Admin** > **Databases**, then click on the database you want to create actions for. On the right side of the connection settings form, toggle the **Model actions** option. For actions to work, the database user account (the account you're using to connect to the database) must have [write permissions](../../../databases/users-roles-privileges.md#privileges-to-enable-actions-and-editable-table-data). And for now, actions are only supported on PostgreSQL and MySQL databases.2. **Create at least one model from that database.** Actions are associated with models, so you'll need to have created (or have access to) at least one model before you can start creating actions.## Who can use actions-- **To create or edit an action**, a person must be in a group with [Native query editing](../permissions/data.md) privileges for the relevant database.+- **To create or edit an action**, a person must be in a group with [Native query editing](../../../permissions/data.md) privileges for the relevant database.- **To run an action**, all you need is view access to the action's model or dashboard (or a link to a public action).## Types of actions@@ -47,9 +49,9 @@ There are two types of actions:There are multiple ways to run actions:-- [From the model details page](../data-modeling/models.md#model-details) by clicking the **run** button.+- [From the model details page](../../../data-modeling/models/models.md#model-details) by clicking the **run** button.- From a [public form](./custom.md#make-public) of an action.-- From a [button on dashboard](../dashboards/actions.md).+- From a [button on dashboard](../../../dashboards/actions.md).## Actions change data in tables, which affect models@@ -64,10 +66,10 @@ Before using actions in production, consider playing around with actions on some- If caching is enabled for the relevant table or model, you may not see the effects of an action in Metabase until Metabase refreshes the data (though you can always manually refresh the data).- When creating records on a table that lacks an automatically generated primary key, you'll need to input an available ID (i.e., an ID not already in use by another record).- You can't "undo" actions. You can, however, create and run an action to recreate a deleted record, or change an updated record back to its original values (provided you know the original values).-- Actions are unavailable for public dashboards and dashboards in [guest embeds](../embedding/guest-embedding.md). To use actions in embeds, you can use [modular embedding](../embedding/modular-embedding.md) with SSO or [full app embedding](../embedding/full-app-embedding.md).+- Actions are unavailable for public dashboards and dashboards in [guest embeds](../../../embedding/guest-embedding.md). To use actions in embeds, you can use [modular embedding](../../../embedding/modular-embedding.md) with SSO or [full app embedding](../../../embedding/full-app-embedding.md).## Further reading- [Basic actions](./basic.md)- [Custom actions](./custom.md)-- [Actions in dashboards](../dashboards/actions.md)+- [Actions in dashboards](../../../dashboards/actions.md)diff --git a/docs/actions/start.md b/docs/data-modeling/models/actions/start.mdsimilarity index 82%rename from docs/actions/start.mdrename to docs/data-modeling/models/actions/start.mdindex 4d47565b560..f45471f0a0c 100644--- a/docs/actions/start.md+++ b/docs/data-modeling/models/actions/start.md@@ -1,7 +1,9 @@---title: Actions overviewredirect_from:+ - /docs/latest/data-modeling/models/actions/start- /docs/latest/actions+ - /docs/latest/actions/start---# Actions overview@@ -22,6 +24,6 @@ Metabase will create basic actions that auto-track a model's schema.Write SQL to create new actions.-## [Actions on dashboards](../dashboards/actions.md)+## [Actions on dashboards](../../../dashboards/actions.md)Add actions on dashboards as buttons that you can pass filter values to.diff --git a/docs/data-modeling/model-persistence.md b/docs/data-modeling/models/model-persistence.mdsimilarity index 81%rename from docs/data-modeling/model-persistence.mdrename to docs/data-modeling/models/model-persistence.mdindex e45ecf3fb71..2d60be11354 100644--- a/docs/data-modeling/model-persistence.md+++ b/docs/data-modeling/models/model-persistence.md@@ -1,16 +1,18 @@---title: Model persistence+redirect_from:+ - /docs/latest/data-modeling/model-persistence---# Model persistence-> Prefer [Transforms](../data-studio/transforms/transforms-overview.md) instead of model persistence. Model persistence remains supported for now, but it will be deprecated in future versions of Metabase. You can [convert models to transforms in bulk](../data-studio/transforms/query-transforms.md#convert-models-to-transforms).+> Prefer [Transforms](../transforms/transforms-overview.md) instead of model persistence. Model persistence remains supported for now, but it will be deprecated in future versions of Metabase. You can [convert models to transforms in bulk](../transforms/query.md#convert-models-to-transforms).Metabase can persist the results of your models so that your models (and the questions based on those models) load faster.Metabase will store model results in tables in a bespoke schema in your data warehouse (not the Metabase application database). When people ask questions based on your models, Metabase will use the tables with the stored results instead of re-running the model's query.-> Model persistence doesn't work with [row and column security](../permissions/row-and-column-security.md) or [impersonation](../permissions/impersonation.md).+> Model persistence doesn't work with [row and column security](../../permissions/row-and-column-security.md) or [impersonation](../../permissions/impersonation.md).## Databases that support model persistence@@ -20,7 +22,7 @@ Currently, model persistence is only available for the following databases:- MySQL- Redshift-Model persistence doesn't work with [row and column security](../permissions/row-and-column-security.md) or [impersonation](../permissions/impersonation.md).+Model persistence doesn't work with [row and column security](../../permissions/row-and-column-security.md) or [impersonation](../../permissions/impersonation.md).## Turn on model persistence in Metabase@@ -36,7 +38,7 @@ To turn on model persistence for your Metabase, go to **Admin** > **Performance*You can set models to refresh based on one of the default frequencies (every 1 hour, 2 hours, etc.), or select the **Custom** option to use [cron syntax](https://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html) to specify your own update frequency.-The cron scheduler uses the [default instance report Timezone](../configuring-metabase/localization.md#set-default-instance-report-timezone) if selected. Otherwise the scheduler will use the System Timezone (which defaults to GMT in [Metabase Cloud](https://www.metabase.com/cloud)).+The cron scheduler uses the [default instance report Timezone](../../configuring-metabase/localization.md#set-default-instance-report-timezone) if selected. Otherwise the scheduler will use the System Timezone (which defaults to GMT in [Metabase Cloud](https://www.metabase.com/cloud/)).We recommend scheduling your models to refresh on a frequency that makes sense with how often your source tables update with new data.@@ -60,7 +62,7 @@ By default, new models on the database will _not_ be persisted. You need to [Tur{% include plans-blockquote.html feature="Individual model persistence" %}-You can also toggle persistence on or off for individual models. When viewing a model, click on the **...** in the upper right and select **Edit settings**. Toggle **Persist model data** on (you'll need [Curate access](../permissions/collections.md#curate-access) to the model's collection to do this).+You can also toggle persistence on or off for individual models. When viewing a model, click on the **...** in the upper right and select **Edit settings**. Toggle **Persist model data** on (you'll need [Curate access](../../permissions/collections.md#curate-access) to the model's collection to do this).Toggling persistence for individual models is useful for models with data that updates at different frequencies than the schedule you set for other models in that database, or for models that are used more or less than other models in that database.@@ -70,11 +72,11 @@ To refresh a model's results, go to the model and click on the three-dot menu (*## View model persistence logs-You can view the logs for model persistence in **Monitor** > **Model persistence log**. See [Model persistence log](../monitor/model-persistence-log.md).+You can view the logs for model persistence in **Monitor** > **Model persistence log**. See [Model persistence log](../../monitor/model-persistence-log.md).## Difference between persisted models and caching-Persisted models differ from [cached results](../configuring-metabase/caching.md):+Persisted models differ from [cached results](../../configuring-metabase/caching.md):- **Models are persisted in your data warehouse; cached results are stored in the application database**. Metabase stores cached results in its application database. Metabase persists models in your connected data warehouse as tables.- **Metabase refreshes model results and invalidates cached results**. Metabase will refresh results of models according to the schedule you set. That is, Metabase will re-run the model's query and store the results in your data warehouse. For cached results of saved questions and dashboards, Metabase won't run the queries automatically; it will cache results when people view the question or dashboard, and invalidate the cached results according to the caching policy you set.@@ -82,4 +84,4 @@ Persisted models differ from [cached results](../configuring-metabase/caching.md## Further reading- [Models](./models.md)-- [Caching policies](../configuring-metabase/caching.md)+- [Caching policies](../../configuring-metabase/caching.md)diff --git a/docs/data-modeling/models.md b/docs/data-modeling/models/models.mdsimilarity index 82%rename from docs/data-modeling/models.mdrename to docs/data-modeling/models/models.mdindex b52f70d71ea..841e2bac911 100644--- a/docs/data-modeling/models.md+++ b/docs/data-modeling/models/models.md@@ -1,12 +1,13 @@---title: "Models"redirect_from:+ - /docs/latest/data-modeling/models- /docs/latest/users-guide/models---# Models-> Consider using [Transforms](../data-studio/transforms/transforms-overview.md) instead of models. You can [convert models to transforms in bulk](../data-studio/transforms/query-transforms.md#convert-models-to-transforms).+> Consider using [Transforms](../transforms/transforms-overview.md) instead of models. You can [convert models to transforms in bulk](../transforms/query.md#convert-models-to-transforms).Models curate data from one or more tables (from the same database) to anticipate the kinds of questions people will ask of the data. You can think of them as derived tables, or a special kind of saved question meant to be used as the starting point for new questions. You can base a model on a SQL or query builder question, which means you can include custom, calculated columns in your model.@@ -38,7 +39,7 @@ First, search for models that already exist. If you can't find one that meets yo- [from scratch](#create-a-model-from-scratch), or- [from a saved question](#create-a-model-from-a-saved-question).-Models you create are automatically [pinned to the current collection](../exploration-and-organization/collections.md#pinned-items).+Models you create are automatically [pinned to the current collection](../../exploration-and-organization/collections.md#pinned-items).### Create a model from scratch@@ -49,7 +50,7 @@ Now choose either the query builder or a native query (if you want to use SQL).Next, select your data, create your query, and save it.-Models you create are automatically [pinned to the current collection](../exploration-and-organization/collections.md#pinned-items).+Models you create are automatically [pinned to the current collection](../../exploration-and-organization/collections.md#pinned-items).### Create a model from a saved question@@ -57,17 +58,17 @@ Models you create are automatically [pinned to the current collection](../explor2. Save the question.3. Click on the **...** > **Turn this into a model**.-+## Model detailsTo view a model's details, visit the model and click on the **info** button in the upper right. Here you'll see several tabs:-- **Overview**: Includes the description, Creator and Last Editor, and the list of fields included in the model. As well as the model's [Entity ID](../installation-and-operation/serialization.md#metabase-uses-entity-ids-to-identify-metabase-items).+- **Overview**: Includes the description, Creator and Last Editor, and the list of fields included in the model. As well as the model's [Entity ID](../../installation-and-operation/serialization.md#metabase-uses-entity-ids-to-identify-metabase-items).- **History**: Lists changes to the model, and by whom.- **Relationships**: Lists which questions use the model, and which tables the model is linked to.- **Actions**: Lists actions created based on the model.-- **Insights**: Info about the [model's usage](../usage-and-performance-tools/usage-analytics.md). Only visible to admins on a [Pro or Enterprise plan](https://www.metabase.com/pricing).+- **Insights**: Info about the [model's usage](../../usage-and-performance-tools/usage-analytics.md). Only visible to admins on a [Pro or Enterprise plan](https://www.metabase.com/pricing/).## Add metadata to columns in a model@@ -91,7 +92,7 @@ For models based on SQL queries, you can tell Metabase if the column has the samYou can set the [column type][column-type]. The default is "No special type".-If your model is based on a SQL query and you want people to be able to explore the results with the query builder, you'll need to set the [column type](./semantic-types.md) for each column in your model.+If your model is based on a SQL query and you want people to be able to explore the results with the query builder, you'll need to set the [column type](../metadata/semantic-types.md) for each column in your model.### This column should appear in...@@ -127,13 +128,13 @@ You can edit a model's query by clicking on the down arrow next to the model's nWhen you save changes to a model, Metabase will try to detect whether your changes would break any other entities that depend on that model. For example, if you remove a column from the model, but other questions based on that model rely on that column, Metabase will warn you that those downstream questions will break.-+Currently, Metabase will look for broken column references. If you rename or remove a column, Metabase will likely flag the change as breaking downstream entities. But Metabase can't detect other types of changes like changing the column type or computation logic as breaking changes.## Model list view-+List view helps you explore records one by one instead of sorting through big tables. You can customize the layout to highlight the most important fields.@@ -145,11 +146,11 @@ To view a model as a list:4. Navigate to the **Settings** tab.5. Under "What should the default view of this data be?", toggle to **List**.-+### Customize model list view-+You can customize how the data appears by clicking **Customize the List layout**.@@ -174,7 +175,7 @@ Click **Done** to save your changes.See [asking questions][question].-## [Refer to a model in the SQL query editor](../questions/native-editor/referencing-saved-questions-in-queries.md)+## [Refer to a model in the SQL query editor](../../questions/native-editor/referencing-saved-questions-in-queries.md)You can refer to a model in a SQL query just like you can refer to a saved question:@@ -200,19 +201,19 @@ You can also use the data reference sidebar to browse the models available. To o## Model version history-For [questions](../questions/start.md), [dashboards](../dashboards/start.md), and models, Metabase keeps a version history for the previous fifteen versions of that item. You can view changes and revert to previous versions.+For [questions](../../questions/start.md), [dashboards](../../dashboards/start.md), and models, Metabase keeps a version history for the previous fifteen versions of that item. You can view changes and revert to previous versions.-See [History](../exploration-and-organization/history.md).+See [History](../../exploration-and-organization/history.md).## Delete a modelYou can move outdated or unneeded models to trash, or delete them permanently. Deleting a model will affect questions that use it as a data source.-See [Deleting and restoring items](../exploration-and-organization/delete-and-restore.md).+See [Deleting and restoring items](../../exploration-and-organization/delete-and-restore.md).## Verifying a model-See [content verification](../exploration-and-organization/content-verification.md).+See [content verification](../../exploration-and-organization/content-verification.md).## Model persistence@@ -220,20 +221,20 @@ See [Model persistence](./model-persistence.md)## Convert a model to a transform-[Transforms](../data-studio/transforms/transforms-overview.md) are the successor to models. Transforms create a persistent table in your database that refreshes on a schedule, instead of running the query live each time. Metabase will be gradually phasing out models in favor of transforms.+[Transforms](../transforms/transforms-overview.md) are the successor to models. Transforms create a persistent table in your database that refreshes on a schedule, instead of running the query live each time. Metabase will be gradually phasing out models in favor of transforms.If you're an admin, you can convert existing models to transforms one at a time. Conversion creates a transform from the model's query, runs it to produce the output table, and then updates all questions and dashboards that used the model to use the transform's table instead. The model itself becomes a saved question.-See [Convert existing models to transforms](../data-studio/transforms/query-transforms.md#convert-models-to-transforms).+See [Convert existing models to transforms](../transforms/query.md#convert-models-to-transforms).## Further reading- [Models in Metabase][learn-models]- [Troubleshooting models][troubleshooting-models].-[column-type]: ./semantic-types.md+[column-type]: ../metadata/semantic-types.md[cte]: https://www.metabase.com/learn/sql/working-with-sql/sql-cte[measures-dimensions]: https://www.metabase.com/learn/grow-your-data-skills/data-fundamentals/dimensions-and-measures-[question]: ../questions/start.md+[question]: ../../questions/start.md[learn-models]: https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/models-[troubleshooting-models]: ../troubleshooting-guide/models.md+[troubleshooting-models]: ../../troubleshooting-guide/models.mddiff --git a/docs/data-modeling/images/common-metrics.png b/docs/data-modeling/semantic-layer/images/common-metrics.pngsimilarity index 100%rename from docs/data-modeling/images/common-metrics.pngrename to docs/data-modeling/semantic-layer/images/common-metrics.pngdiff --git a/docs/data-studio/images/explore-measure.png b/docs/data-modeling/semantic-layer/images/explore-measure.pngsimilarity index 100%rename from docs/data-studio/images/explore-measure.pngrename to docs/data-modeling/semantic-layer/images/explore-measure.pngdiff --git a/docs/data-studio/images/find-measures.png b/docs/data-modeling/semantic-layer/images/find-measures.pngsimilarity index 100%rename from docs/data-studio/images/find-measures.pngrename to docs/data-modeling/semantic-layer/images/find-measures.pngdiff --git a/docs/data-modeling/images/formula.png b/docs/data-modeling/semantic-layer/images/formula.pngsimilarity index 100%rename from docs/data-modeling/images/formula.pngrename to docs/data-modeling/semantic-layer/images/formula.pngdiff --git a/docs/data-studio/images/library-data-picker.png b/docs/data-modeling/semantic-layer/images/library-data-picker.pngsimilarity index 100%rename from docs/data-studio/images/library-data-picker.pngrename to docs/data-modeling/semantic-layer/images/library-data-picker.pngdiff --git a/docs/data-modeling/semantic-layer/images/library-in-data-studio.png b/docs/data-modeling/semantic-layer/images/library-in-data-studio.pngnew file mode 100644index 00000000000..9aff4a2a7c7Binary files /dev/null and b/docs/data-modeling/semantic-layer/images/library-in-data-studio.png differdiff --git a/docs/data-modeling/semantic-layer/images/library-in-sidebar.png b/docs/data-modeling/semantic-layer/images/library-in-sidebar.pngnew file mode 100644index 00000000000..978367c29dfBinary files /dev/null and b/docs/data-modeling/semantic-layer/images/library-in-sidebar.png differdiff --git a/docs/data-studio/images/library-org.png b/docs/data-modeling/semantic-layer/images/library-org.pngsimilarity index 100%rename from docs/data-studio/images/library-org.pngrename to docs/data-modeling/semantic-layer/images/library-org.pngdiff --git a/docs/data-modeling/semantic-layer/images/library-permissions.png b/docs/data-modeling/semantic-layer/images/library-permissions.pngnew file mode 100644index 00000000000..ee3b13671acBinary files /dev/null and b/docs/data-modeling/semantic-layer/images/library-permissions.png differdiff --git a/docs/data-studio/images/library-unpublish.png b/docs/data-modeling/semantic-layer/images/library-unpublish.pngsimilarity index 100%rename from docs/data-studio/images/library-unpublish.pngrename to docs/data-modeling/semantic-layer/images/library-unpublish.pngdiff --git a/docs/data-studio/images/measure-definition.png b/docs/data-modeling/semantic-layer/images/measure-definition.pngsimilarity index 100%rename from docs/data-studio/images/measure-definition.pngrename to docs/data-modeling/semantic-layer/images/measure-definition.pngdiff --git a/docs/data-studio/images/measure.png b/docs/data-modeling/semantic-layer/images/measure.pngsimilarity index 100%rename from docs/data-studio/images/measure.pngrename to docs/data-modeling/semantic-layer/images/measure.pngdiff --git a/docs/data-modeling/images/metric-definition.png b/docs/data-modeling/semantic-layer/images/metric-definition.pngsimilarity index 100%rename from docs/data-modeling/images/metric-definition.pngrename to docs/data-modeling/semantic-layer/images/metric-definition.pngdiff --git a/docs/data-modeling/images/metric-dimensions.png b/docs/data-modeling/semantic-layer/images/metric-dimensions.pngsimilarity index 100%rename from docs/data-modeling/images/metric-dimensions.pngrename to docs/data-modeling/semantic-layer/images/metric-dimensions.pngdiff --git a/docs/data-modeling/semantic-layer/images/metric-explorer.png b/docs/data-modeling/semantic-layer/images/metric-explorer.pngnew file mode 100644index 00000000000..4b892a3b7eeBinary files /dev/null and b/docs/data-modeling/semantic-layer/images/metric-explorer.png differdiff --git a/docs/data-modeling/images/metric.png b/docs/data-modeling/semantic-layer/images/metric.pngsimilarity index 100%rename from docs/data-modeling/images/metric.pngrename to docs/data-modeling/semantic-layer/images/metric.pngdiff --git a/docs/data-studio/images/segment-definition.png b/docs/data-modeling/semantic-layer/images/segment-definition.pngsimilarity index 100%rename from docs/data-studio/images/segment-definition.pngrename to docs/data-modeling/semantic-layer/images/segment-definition.pngdiff --git a/docs/data-studio/images/segment.png b/docs/data-modeling/semantic-layer/images/segment.pngsimilarity index 100%rename from docs/data-studio/images/segment.pngrename to docs/data-modeling/semantic-layer/images/segment.pngdiff --git a/docs/data-studio/images/starting-data.png b/docs/data-modeling/semantic-layer/images/starting-data.pngsimilarity index 100%rename from docs/data-studio/images/starting-data.pngrename to docs/data-modeling/semantic-layer/images/starting-data.pngdiff --git a/docs/data-modeling/semantic-layer/images/use-metric-in-qb.png b/docs/data-modeling/semantic-layer/images/use-metric-in-qb.pngnew file mode 100644index 00000000000..a9df5d3d65bBinary files /dev/null and b/docs/data-modeling/semantic-layer/images/use-metric-in-qb.png differdiff --git a/docs/data-modeling/legacy-metrics.md b/docs/data-modeling/semantic-layer/legacy-metrics.mdsimilarity index 91%rename from docs/data-modeling/legacy-metrics.mdrename to docs/data-modeling/semantic-layer/legacy-metrics.mdindex a2ba0bf6e04..ffe443838fc 100644--- a/docs/data-modeling/legacy-metrics.md+++ b/docs/data-modeling/semantic-layer/legacy-metrics.md@@ -1,5 +1,7 @@---title: Legacy metrics+redirect_from:+ - /docs/latest/data-modeling/legacy-metrics---# Legacy metricsdiff --git a/docs/data-modeling/segments.md b/docs/data-modeling/semantic-layer/legacy-segments.mdsimilarity index 88%rename from docs/data-modeling/segments.mdrename to docs/data-modeling/semantic-layer/legacy-segments.mdindex 88433d8e4d7..23ef226335d 100644--- a/docs/data-modeling/segments.md+++ b/docs/data-modeling/semantic-layer/legacy-segments.md@@ -4,7 +4,7 @@ title: "Segments"# Segments-> Prefer [Data Studio](../data-studio/segments.md) for managing segments.+> Prefer [Data Studio](./segments.md) for managing segments.Metabase allows admins to create segments so people can quickly and easily reference them in the query builder.@@ -21,29 +21,29 @@ A segment is just a special named filter or set of filters. You can create theseTo start, select the **Segments** tab, followed by the **New segment** button on the right side of the screen. Choose the appropriate table and filters for your new segment and add a title and description. When you’re done, this segment will be accessible from the filter list in the query builder when viewing this table (the segment will not be automatically applied to the table).-+Now you’ll be looking at the segment builder, which is a limited version of the query builder, with only the option to add filters. Add your filter(s) as you would in the query builder, and then give your segment a name and a description (these will be visible in the query builder filter dropdown after you’ve saved). If you want to test out your segment in the query builder before you save it, just click the Preview button, which will open a new query builder window with your segment applied.-+Once you’re done, click **Save changes**. Now your new segment will appear in the segments list of your table.-+If you exit the Admin Panel and try asking a new question, then click on the button to add a filter, you’ll see your segment at the top of the list.-+## Editing and retiring segmentsYou can edit and retire segments from the Table Metadata screen in the Admin Panel. Select the table with the segment you’re looking for, and click the ellipsis (…) icon to the right of that segment.-+When editing a segment, you’ll be required to leave a note about why you’re changing it, just so everyone can understand why things are different. If any user is the creator of a saved question or dashboard that utilized the segment you’ve edited, they’ll receive an email letting them know that things have changed, along with the explanation that you write in this box.-+Retiring a segment will make it no longer selectable from the query builder. However, **it won’t break existing saved questions that depend on that segment**.diff --git a/docs/data-studio/library.md b/docs/data-modeling/semantic-layer/library.mdsimilarity index 70%rename from docs/data-studio/library.mdrename to docs/data-modeling/semantic-layer/library.mdindex 07ab782c529..866ea1566dd 100644--- a/docs/data-studio/library.md+++ b/docs/data-modeling/semantic-layer/library.md@@ -1,6 +1,8 @@---title: Librarysummary: Create a source of truth for analytics with curated tables, metrics, and SQL snippets that your team can trust.+redirect_from:+ - /docs/latest/data-studio/library---# Library@@ -19,7 +21,7 @@ The Library helps you create a source of truth for analytics by providing a cent-The Library is a special section in the navigation sidebar of the main Metabase app that you curate in [Data Studio](./overview.md) (and only in Data Studio). It has three root sections — **Data**, **Metrics**, and **Snippets** — each of which restricts the type of content it contains. You can create subcollections within Data and Metrics to further organize content - for example, you can group together tables useful for Marketing or Sales.+The Library is a special section in the navigation sidebar of the main Metabase app that you curate in [Data Studio](../data-studio.md) (and only in Data Studio). It has three root sections — **Data**, **Metrics**, and **Snippets** — each of which restricts the type of content it contains. You can create subcollections within Data and Metrics to further organize content - for example, you can group together tables useful for Marketing or Sales.## Adding items to the Library@@ -67,7 +69,7 @@ To create a new subcollection for one of the Library's special collections:Tables published to the Library appear first in the Data section when people choose data sources, nudging them toward trusted data.-You must explicitly publish tables to the Library. We use the word "publish" to suggest that the tables you include in your Library are meant to be finished, polished tables. If your tables need to be cleaned or combined before they're ready for analytical queries, check out [transforms](./transforms/transforms-overview.md).+You must explicitly publish tables to the Library. We use the word "publish" to suggest that the tables you include in your Library are meant to be finished, polished tables. If your tables need to be cleaned or combined before they're ready for analytical queries, check out [transforms](../transforms/transforms-overview.md).Tables published to the Library remain available via the data browser as well.@@ -83,7 +85,7 @@ Once a table is published, you can view and manage its metadata, and more.- Fields- [Segments](segments.md)- [Measures](measures.md)-- [Dependencies](./dependencies/graph.md)+- [Dependencies](../tools/graph.md)To query a table from the Library in Data Studio:@@ -93,7 +95,7 @@ To query a table from the Library in Data Studio:### Published tables can't have dependencies outside of the Library-Tables published to the Library can't depend on any tables outside of the Library. If, for example, you want to publish a table that includes data from another table, such as a [foreign-key remapping](../questions/visualizations/table.md#foreign-key-remapping), Metabase will publish those tables as well.+Tables published to the Library can't depend on any tables outside of the Library. If, for example, you want to publish a table that includes data from another table, such as a [foreign-key remapping](../../questions/visualizations/table.md#foreign-key-remapping), Metabase will publish those tables as well.### Unpublishing tables@@ -113,25 +115,25 @@ Unpublishing a table just removes the table from the Library. That table will st## Metrics-[Metrics](../data-modeling/metrics.md) are standardized calculations that people can trust.+[Metrics](./metrics.md) are standardized calculations that people can trust.Metrics can live in any collection, but metrics in the Library will be prioritized in navigation, search, the query builder, and other places. Use the Library as a place for curated, "official" metrics, like your company's revenue.To add an already existing metric to the Library, move the metric to the **Library > Metrics** collection (or any of its subcollections).-To create a new Library metric, go to **Data Studio > Library** and select **+ New > Metric**. See [creating metrics](../data-modeling/metrics.md#create-a-metric) for more on building metrics.+To create a new Library metric, go to **Data Studio > Library** and select **+ New > Metric**. See [creating metrics](./metrics.md#create-a-metric) for more on building metrics.## SQL snippets-[SQL snippets](../questions/native-editor/snippets.md) are reusable bits of code. All snippets in your Metabase are available to the library, including snippets created elsewhere in your Metabase. You can also create snippet folders in the Library.+[SQL snippets](../../questions/native-editor/snippets.md) are reusable bits of code. All snippets in your Metabase are available to the library, including snippets created elsewhere in your Metabase. You can also create snippet folders in the Library.## Versioning the Library-You can [sync Library content to version control](../installation-and-operation/remote-sync.md), giving you change history and the ability to publish content across environments.+You can [sync Library content to version control](../../installation-and-operation/remote-sync.md), giving you change history and the ability to publish content across environments.## Library permissions-Library is essentially a special collection. Metabase uses the standard [collection permissions](../permissions/collections.md) to determine who can view and edit items in the Library, with some caveats. Library collection permissions are only relevant to the Data and Metrics collections. Snippets permissions are handled by [permissions for snippet folders](../permissions/snippets.md).+Library is essentially a special collection. Metabase uses the standard [collection permissions](../../permissions/collections.md) to determine who can view and edit items in the Library, with some caveats. Library collection permissions are only relevant to the Data and Metrics collections. Snippets permissions are handled by [permissions for snippet folders](../../permissions/snippets.md).@@ -145,21 +147,21 @@ To configure permissions for the library:### Curate permissions-- **Data** collection and its subcollections: The group can view tables in the Data collection, provided they have [data permissions](../permissions/data.md) for the tables. But they can't add, edit, or remove tables. The Admin and Data Analyst groups are the _only_ groups that can publish tables to the Library.+- **Data** collection and its subcollections: The group can view tables in the Data collection, provided they have [data permissions](../../permissions/data.md) for the tables. But they can't add, edit, or remove tables. The Admin and Data Analyst groups are the _only_ groups that can publish tables to the Library.- **Metrics** collection and its subcollections: the group can add, edit, and archive metrics. Groups don't need access to Data Studio to curate metrics.### View permissionsControls whether a group can view the Library and its items.-- **Data** and its subcollections: The group can view tables in the Data collection, provided they have [data permissions](../permissions/data.md) for the tables.+- **Data** and its subcollections: The group can view tables in the Data collection, provided they have [data permissions](../../permissions/data.md) for the tables.- **Metrics** and its subcollections: the group can view the metrics and use them in their queries.### No accessGroups with **No access** won't even see the Library (including in the navigation sidebar and the query builder).-The group may still have access to tables published to the Library, if they have [data permissions](../permissions/data.md) to those tables. Do not use collction permissions to **Library > Data** to block access to tables - use [data permissions](../permissions/data.md) instead.+The group may still have access to tables published to the Library, if they have [data permissions](../../permissions/data.md) to those tables. Do not use collction permissions to **Library > Data** to block access to tables - use [data permissions](../../permissions/data.md) instead.### Permissions to edit the Library@@ -169,17 +171,17 @@ There are some caveats through, depending on which part of the Library you're wo- **Data** (published tables):- - Only [admins and data analysts](../people-and-groups/managing.md) can publish tables to the Data section of the Library;+ - Only [admins and data analysts](../../people-and-groups/managing.md) can publish tables to the Data section of the Library;- Even if you give "Curate" permissions to **Library > Data** or its subcollections to a non-admin and non-analyst group, people in that group will **not** be able to publish tables. People can only publish tables if they have access to Data Studio, and only admins or data analysts can access Sata Studio.- **Metrics**:- - [Admins and data analysts](../people-and-groups/managing.md) can always manage metrics in the Library and its subollections;+ - [Admins and data analysts](../../people-and-groups/managing.md) can always manage metrics in the Library and its subollections;- If you give "Curate" permissions to **Library > Metrics** or its subcollections to a non-admin and non-analyst group, people in that group will be able to save or move metrics to those subcollections from the main app only. "Curate" permissions to **Library > Metrics** or subcolelcitons do _not_ give access to Data Studio.- **Snippets**- - Snippet management is controlled by [snippet permissions](../permissions/snippets.md) - not regular collection permissions.+ - Snippet management is controlled by [snippet permissions](../../permissions/snippets.md) - not regular collection permissions.The root sections (Data, Metrics, Snippets) have fixed properties and can't be renamed or deleted. Subcollections you create follow the normal collection permission rules.@@ -191,11 +193,11 @@ People who have View or Curate collection permissions to the **Library** subcoll- People who have View or Curate collection permissions to **Library > Data** or its subcollections will be able to see published tables the in the navigation sidebar, see the published tables in the query builder, and search for published tables (all restricted to subcollections they have access to, of course).- - **Don't use collection permissions on the Data subcollections for restricting access to tables**. Use [Data permissions](../permissions/data.md) to control access to tables. Collection permissions on **Library > Data** subcollections only control what people see in navigation and data picker, but do not restrict data access. Collection permissions on Data subcollections are useful when you want to declutter the UI for your users - like removing Sales tables from the default view for Marketing group, without necessarily forbidding Marketing from accessing Sales tables altogether.+ - **Don't use collection permissions on the Data subcollections for restricting access to tables**. Use [Data permissions](../../permissions/data.md) to control access to tables. Collection permissions on **Library > Data** subcollections only control what people see in navigation and data picker, but do not restrict data access. Collection permissions on Data subcollections are useful when you want to declutter the UI for your users - like removing Sales tables from the default view for Marketing group, without necessarily forbidding Marketing from accessing Sales tables altogether.- - Use [Data permissions](../permissions/data.md) - not Library collection permissions to control access to the actual data in the tables published to **Library > Data**. Data permissions work the same way in the Library as everywhere else in Metabase.+ - Use [Data permissions](../../permissions/data.md) - not Library collection permissions to control access to the actual data in the tables published to **Library > Data**. Data permissions work the same way in the Library as everywhere else in Metabase.- - Like with models, if you publish a table to the Library, it will grant query access to a group with view access to the database, even if their group has Create Queries set to No in [data permissions](../permissions/data.md) for that particular table.+ - Like with models, if you publish a table to the Library, it will grant query access to a group with view access to the database, even if their group has Create Queries set to No in [data permissions](../../permissions/data.md) for that particular table.- **Metrics**:@@ -203,11 +205,11 @@ People who have View or Curate collection permissions to the **Library** subcoll- **Snippets**:- - Snippet access is controlled by [snippet permissions](../permissions/snippets.md) - not regular collection permissions.+ - Snippet access is controlled by [snippet permissions](../../permissions/snippets.md) - not regular collection permissions.## Further reading-- [Dependency graph](./dependencies/graph.md)-- [Remote sync](../installation-and-operation/remote-sync.md)-- [Metrics](../data-modeling/metrics.md)-- [Snippets](../questions/native-editor/snippets.md).+- [Dependency graph](../tools/graph.md)+- [Remote sync](../../installation-and-operation/remote-sync.md)+- [Metrics](./metrics.md)+- [Snippets](../../questions/native-editor/snippets.md).diff --git a/docs/data-studio/measures.md b/docs/data-modeling/semantic-layer/measures.mdsimilarity index 73%rename from docs/data-studio/measures.mdrename to docs/data-modeling/semantic-layer/measures.mdindex a8cb93ae570..79a3cce1dfa 100644--- a/docs/data-studio/measures.md+++ b/docs/data-modeling/semantic-layer/measures.md@@ -1,21 +1,23 @@---title: Measuressummary: Create saved aggregations on tables so people can use consistent calculations when building queries.+redirect_from:+ - /docs/latest/data-studio/measures---# MeasuresMeasures are saved aggregations associated with a table. You can use measures to create an official definition of a calculation—like Net Promoter Score—so everyone in your Metabase uses the same formula instead of writing their own versions.-People will see measures as options in the Summarize block of the [query builder](../questions/query-builder/editor.md).+People will see measures as options in the Summarize block of the [query builder](../../questions/query-builder/editor.md).## Create measures-> If your instance is in read-only [remote sync](../installation-and-operation/remote-sync.md) mode, and you enabled sync of the [Library](./library.md), you will not be able to create measures on tables published in the Library while in read-only mode.+> If your instance is in read-only [remote sync](../../installation-and-operation/remote-sync.md) mode, and you enabled sync of the [Library](./library.md), you will not be able to create measures on tables published in the Library while in read-only mode.-Measures are created in [Data Studio](../data-studio/overview.md).+Measures are created in [Data Studio](../data-studio.md).1. Go to **Data Studio** by clicking the **grid icon** in top right of the screen and selecting **Data Studio**.2. In Data Studio, go to **Tables** in the left sidebar, and select the table to define a measure on.@@ -25,7 +27,7 @@ Measures are created in [Data Studio](../data-studio/overview.md).4. Click **+New measure**. You'll see an abridged version of Metabase's query builder that focuses on aggregation.-5. Add your aggregation formula. For more complex aggregations, check out [custom expressions](../questions/query-builder/expressions.md).+5. Add your aggregation formula. For more complex aggregations, check out [custom expressions](../../questions/query-builder/expressions.md).For example, you can define a measure like `(CountIf([Score] >= 9) - CountIf([Score] <= 6)) / Count() * 100` to calculate Net Promoter Score.@@ -61,37 +63,37 @@ Deleting a measure won't break questions using it. The questions that use the de## Explore measures-You can explore measures along dimensions and compare several measures in the [Metrics Explorer](../questions/metrics-explorer.md).+You can explore measures along dimensions and compare several measures in the [Metrics Explorer](../../questions/metrics-explorer.md).-To see all measures on a table, select the table in [Data Studio > Managing tables](./managing-tables.md) and switch to the **Measures** tab.+To see all measures on a table, select the table in [Data Studio > Managing tables](../metadata/managing-tables.md) and switch to the **Measures** tab.## Permissions for measuresTo **create, edit, or delete** measures, people need to:-- Be admins or members of the [Data Analysts](../people-and-groups/managing.md#data-analysts) group. This is needed to access Data Studio.-- Have [Create queries](../permissions/data.md#create-queries-permissions) permissions on the measure's table. This is needed to create the measure's query.+- Be admins or members of the [Data Analysts](../../people-and-groups/managing.md#data-analysts) group. This is needed to access Data Studio.+- Have [Create queries](../../permissions/data.md#create-queries-permissions) permissions on the measure's table. This is needed to create the measure's query.To **use** a measure, people need to:-- Have [Create queries](../permissions/data.md#create-queries-permissions) permissions on the measure's table.+- Have [Create queries](../../permissions/data.md#create-queries-permissions) permissions on the measure's table.## Only measures on published tables are synced to Git-When using [Remote Sync](../installation-and-operation/remote-sync.md):+When using [Remote Sync](../../installation-and-operation/remote-sync.md):- Measures on tables that are _not_ published to the [Library](./library.md) are _not_ synced;- Measures on published tables are only synced if [_Library sync is enabled_](./library.md#versioning-the-library).If your instance is in read-only Remote Sync mode, and the Library sync is enabled, you won't be able to create measures on published tables.-You can, however, sync [Metrics](../data-modeling/metrics.md) on any tables by syncing their collection.+You can, however, sync [Metrics](./metrics.md) on any tables by syncing their collection.## Limitations-- Measures are only available for use in the query builder. For defining reusable bits of SQL, check out [Snippets](../questions/native-editor/snippets.md).+- Measures are only available for use in the query builder. For defining reusable bits of SQL, check out [Snippets](../../questions/native-editor/snippets.md).- Measures are only available on questions that use the measure's table as the primary data source.- All admins and people in the Data Analyst group can create measures on tables they have permissions to query. There aren't additional controls to restrict who can create measures beyond special groups and data permissions.- [Only measures on published tables are synced to Git](#only-measures-on-published-tables-are-synced-to-git).@@ -100,5 +102,5 @@ You can, however, sync [Metrics](../data-modeling/metrics.md) on any tables by s- [Library](./library.md)- [Segments](./segments.md)-- [Metrics](../data-modeling/metrics.md)-- [SQL snippets](../questions/native-editor/snippets.md)+- [Metrics](./metrics.md)+- [SQL snippets](../../questions/native-editor/snippets.md)diff --git a/docs/data-modeling/metrics.md b/docs/data-modeling/semantic-layer/metrics.mdsimilarity index 80%rename from docs/data-modeling/metrics.mdrename to docs/data-modeling/semantic-layer/metrics.mdindex 24aafa4658b..7a067dff124 100644--- a/docs/data-modeling/metrics.md+++ b/docs/data-modeling/semantic-layer/metrics.md@@ -3,6 +3,7 @@ title: Metricsredirect_from:- /docs/latest/administration-guide/07-segments-and-metrics- /docs/latest/data-modeling/segments-and-metrics+ - /docs/latest/data-modeling/metricssummary: Metrics are reusable, standardized aggregations that let your team consistently define important numbers across your Metabase.---@@ -18,7 +19,7 @@ For example, you may want to create a metric that calculates revenue, so people## How metrics work-Think of a metric like a reusable formula. For example, you can create a metric on a `Survey` table that calculates `(CountIf([Score] >= 9) - CountIf([Score] <= 6)) / Count()` (a.k.a. Net Promoter Score). Now other people in your Metabase, instead of writing their own version of NPS, can simply look up that agreed-upon NPS metric, or refer to it in the [query builder](../questions/query-builder/editor.md) when creating new questions.+Think of a metric like a reusable formula. For example, you can create a metric on a `Survey` table that calculates `(CountIf([Score] >= 9) - CountIf([Score] <= 6)) / Count()` (a.k.a. Net Promoter Score). Now other people in your Metabase, instead of writing their own version of NPS, can simply look up that agreed-upon NPS metric, or refer to it in the [query builder](../../questions/query-builder/editor.md) when creating new questions.Metrics have three components:@@ -30,7 +31,7 @@ Metabase will show the metrics as an option in the query builder along with theIf you use a metric as your aggregation, Metabase will replace the metric with the saved formula behind the scenes. See [Use metrics in the query builder](#use-metrics-in-the-query-builder).-Metrics live in collections. You can save metrics into the [Library](../data-studio/library.md) collection to surface your org's official curated metrics and encourage people to use them for their own questions.+Metrics live in collections. You can save metrics into the [Library](./library.md) collection to surface your org's official curated metrics and encourage people to use them for their own questions.## Use metrics in the query builder@@ -54,7 +55,7 @@ To create a metric:You can also create a new metric by going to **Browse > Metrics** in the navigation sidebar and clicking on **+**.- If you're creating a [Library metric](../data-studio/library.md#metrics), you can also [navigate to the Library](../data-studio/library.md) and click **+ New > Metric**.+ If you're creating a [Library metric](./library.md#metrics), you can also [navigate to the Library](./library.md) and click **+ New > Metric**.2. Select your starting data. You can start from a table, saved question, model, or another metric.@@ -62,7 +63,7 @@ To create a metric:3. Define your metric. The metric editor is similar to the regular query builder, with one key difference:- - The [**Formula**](#metric-formula) block is where you define your aggregation. You can use [custom expressions](../questions/query-builder/expressions.md) to write the formula, for example `SumIf([Total], [Plan] != 'free')`.+ - The [**Formula**](#metric-formula) block is where you define your aggregation. You can use [custom expressions](../../questions/query-builder/expressions.md) to write the formula, for example `SumIf([Total], [Plan] != 'free')`.@@ -90,7 +91,7 @@ To edit a metric:## Explore, compare, and do math with metrics-To break metrics out by different dimensions, compare metrics and [measures](../data-studio/measures.md), and do math with metrics (like add or divide metrics by each other), check out the [Metrics explorer](../questions/metrics-explorer.md).+To break metrics out by different dimensions, compare metrics and [measures](./measures.md), and do math with metrics (like add or divide metrics by each other), check out the [Metrics explorer](../../questions/metrics-explorer.md).@@ -102,21 +103,21 @@ Metrics are attached to a specific data source. This means that if you define aYou can build metrics on tables, saved questions, models, and other metrics.-We don't recommend using joins in metric definitions. If you need to build a metric that uses information from multiple tables, consider making a [transform](../data-studio/transforms/transforms-overview.md) to join those tables, _then_ create a metric on the table the transform creates.+We don't recommend using joins in metric definitions. If you need to build a metric that uses information from multiple tables, consider making a [transform](../transforms/transforms-overview.md) to join those tables, _then_ create a metric on the table the transform creates.## Metric formulaThe formula is the core of the metric. It's the thing you are aggregating, and it's required when defining a metric.-You can use [custom expressions](../questions/query-builder/expressions.md) to define a metric, for example:+You can use [custom expressions](../../questions/query-builder/expressions.md) to define a metric, for example:```(CountIf([Score] >= 9) - CountIf([Score] <= 6) ) / Count() * 100```-A metric formula must be an _aggregation_ of a column, meaning you can have a formula like `Sum([Price])` which will add up all the values in the `Price` column across all records, but you can't have a formula like `[Price] + [Tax]` which adds two values on a per-record basis. If you want to create a "calculated" column, consider creating a [transform](../data-studio/transforms/transforms-overview.md) or [model](../data-modeling/models.md) instead.+A metric formula must be an _aggregation_ of a column, meaning you can have a formula like `Sum([Price])` which will add up all the values in the `Price` column across all records, but you can't have a formula like `[Price] + [Tax]` which adds two values on a per-record basis. If you want to create a "calculated" column, consider creating a [transform](../transforms/transforms-overview.md) or [model](../models/models.md) instead.-We don't recommend adding filters into the metric definition to avoid filter conflicts when using metrics in the query builder. You can use conditional custom expressions like [`CountIf`, `SumIf`, and `DistinctIf`](../questions/query-builder/expressions-list.md#aggregations) to create conditional aggregations.+We don't recommend adding filters into the metric definition to avoid filter conflicts when using metrics in the query builder. You can use conditional custom expressions like [`CountIf`, `SumIf`, and `DistinctIf`](../../questions/query-builder/expressions-list.md#aggregations) to create conditional aggregations.You can reference other metrics when defining the formula for your metric.@@ -128,9 +129,9 @@ Metric dimensions are the fields people can use to break out and filter a metricBy default, every column from a metric's source data serves as a dimension. You can curate a metric's dimensions to choose which fields appear as breakout and filter options. You can also set the default dimension Metabase uses to display the metric.-Metabase uses the curated dimensions as the breakout and filter options in the [Metrics explorer](../questions/metrics-explorer.md), on the metric's **About** tab, and for dashboard filters. A dashboard filter can connect to the curated dimensions that match the filter's type.+Metabase uses the curated dimensions as the breakout and filter options in the [Metrics explorer](../../questions/metrics-explorer.md), on the metric's **About** tab, and for dashboard filters. A dashboard filter can connect to the curated dimensions that match the filter's type.-Curated dimensions don't affect the [query builder](../questions/query-builder/editor.md)'s filter and summarize pickers. When someone uses a metric in a question, they can filter and summarize by any column from the metric's source data.+Curated dimensions don't affect the [query builder](../../questions/query-builder/editor.md)'s filter and summarize pickers. When someone uses a metric in a question, they can filter and summarize by any column from the metric's source data.### Curate a metric's dimensions@@ -160,7 +161,7 @@ You can see all metrics on your instance:## Metric permissions-Because metrics live in collections, are attached to a data source, and define a query, permissions for metrics are determined by a combination of [collection permissions](../permissions/collections.md), ["View data" permissions](../permissions/data.md#can-view-data-permission), and ["Create queries" permissions](../permissions/data.md#create-queries-permissions).+Because metrics live in collections, are attached to a data source, and define a query, permissions for metrics are determined by a combination of [collection permissions](../../permissions/collections.md), ["View data" permissions](../../permissions/data.md#can-view-data-permission), and ["Create queries" permissions](../../permissions/data.md#create-queries-permissions).| Metric action \ Permissions | View data | Create queries | Collection || --------------------------------- | ------------- | ------------------------ | ---------- |@@ -172,13 +173,13 @@ Anyone who has these permissions will be able to interact with the metric: for e## Metrics in the Library-By adding metrics to your Library, the query builder will display the metrics more prominently in menus. See [Library metrics](../data-studio/library.md#metrics).+By adding metrics to your Library, the query builder will display the metrics more prominently in menus. See [Library metrics](./library.md#metrics).## Verifying a metric-On [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans, you can [mark metrics as verified](../exploration-and-organization/content-verification.md).+On [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans, you can [mark metrics as verified](../../exploration-and-organization/content-verification.md).-Prefer using the [Library](../data-studio/library.md#metrics) to let people know which metrics they should use.+Prefer using the [Library](./library.md#metrics) to let people know which metrics they should use.## Caching a metric@@ -189,19 +190,19 @@ You can cache results of a metric to improve performance:1. Visit the metric.2. Click **three dots** in the top right corner.3. Click **Caching**.-4. Select the [caching policy](../configuring-metabase/caching.md#cache-invalidation-policies).+4. Select the [caching policy](../../configuring-metabase/caching.md#cache-invalidation-policies).-See [Query caching](../configuring-metabase/caching.md).+See [Query caching](../../configuring-metabase/caching.md).## Limitations- For now, metrics are associated with a specific data source, and can't be used on any other data source, including on data sources derived from metric's original data source.-- Metrics are only available to the query builder. For defining reusable bits of SQL, check out [Snippets](../questions/native-editor/snippets.md).+- Metrics are only available to the query builder. For defining reusable bits of SQL, check out [Snippets](../../questions/native-editor/snippets.md).- You can't limit people from creating metrics on data sources they otherwise have permissions to query.## Further reading-- [Measures](../data-studio/measures.md)-- [Models](./models.md)+- [Measures](./measures.md)+- [Models](../models/models.md)- [Segments](./segments.md)-- [SQL Snippets](../questions/native-editor/snippets.md)\ No newline at end of file+- [SQL Snippets](../../questions/native-editor/snippets.md)diff --git a/docs/data-studio/segments.md b/docs/data-modeling/semantic-layer/segments.mdsimilarity index 75%rename from docs/data-studio/segments.mdrename to docs/data-modeling/semantic-layer/segments.mdindex 70d6e3be26d..44772544592 100644--- a/docs/data-studio/segments.md+++ b/docs/data-modeling/semantic-layer/segments.md@@ -1,25 +1,28 @@---title: Segmentssummary: Create saved filters on tables so people can use consistent definitions when building queries.+redirect_from:+ - /docs/latest/data-studio/segments+ - /docs/latest/data-modeling/segments---# SegmentsSegments are saved filters on tables. You can use segments to create official definitions of a subset of customers, users, or products that everyone on your team can refer to consistently (for example what constitutes an "active user").-People will see segments as options in the Filter block of the [query builder](../questions/query-builder/editor.md).+People will see segments as options in the Filter block of the [query builder](../../questions/query-builder/editor.md).-For now, in addition to Data Studio, segments can also be managed through **Admin > Table Metadata**, see [Segments in table metadata](../data-modeling/segments.md).+For now, in addition to Data Studio, segments can also be managed through **Admin > Table Metadata**, see [Segments in table metadata](./legacy-segments.md).-To see all segments on a table, select the table in [Managing tables](./managing-tables.md) and switch to the **Segments** tab.+To see all segments on a table, select the table in [Managing tables](../metadata/managing-tables.md) and switch to the **Segments** tab.## Create segments-> If your instance is in read-only [remote sync](../installation-and-operation/remote-sync.md) mode, and you enabled sync of the [Library](./library.md), you will not be able to create segments on tables published in the Library while in read-only mode.+> If your instance is in read-only [remote sync](../../installation-and-operation/remote-sync.md) mode, and you enabled sync of the [Library](./library.md), you will not be able to create segments on tables published in the Library while in read-only mode.-Segments are created in [Data Studio](../data-studio/overview.md).+Segments are created in [Data Studio](../data-studio.md).1. Go to **Data Studio** by clicking the **grid icon** in top right of the screen and selecting **Data Studio**.2. In Data Studio, go to **Tables** in the left sidebar, and select the table to define a segment on.@@ -57,16 +60,16 @@ Deleting a segment will not break questions using it. The questions that use theTo **create, edit, or delete** segments, people need to:-- Be admins or members of the [Data Analysts](../people-and-groups/managing.md#data-analysts) group. This is needed to access Data Studio.-- Have [Create queries](../permissions/data.md#create-queries-permissions) permissions on the segment's table. This is needed to create the segment's query.+- Be admins or members of the [Data Analysts](../../people-and-groups/managing.md#data-analysts) group. This is needed to access Data Studio.+- Have [Create queries](../../permissions/data.md#create-queries-permissions) permissions on the segment's table. This is needed to create the segment's query.To **use** a segment, people need to:-- Have [Create queries](../permissions/data.md#create-queries-permissions) permissions on the segment's table.+- Have [Create queries](../../permissions/data.md#create-queries-permissions) permissions on the segment's table.## Only segments on published tables are synced to Git-When using [Remote Sync](../installation-and-operation/remote-sync.md):+When using [Remote Sync](../../installation-and-operation/remote-sync.md):- Segments on tables that are _not_ published to the [Library](./library.md) are _not_ synced;- Segments on published tables are only synced if [_Library sync is enabled_](./library.md#versioning-the-library).@@ -75,7 +78,7 @@ If your instance is in read-only Remote Sync mode, and the Library sync is enabl## Limitations-- Segments are only available for use in the query builder. For defining reusable bits of SQL, check out [Snippets](../questions/native-editor/snippets.md).+- Segments are only available for use in the query builder. For defining reusable bits of SQL, check out [Snippets](../../questions/native-editor/snippets.md).- Segments are only available on questions that use the segment's table as the primary data source.- All admins and people in the Data Analyst group can create segments on tables they have permissions to query. There aren't additional controls to restrict who can create segments beyond special groups and data permissions.- [Only segments on published tables are synced to Git](#only-segments-on-published-tables-are-synced-to-git).@@ -84,4 +87,4 @@ If your instance is in read-only Remote Sync mode, and the Library sync is enabl- [Library](./library.md)- [Measures](./measures.md)-- [SQL snippets](../questions/native-editor/snippets.md)+- [SQL snippets](../../questions/native-editor/snippets.md)diff --git a/docs/data-modeling/start.md b/docs/data-modeling/start.mdindex 777b3f43cbd..eaf66d20827 100644--- a/docs/data-modeling/start.md+++ b/docs/data-modeling/start.md@@ -8,34 +8,34 @@ redirect_from:Metabase provides tools for organizing your data and making it easier for people to understand.-## [Models](./models.md)+## [Models](models/models.md)Models curate data from another table or tables from the same database to anticipate the kinds of questions people will ask of the data. You can think of them as derived tables, or a special kind of saved question meant to be used as the starting point for new questions.-## [Model persistence](./model-persistence.md)+## [Model persistence](models/model-persistence.md)Persist model results for faster loading times.-## [Metrics](./metrics.md)+## [Metrics](semantic-layer/metrics.md)Create metrics to define the official way to calculate important numbers for your team.-## [Table metadata admin settings](./metadata-editing.md)+## [Table metadata admin settings](./metadata/metadata-editing.md)Guide people to the right data by adding display names, hiding outdated tables, configuring filter types, and more.-## [Field types](./semantic-types.md)+## [Field types](./metadata/semantic-types.md)Field types dictate how Metabase displays its data, as well as the column’s special functionality, if any.-## [Setting default formatting for your data](./formatting.md)+## [Setting default formatting for your data](./metadata/formatting.md)Define formatting and display defaults for numbers, currencies, datetimes, and more.-## [Working with JSON](./json-unfolding.md)+## [Working with JSON](./metadata/json-unfolding.md)Metabase can unfold JSON columns into their component fields, which you can then filter on using the query builder.-## [Segments](./segments.md)+## [Segments](./semantic-layer/segments.md)Admins can define segments to create official filters for your data.diff --git a/docs/data-studio/dependencies/graph.md b/docs/data-modeling/tools/graph.mdsimilarity index 89%rename from docs/data-studio/dependencies/graph.mdrename to docs/data-modeling/tools/graph.mdindex 22bdc95bc87..933d958c8ce 100644--- a/docs/data-studio/dependencies/graph.md+++ b/docs/data-modeling/tools/graph.md@@ -2,6 +2,7 @@title: Dependency graphsummary: Visualize how your content connects and what depends on what in Metabase.redirect_from:+ - /docs/latest/data-studio/dependencies/graph- /docs/latest/data-studio/dependency-graph---@@ -13,29 +14,29 @@ redirect_from:The dependency graph provides a visual representation of how your Metabase content is connected. You can use it to follow how data flows through your Metabase to better understand the impact of any changes you make.-If you're looking for a visual representation of foreign key relationships between tables, check out the [Schema viewer](../schema-viewer.md) instead.+If you're looking for a visual representation of foreign key relationships between tables, check out the [Schema viewer](schema-viewer.md) instead.## What the dependency graph tracksThe dependency graph tracks the relationships between Metabase entities:- [Questions](../../questions/introduction.md)-- [Models](../../data-modeling/models.md)+- [Models](../../data-modeling/models/models.md)- [Snippets](../../questions/native-editor/snippets.md)- [Transforms](../transforms/transforms-overview.md)-- [Metrics](../../data-modeling/metrics.md)+- [Metrics](../../data-modeling/semantic-layer/metrics.md)- [Dashboards](../../dashboards/introduction.md)- [Documents](../../documents/introduction.md)Dependency graph will also show the dependencies of Metabase entities on the tables that serve as data sources for those entities.-To see foreign key relationships between tables, see the [Schema viewer](../schema-viewer.md) instead.+To see foreign key relationships between tables, see the [Schema viewer](schema-viewer.md) instead.## Viewing the dependency graphTo open the full dependency graph:-1. Open [Data Studio](../overview.md).+1. Open [Data Studio](../data-studio.md).2. Click **Dependency graph** in the left sidebar.This opens a canvas view where you can search for and visualize the dependencies of any item across your entire Metabase instance.@@ -79,7 +80,7 @@ You can use the dependency graph to replace query sources in bulk. See [Replace## Further reading-- [Library](../library.md)+- [Library](../semantic-layer/library.md)- [Dependency diagnostics](../../monitor/dependency-diagnostics.md)- [Replace data sources](./replace-data-sources.md)-- [Schema viewer](../schema-viewer.md)+- [Schema viewer](schema-viewer.md)diff --git a/docs/data-studio/dependencies/replace-data-sources.md b/docs/data-modeling/tools/replace-data-sources.mdsimilarity index 97%rename from docs/data-studio/dependencies/replace-data-sources.mdrename to docs/data-modeling/tools/replace-data-sources.mdindex b8f6675c782..aa198f9d6a5 100644--- a/docs/data-studio/dependencies/replace-data-sources.md+++ b/docs/data-modeling/tools/replace-data-sources.md@@ -1,6 +1,8 @@---title: Replace data sourcessummary: Admins can swap out a table, model, or question and replace it with a different one across your entire Metabase.+redirect_from:+ - /docs/latest/data-studio/dependencies/replace-data-sources---# Replace data sources@@ -61,7 +63,7 @@ You can replace a table, model, or saved question with any other table, model, oFor example, if `old_table` has `ID` column with Metabase semantic type "Entity key", then the replacement source `new_table` also must have an `ID` column with Metabase semantic type "Entity key".-- If replacing a table, that **original table can't be a target of a Metabase's [semantic foreign keys](../../data-modeling/semantic-types.md)** from other tables.+- If replacing a table, that **original table can't be a target of a Metabase's [semantic foreign keys](../metadata/semantic-types.md)** from other tables.Foreign keys can still exist on the database level, but not on the level of Metabase semantic types. This requirement is necessary to avoid issues with implicit joins when swapping tables.@@ -117,7 +119,7 @@ Metabase **will not replace** tables/models/questions in:- Snippets- Questions or models that power dropdown filter values in SQL questions and dashboards- [Links](../../dashboards/introduction.md#link-cards) and [custom destinations](../../dashboards/interactive.md#custom-destinations) on dashboards;-- Targets for [actions](../../actions/introduction.md).+- Targets for [actions](../../data-modeling/models/actions/introduction.md).Metabase will **not allow** you to replace data sources that are used as:diff --git a/docs/data-studio/schema-viewer.md b/docs/data-modeling/tools/schema-viewer.mdsimilarity index 58%rename from docs/data-studio/schema-viewer.mdrename to docs/data-modeling/tools/schema-viewer.mdindex ef02faef943..49587b33ca0 100644--- a/docs/data-studio/schema-viewer.md+++ b/docs/data-modeling/tools/schema-viewer.md@@ -1,6 +1,8 @@---title: Schema viewersummary: Visualize relationships between tables in your database using an entity-relationship diagram (ERD)+redirect_from:+ - /docs/latest/data-studio/schema-viewer---# Schema viewer@@ -11,9 +13,9 @@ _Data Studio > Schema viewer_The schema viewer helps you understand relationships between tables in your database.-+-If you're looking for a visual representation of dependencies between _Metabase entities_ (questions, metrics etc) and their underlying tables, check out the [dependency graph](./dependencies/graph.md) instead.+If you're looking for a visual representation of dependencies between _Metabase entities_ (questions, metrics etc) and their underlying tables, check out the [dependency graph](graph.md) instead.## What the schema viewer shows@@ -25,11 +27,11 @@ For a particular schema (if your), the schema viewer will display:- Foreign key relationships _set in Metabase_ (as arrows between tables)- Entity keys _set in Metabase_-Schema viewer displays relationships based on the [Foreign Key semantic type](../data-modeling/metadata-editing.md) defined in Metabase, not based on constraints defined directly in your database. However, during [database sync](../databases/sync-scan.md), Metabase automatically maps database foreign key constraints to foreign key semantic types, so in most cases you won't need to set these manually.+Schema viewer displays relationships based on the [Foreign Key semantic type](../metadata/metadata-editing.md) defined in Metabase, not based on constraints defined directly in your database. However, during [database sync](../../databases/sync-scan.md), Metabase automatically maps database foreign key constraints to foreign key semantic types, so in most cases you won't need to set these manually.If you've defined additional foreign key relationships in Metabase table metadata that don't have corresponding database constraints, schema viewer will display those as well.-Similarly, schema viewer displays entity keys based on the [Entity Key semantic type](../data-modeling/metadata-editing.md) defined in Metabase, not on primary key constraints in your database. During sync, Metabase automatically maps database primary keys to entity key semantic types, so they'll usually match. If you've manually set an entity key on a field that isn't a database primary key, schema viewer will display that as well.+Similarly, schema viewer displays entity keys based on the [Entity Key semantic type](../metadata/metadata-editing.md) defined in Metabase, not on primary key constraints in your database. During sync, Metabase automatically maps database primary keys to entity key semantic types, so they'll usually match. If you've manually set an entity key on a field that isn't a database primary key, schema viewer will display that as well.## Using the schema viewer@@ -49,13 +51,13 @@ In the schema viewer, you can:## Permissions for schema viewer-The schema viewer is part of Data Studio, which only people in the Admin or [Data Analysts](../people-and-groups/managing.md#data-analysts) groups can access.+The schema viewer is part of Data Studio, which only people in the Admin or [Data Analysts](../../people-and-groups/managing.md#data-analysts) groups can access.-The Data Analyst group additionally needs to have at least [query builder](../permissions/data.md) permissions for one or more tables in a database to use the schema viewer for that database.+The Data Analyst group additionally needs to have at least [query builder](../../permissions/data.md) permissions for one or more tables in a database to use the schema viewer for that database.## Further reading-- [Managing tables](./managing-tables.md)-- [Table metadata](../data-modeling/metadata-editing.md)-- [Syncs and scans](../databases/sync-scan.md)-- [Dependency graph](./dependencies/graph.md)+- [Managing tables](../metadata/managing-tables.md)+- [Table metadata](../metadata/metadata-editing.md)+- [Syncs and scans](../../databases/sync-scan.md)+- [Dependency graph](graph.md)diff --git a/docs/data-studio/transforms/addons.md b/docs/data-modeling/transforms/addons.mdsimilarity index 92%rename from docs/data-studio/transforms/addons.mdrename to docs/data-modeling/transforms/addons.mdindex 00e8a3bf614..82a725600ee 100644--- a/docs/data-studio/transforms/addons.md+++ b/docs/data-modeling/transforms/addons.md@@ -1,6 +1,8 @@---title: Transform add-onssummary: Metabase transforms come in two flavors - basic transforms for basic query-based functionality, and advanced transforms for Python workflows, transform inspector, and other functionality.+redirect_from:+ - /docs/latest/data-studio/transforms/addons---# Transform add-ons@@ -9,17 +11,17 @@ At a glance:[**Basic transforms**](#basic-transforms):-- Run [query-based transforms](query-transforms.md)+- Run [query-based transforms](query.md)- Schedule transform [jobs](jobs-and-runs.md).- (Pro/Enterprise only) Configure [permissions for transforms](transforms-overview.md#permissions-for-transforms).[**Advanced transforms**](#advanced-transforms):-- Run [query-based](query-transforms.md) and [Python transforms](python-transforms.md);+- Run [query-based](query.md) and [Python transforms](python.md);- Schedule transform [jobs](jobs-and-runs.md).- (Pro/Enterprise only) Configure [permissions for transforms](transforms-overview.md#permissions-for-transforms).- [Writable connection](../../databases/writable-connection.md): separate database connection used for write operations.-- [Transform inspector](transform-inspector.md).+- [Transform inspector](inspector.md).Availability and pricing depends on your plan and hosting method.@@ -27,7 +29,7 @@ Availability and pricing depends on your plan and hosting method.With basic transforms, you can:-- Write and run [query-based transforms](query-transforms.md) (but not Python transforms).+- Write and run [query-based transforms](query.md) (but not Python transforms).- [Schedule and run jobs](jobs-and-runs.md).- (Pro/Enterprise only) Configure [permissions for transforms](transforms-overview.md#permissions-for-transforms).@@ -48,9 +50,9 @@ Once basic transforms are enabled on your Metabase Cloud instance, they can't beAdvanced transforms include:- Everything in [basic transforms](#basic-transforms).-- [Python transforms](python-transforms.md) for more flexible data processing.+- [Python transforms](python.md) for more flexible data processing.- [Writable connection](../../databases/writable-connection.md): separate database connection used for write operations.-- [Transform inspector](transform-inspector.md).+- [Transform inspector](inspector.md).You can buy the Advanced transforms add-on for:diff --git a/docs/data-studio/transforms/transform-inspector.md b/docs/data-modeling/transforms/inspector.mdsimilarity index 95%rename from docs/data-studio/transforms/transform-inspector.mdrename to docs/data-modeling/transforms/inspector.mdindex 386400e568c..968d5f517c4 100644--- a/docs/data-studio/transforms/transform-inspector.md+++ b/docs/data-modeling/transforms/inspector.md@@ -1,6 +1,8 @@---title: Transform inspectorsummary: Analyze how your transforms process data by inspecting input and output shapes, join behavior, and column distributions.+redirect_from:+ - /docs/latest/data-studio/transforms/transform-inspector---# Transform inspector@@ -61,5 +63,5 @@ Inspector lenses run queries against your database, and some lenses can take lon## Further reading- [Transforms overview](transforms-overview.md)-- [Query-based transforms](query-transforms.md)-- [Python transforms](python-transforms.md)+- [Query-based transforms](query.md)+- [Python transforms](python.md)diff --git a/docs/data-studio/transforms/jobs-and-runs.md b/docs/data-modeling/transforms/jobs-and-runs.mdsimilarity index 99%rename from docs/data-studio/transforms/jobs-and-runs.mdrename to docs/data-modeling/transforms/jobs-and-runs.mdindex 5d71cd465ca..1618d9b30a9 100644--- a/docs/data-studio/transforms/jobs-and-runs.md+++ b/docs/data-modeling/transforms/jobs-and-runs.md@@ -1,6 +1,8 @@---title: Transform jobssummary: Run transforms on schedule.+redirect_from:+ - /docs/latest/data-studio/transforms/jobs-and-runs---# Transform jobsdiff --git a/docs/data-studio/transforms/python-runner.md b/docs/data-modeling/transforms/python-runner.mdsimilarity index 97%rename from docs/data-studio/transforms/python-runner.mdrename to docs/data-modeling/transforms/python-runner.mdindex 801cd8d322a..ecd97c8caa8 100644--- a/docs/data-studio/transforms/python-runner.md+++ b/docs/data-modeling/transforms/python-runner.md@@ -1,6 +1,8 @@---title: Python runnersummary: Configure self-hosted Python execution environment to run Python transforms in Metabase.+redirect_from:+ - /docs/latest/data-studio/transforms/python-runner---# Python runner@@ -198,6 +200,6 @@ Then bring everything up and try a transform:docker compose up -d```-3. You'll need a Pro or Enterprise license with the [Advanced transforms add-on](addons.md). In Metabase, [enable transforms](transforms-overview.md#enable-transforms), then [create a Python transform](python-transforms.md#create-a-python-transform) and click **Run**.+3. You'll need a Pro or Enterprise license with the [Advanced transforms add-on](addons.md). In Metabase, [enable transforms](transforms-overview.md#enable-transforms), then [create a Python transform](python.md#create-a-python-transform) and click **Run**.-4. Open **Data Studio > Jobs > Runs** and find your run. If it failed, the run's logs will usually tell you whether Metabase couldn't reach the runner, or the runner couldn't reach MinIO.\ No newline at end of file+4. Open **Data Studio > Jobs > Runs** and find your run. If it failed, the run's logs will usually tell you whether Metabase couldn't reach the runner, or the runner couldn't reach MinIO.diff --git a/docs/data-studio/transforms/python-transforms.md b/docs/data-modeling/transforms/python.mdsimilarity index 98%rename from docs/data-studio/transforms/python-transforms.mdrename to docs/data-modeling/transforms/python.mdindex 535267aecac..c782a9ad009 100644--- a/docs/data-studio/transforms/python-transforms.md+++ b/docs/data-modeling/transforms/python.md@@ -1,6 +1,8 @@---title: Python transformssummary: Use Python to wrangle your data in Metabase and write the results back to your database.+redirect_from:+ - /docs/latest/data-studio/transforms/python-transforms---# Python transforms@@ -129,5 +131,5 @@ To make a Python transform incremental:- Transform preview only uses 100 input rows from each input table.- DataFrame indexes, including indexes created by `groupby()`, are ignored from writing back to the database. If you're using a custom index that you'd like to include in the target table, you'll need to [reset index](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.reset_index.html) on your DataFrame inside the `transform()` function to make the index into a real column.- Only a [limited set of packages](#available-python-packages) are available for import. You can't install additional packages.-- Because Python transforms use `pandas`, all data manipulation is done in memory. The available memory is determined by the Python execution add-on. For large datasets, consider using [query-based transforms](./query-transforms.md) that run in your database.+- Because Python transforms use `pandas`, all data manipulation is done in memory. The available memory is determined by the Python execution add-on. For large datasets, consider using [query-based transforms](./query.md) that run in your database.- Only one Python transform can be run at any given time.diff --git a/docs/data-studio/transforms/query-transforms.md b/docs/data-modeling/transforms/query.mdsimilarity index 95%rename from docs/data-studio/transforms/query-transforms.mdrename to docs/data-modeling/transforms/query.mdindex 678e107b718..757af63b46b 100644--- a/docs/data-studio/transforms/query-transforms.md+++ b/docs/data-modeling/transforms/query.md@@ -1,6 +1,8 @@---title: Query-based transformssummary: Create Metabase questions and SQL queries to transform your data and write the results back into your data warehouse.+redirect_from:+ - /docs/latest/data-studio/transforms/query-transforms---# Query-based transforms@@ -172,7 +174,7 @@ You must be an admin to convert models, and the model's database must [support tTo convert a model into a transform:-1. Review [Replacing data sources](../dependencies/replace-data-sources.md) docs for overview and limitations of the process.+1. Review [Replacing data sources](../tools/replace-data-sources.md) docs for overview and limitations of the process.2. Open **Data Studio** and select **Transforms** in the sidebar.3. Click **Tools > Migrate models**.4. Find the model you want to convert and click it to open its details panel. The panel shows the model's name, database, and collection, and a list of items that depend on it.@@ -184,8 +186,8 @@ Metabase runs the conversion in the background. A status indicator at the bottomIf the transform run fails, Metabase stops and leaves the model unchanged—nothing is replaced.-If the transform runs successfully, but the source swap fails afterward, the transform and its output table are kept. The model is left unchanged. You can complete the migration manually using [Replace data sources](../dependencies/replace-data-sources.md) to point the remaining content from the model to the transform's output table.+If the transform runs successfully, but the source swap fails afterward, the transform and its output table are kept. The model is left unchanged. You can complete the migration manually using [Replace data sources](../tools/replace-data-sources.md) to point the remaining content from the model to the transform's output table.Once conversion completes, all content that previously queried the model now queries the transform's output table. The original model just becomes a question.-Newly created tables will be created with default permissions and will _not_ inherit the model's permissions. As an alternative, consider manually creating and running the transform first, setting up the permissions, then using [Replace data sources](../dependencies/replace-data-sources.md) to swap the model for the transform's output table once you configured permissions.+Newly created tables will be created with default permissions and will _not_ inherit the model's permissions. As an alternative, consider manually creating and running the transform first, setting up the permissions, then using [Replace data sources](../tools/replace-data-sources.md) to swap the model for the transform's output table once you configured permissions.diff --git a/docs/data-studio/transforms/transforms-overview.md b/docs/data-modeling/transforms/transforms-overview.mdsimilarity index 89%rename from docs/data-studio/transforms/transforms-overview.mdrename to docs/data-modeling/transforms/transforms-overview.mdindex 85bb0f05a07..abeaafa9ccd 100644--- a/docs/data-studio/transforms/transforms-overview.md+++ b/docs/data-modeling/transforms/transforms-overview.md@@ -1,6 +1,8 @@---title: Transforms overviewsummary: Transforms allow you to wrangle your data in Metabase, write the query results back to your database, and reuse them in Metabase as sources for new queries.+redirect_from:+ - /docs/latest/data-studio/transforms/transforms-overview---# Transforms@@ -20,7 +22,7 @@ You'll write a query or a Python script in Metabase, a transform will run this q- You assign tags (e.g., daily, hourly) to group your transforms.- A job runs on a schedule (e.g., every day at midnight) and executes all transforms that have been assigned a specific tag.- Each execution of a transform is a **run**. A run replaces the target table with fresh results. You can review the history of runs to monitor their success or failure.-- You can **inspect** a transform to analyze its data flow, join behavior, and column distributions. See [Transform inspector](transform-inspector.md).+- You can **inspect** a transform to analyze its data flow, join behavior, and column distributions. See [Transform inspector](inspector.md).## Databases that support transforms@@ -42,8 +44,8 @@ Transforms will create tables in your database, so the database user you use forMetabase supports two types of transforms: query-based transforms and Python transforms. You can write query-based transforms in SQL or Metabase Query builder, and they will run in your database. Python transforms are written in (unsurprisingly) Python and will run in a dedicated execution environment. For more details:-- [How query-based transforms work](query-transforms.md#how-query-based-transforms-work)-- [How Python transforms work](python-transforms.md#how-python-transforms-work)+- [How query-based transforms work](query.md#how-query-based-transforms-work)+- [How Python transforms work](python.md#how-python-transforms-work)## Permissions for transforms@@ -60,11 +62,11 @@ Permission configuration for transform depends on your plan.If you run Metabase yourself, here's the path to working transforms:-1. **Check your plan.** [Basic transforms](addons.md#basic-transforms) (query-based) are included on self-hosted Metabase. [Advanced transforms](addons.md#advanced-transforms) — Python transforms, the [transform inspector](transform-inspector.md), and [writable connections](../../databases/writable-connection.md) — need a self-hosted Pro or Enterprise plan with the Advanced transforms add-on.+1. **Check your plan.** [Basic transforms](addons.md#basic-transforms) (query-based) are included on self-hosted Metabase. [Advanced transforms](addons.md#advanced-transforms) — Python transforms, the [transform inspector](inspector.md), and [writable connections](../../databases/writable-connection.md) — need a self-hosted Pro or Enterprise plan with the Advanced transforms add-on.2. **Connect a database that can write.** Transforms create and replace tables in your database, so the database user needs create, drop, and write privileges. See [Database users, roles, and privileges](../../databases/users-roles-privileges.md). For cleaner isolation, point the transform at a [writable connection](../../databases/writable-connection.md). Only some databases [support transforms](#databases-that-support-transforms).3. **For Python transforms, set up a runner.** Query-based transforms need nothing extra — they run inside your database. Python transforms run in a separate execution environment, so you'll point Metabase at a [self-hosted Python runner](python-runner.md) backed by S3-compatible storage (AWS S3, MinIO, and so on).4. **[Enable transforms](#enable-transforms)** in Data Studio.-5. **Create and run a transform.** [Create a query-based transform](query-transforms.md#create-a-query-based-transform) or a [Python transform](python-transforms.md#create-a-python-transform), run it manually, and check the result under **Runs**. Once it works, [schedule it with jobs](jobs-and-runs.md).+5. **Create and run a transform.** [Create a query-based transform](query.md#create-a-query-based-transform) or a [Python transform](python.md#create-a-python-transform), run it manually, and check the result under **Runs**. Once it works, [schedule it with jobs](jobs-and-runs.md).## Enable transforms@@ -74,7 +76,7 @@ If you're on a Metabase Cloud plan, only people logged in with an email of a [MeTo enable transforms:-1. Navigate to [**Data Studio**](../overview.md) by click the **grid icon** in top right corner of your Metabase and selecing **Data Studio**.+1. Navigate to [**Data Studio**](../data-studio.md) by click the **grid icon** in top right corner of your Metabase and selecing **Data Studio**.2. In Data Studio, click **Transforms** in the right sidebar.3. If the transforms have not been enabled on your instance yet, you'll see a prompt to enable them. You can do just that.@@ -112,7 +114,7 @@ To create a transform:You can create your transform using Metabase's [graphical query builder](../../questions/query-builder/editor.md), SQL, or Python.- For more information on transforms built with the query builder or SQL, see [query-based transforms](query-transforms.md). For more information on Python transforms, see [Python transforms](python-transforms.md).+ For more information on transforms built with the query builder or SQL, see [query-based transforms](query.md). For more information on Python transforms, see [Python transforms](python.md).@@ -120,9 +122,9 @@ To create a transform:5. Create the query or script for your transform.- See [query-based transforms](query-transforms.md) and [Python transforms](python-transforms.md) for more information. You can reference target tables of other transforms when writing your transform.+ See [query-based transforms](query.md) and [Python transforms](python.md) for more information. You can reference target tables of other transforms when writing your transform.- If you're writing a SQL transform, variables _must_ be wrapped in optional blocks (`[[ ]]`), or given a default value. See [variables in SQL transforms](query-transforms.md#variables-in-sql-transforms) for more details.+ If you're writing a SQL transform, variables _must_ be wrapped in optional blocks (`[[ ]]`), or given a default value. See [variables in SQL transforms](query.md#variables-in-sql-transforms) for more details.If [Metabot is enabled](../../ai/settings.md#enable-ai-features), you can [use Metabot](#use-metabot-to-generate-code-for-transforms) to generate code for your transform.@@ -132,7 +134,7 @@ To create a transform:- **Schema** (required): Target schema for your transform. This schema can be different from the schema of the source table(s). You create a new schema by typing its name in this field. You can only transform data _within_ a database; you can't write from one database to another.- **Table name** (required): Name of the target table. Metabase will write the results of the transform into this table, and then sync the table in Metabase.- **Folder** (optional): The folder where the transform should live. Click on the field to pick a different folder or create a new one.- - **Incremental transformation** (optional): see [Incremental query-based transforms](query-transforms.md#incremental-query-transforms) or [Incremental Python transforms](python-transforms.md)+ - **Incremental transformation** (optional): see [Incremental query-based transforms](query.md#incremental-query-transforms) or [Incremental Python transforms](python.md)@@ -182,7 +184,7 @@ To edit the transform's query or script:2. Find the transform you'd like to edit and click on **Edit definition** above the transform definition.3. Edit the query or script.- See [query-based transforms](query-transforms.md) and [Python transforms](python-transforms.md) for more information. You can [use Metabot](#use-metabot-to-generate-code-for-transforms) to help edit your transform.+ See [query-based transforms](query.md) and [Python transforms](python.md) for more information. You can [use Metabot](#use-metabot-to-generate-code-for-transforms) to help edit your transform.Once you change the transform's query or script, the next transform run (manual or scheduled) will use the updated query and write the results into the target table. If you've changed the table's columns, and you have questions that query the table, they might break. For example, if your new transform query no longer includes a column that a downstream question was relying on, that question will break.@@ -202,7 +204,7 @@ You can run a transform manually or schedule the transform using tags and jobs.- To schedule a transform, you'll need to assign one or more tags to it, then create a [scheduled job](./jobs-and-runs.md) that picks up those tags.-Running a transform for the first time will create and sync the table created by the transform, and you'll be able to edit the table's [metadata](../../data-modeling/metadata-editing.md) and [permissions](../../permissions/data.md). Subsequent runs will drop and recreate the table, unless you use [Incremental transforms](#incremental-transforms).+Running a transform for the first time will create and sync the table created by the transform, and you'll be able to edit the table's [metadata](../metadata/metadata-editing.md) and [permissions](../../permissions/data.md). Subsequent runs will drop and recreate the table, unless you use [Incremental transforms](#incremental-transforms).You can see the time and status of the latest transform run on the transform's page, or in the [Runs view](./jobs-and-runs.md). The time of the run is given in the system's timezone.@@ -214,7 +216,7 @@ _Data Studio > Transforms > [transform name] > Inspect_> Transform inspector requires the [Advanced transforms add-on](addons.md)-The [transform inspector](./transform-inspector.md) lets you poke at the input and outputs of your transform.+The [transform inspector](./inspector.md) lets you poke at the input and outputs of your transform.## Transform dependencies@@ -274,7 +276,7 @@ Changing the checkpoint field also resets the stored value, so a transform will### Make a transform incremental-Incremental transforms work differently for query-based transforms and Python transforms, so see [incremental query transforms](query-transforms.md#incremental-query-transforms) and [incremental Python transforms](./python-transforms.md#incremental-python-transforms) for more information.+Incremental transforms work differently for query-based transforms and Python transforms, so see [incremental query transforms](query.md#incremental-query-transforms) and [incremental Python transforms](./python.md#incremental-python-transforms) for more information.## Versioning transforms@@ -303,4 +305,4 @@ Transforms are similar to models with model persistence turned on, but there areUse models to enable non-admins to create their own datasets within Metabase, and to add context like field descriptions and semantic types. Use transforms to create persisted datasets in your database and reuse them across Metabase. In future versions of Metabase, model persistence will be deprecated in favor of transforms.-On Metabase Pro/Enterprise plans, you can convert Metabase models to transforms in bulk, see [Convert models to transforms](query-transforms.md#convert-models-to-transforms)+On Metabase Pro/Enterprise plans, you can convert Metabase models to transforms in bulk, see [Convert models to transforms](query.md#convert-models-to-transforms)diff --git a/docs/data-studio/workspaces.md b/docs/data-modeling/workspaces.mdsimilarity index 97%rename from docs/data-studio/workspaces.mdrename to docs/data-modeling/workspaces.mdindex 016bc7a97d3..1c50c2919fb 100644--- a/docs/data-studio/workspaces.md+++ b/docs/data-modeling/workspaces.md@@ -1,6 +1,8 @@---title: Workspaces-summary: "Workspaces are isolation environments for AI agents. They let agents run data ransforms and develop analyses without touching the databases where the real data lives."+summary: "Workspaces are isolation environments for AI agents. They let agents run data transforms and develop analyses without touching the databases where the real data lives."+redirect_from:+ - /docs/latest/data-studio/workspaces---# Workspacesdiff --git a/docs/data-studio/images/data-studio.png b/docs/data-studio/images/data-studio.pngdeleted file mode 100644index 9c1b1de30fc..00000000000Binary files a/docs/data-studio/images/data-studio.png and /dev/null differdiff --git a/docs/data-studio/images/drill-lens.png b/docs/data-studio/images/drill-lens.pngdeleted file mode 100644index b7cff8fe0b3..00000000000Binary files a/docs/data-studio/images/drill-lens.png and /dev/null differdiff --git a/docs/data-studio/images/library-in-data-studio.png b/docs/data-studio/images/library-in-data-studio.pngdeleted file mode 100644index f4532b414f2..00000000000Binary files a/docs/data-studio/images/library-in-data-studio.png and /dev/null differdiff --git a/docs/data-studio/images/library-in-sidebar.png b/docs/data-studio/images/library-in-sidebar.pngdeleted file mode 100644index 5c48981df11..00000000000Binary files a/docs/data-studio/images/library-in-sidebar.png and /dev/null differdiff --git a/docs/data-studio/images/library-permissions.png b/docs/data-studio/images/library-permissions.pngdeleted file mode 100644index 9b09b78b06e..00000000000Binary files a/docs/data-studio/images/library-permissions.png and /dev/null differdiff --git a/docs/data-studio/images/transform-codegen.png b/docs/data-studio/images/transform-codegen.pngdeleted file mode 100644index 2750d2f64e0..00000000000Binary files a/docs/data-studio/images/transform-codegen.png and /dev/null differdiff --git a/docs/databases/connecting.md b/docs/databases/connecting.mdindex 6378688dcd5..e03dce15269 100644--- a/docs/databases/connecting.md+++ b/docs/databases/connecting.md@@ -83,6 +83,6 @@ If you've deleted the Metabase [Sample Database](https://www.metabase.com/glossa## Further reading-- [Metadata editing](../data-modeling/metadata-editing.md).+- [Metadata editing](../data-modeling/metadata/metadata-editing.md).- [Setting data access permissions](../permissions/data.md).- [Metabase at scale](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale).diff --git a/docs/databases/connections/athena.md b/docs/databases/connections/athena.mdindex 475e66b5f5f..601e7436aa7 100644--- a/docs/databases/connections/athena.md+++ b/docs/databases/connections/athena.md@@ -232,6 +232,6 @@ See [Danger Zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/bigquery.md b/docs/databases/connections/bigquery.mdindex cf11c6e5f4b..4a5d26bc343 100644--- a/docs/databases/connections/bigquery.md+++ b/docs/databases/connections/bigquery.md@@ -184,6 +184,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/databricks.md b/docs/databases/connections/databricks.mdindex b4c38289a1d..4d17efa3546 100644--- a/docs/databases/connections/databricks.md+++ b/docs/databases/connections/databricks.md@@ -124,6 +124,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/druid.md b/docs/databases/connections/druid.mdindex 674ee874a3c..1b504c31472 100644--- a/docs/databases/connections/druid.md+++ b/docs/databases/connections/druid.md@@ -34,7 +34,7 @@ See our [guide to SSH tunneling](../ssh-tunnel.md).This enables unfolding of JSON columns into their component fields.-See [JSON unfolding](../../data-modeling/json-unfolding.md).+See [JSON unfolding](../../data-modeling/metadata/json-unfolding.md).### Authentication@@ -79,6 +79,6 @@ See [Danger Zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/mariadb.md b/docs/databases/connections/mariadb.mdindex 680565d5cce..159e6da26da 100644--- a/docs/databases/connections/mariadb.md+++ b/docs/databases/connections/mariadb.md@@ -119,6 +119,6 @@ See [Danger zone](../danger-zone.md).- [MySQL](./mysql.md)- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/mysql.md b/docs/databases/connections/mysql.mdindex a604a168231..a8fa37131be 100644--- a/docs/databases/connections/mysql.md+++ b/docs/databases/connections/mysql.md@@ -64,7 +64,7 @@ See our [guide to SSH tunneling](../ssh-tunnel.md).For MySQL databases, Metabase can unfold JSON columns into component fields to yield a table where each JSON key becomes a column. JSON unfolding is on by default, but you can turn off JSON unfolding if performance is slow.-If you turn on JSON unfolding, you can also toggle the unfolding for individual columns in [table metadata](../../data-modeling/metadata-editing.md#unfold-json).+If you turn on JSON unfolding, you can also toggle the unfolding for individual columns in [table metadata](../../data-modeling/metadata/metadata-editing.md#unfold-json).### Additional JDBC connection string options@@ -193,15 +193,15 @@ Set up an additional connection used for write operations. See [Writable connect## Model features-Choose whether to enable features related to [Metabase models](../../data-modeling/models.md). These features will often require that the database user account, the one you use to connect to your database, has both read and write privileges.+Choose whether to enable features related to [Metabase models](../../data-modeling/models/models.md). These features will often require that the database user account, the one you use to connect to your database, has both read and write privileges.### Model actions-Turn this setting on to allow [actions](../../actions/introduction.md) from models created from this data to be run. Actions can read, write, and delete data. Your database user will need write permissions.+Turn this setting on to allow [actions](../../data-modeling/models/actions/introduction.md) from models created from this data to be run. Actions can read, write, and delete data. Your database user will need write permissions.### Model persistence-We'll create tables with model data and refresh them on a schedule you define. To enable [model persistence](../../data-modeling/model-persistence.md), you need to grant this connection's credentials read and write permissions on a schema Metabase provides.+We'll create tables with model data and refresh them on a schedule you define. To enable [model persistence](../../data-modeling/models/model-persistence.md), you need to grant this connection's credentials read and write permissions on a schema Metabase provides.## Editable table data@@ -225,6 +225,6 @@ See [Danger zone](../danger-zone.md).- [MariaDB](./mariadb.md)- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/oracle.md b/docs/databases/connections/oracle.mdindex 7fd62904c01..b21b5136dfd 100644--- a/docs/databases/connections/oracle.md+++ b/docs/databases/connections/oracle.md@@ -142,6 +142,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/postgresql.md b/docs/databases/connections/postgresql.mdindex edcef5f5958..77666e0cc78 100644--- a/docs/databases/connections/postgresql.md+++ b/docs/databases/connections/postgresql.md@@ -156,7 +156,7 @@ See our [guide to SSH tunneling](../ssh-tunnel.md).For PostgreSQL databases, Metabase can unfold JSON columns into component fields to yield a table where each JSON key becomes a column. JSON unfolding is on by default, but you can turn off JSON unfolding if performance is slow.-If you turn on JSON unfolding, you can also toggle the unfolding for individual columns in [table metadata](../../data-modeling/metadata-editing.md#unfold-json).+If you turn on JSON unfolding, you can also toggle the unfolding for individual columns in [table metadata](../../data-modeling/metadata/metadata-editing.md#unfold-json).### Additional JDBC connection string options@@ -192,15 +192,15 @@ Set up an additional connection used for write operations. See [Writable connect## Model features-Choose whether to enable features related to [Metabase models](../../data-modeling/models.md). These features will often require that the database user account, the one you use to connect to your database, has both read and write privileges.+Choose whether to enable features related to [Metabase models](../../data-modeling/models/models.md). These features will often require that the database user account, the one you use to connect to your database, has both read and write privileges.### Model actions-Turn this setting on to allow [actions](../../actions/introduction.md) from models created from this data to be run. Actions can read, write, and delete data. Your database user will need write permissions.+Turn this setting on to allow [actions](../../data-modeling/models/actions/introduction.md) from models created from this data to be run. Actions can read, write, and delete data. Your database user will need write permissions.### Model persistence-We'll create tables with model data and refresh them on a schedule you define. To enable [model persistence](../../data-modeling/model-persistence.md), you need to grant this connection's credentials read and write permissions on a schema Metabase provides.+We'll create tables with model data and refresh them on a schedule you define. To enable [model persistence](../../data-modeling/models/model-persistence.md), you need to grant this connection's credentials read and write permissions on a schema Metabase provides.## Editable table data@@ -223,6 +223,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/presto.md b/docs/databases/connections/presto.mdindex 0ead66d609d..904dd808660 100644--- a/docs/databases/connections/presto.md+++ b/docs/databases/connections/presto.md@@ -111,6 +111,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/redshift.md b/docs/databases/connections/redshift.mdindex aeac377a568..3e06f613fef 100644--- a/docs/databases/connections/redshift.md+++ b/docs/databases/connections/redshift.md@@ -110,7 +110,7 @@ Choose whether to enable features related to Metabase models. These will often rYou can enable model persistence to allow Metabase to create tables with model data and refresh them on a schedule. This requires write permissions to a designated schema.-Check out [Model persistence](../../data-modeling/model-persistence.md).+Check out [Model persistence](../../data-modeling/models/model-persistence.md).## Database routing@@ -125,6 +125,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/snowflake.md b/docs/databases/connections/snowflake.mdindex b47819dc152..870d95c34dd 100644--- a/docs/databases/connections/snowflake.md+++ b/docs/databases/connections/snowflake.md@@ -158,6 +158,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/sparksql.md b/docs/databases/connections/sparksql.mdindex 0ce83989b57..0424b7af51e 100644--- a/docs/databases/connections/sparksql.md+++ b/docs/databases/connections/sparksql.md@@ -88,6 +88,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/sql-server.md b/docs/databases/connections/sql-server.mdindex 35faf62c47f..a3811884ea9 100644--- a/docs/databases/connections/sql-server.md+++ b/docs/databases/connections/sql-server.md@@ -115,6 +115,6 @@ See [Danger zone](../danger-zone.md).- [Microsoft JDBC Driver for SQL Server support matrix](https://learn.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix)- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/connections/sqlite.md b/docs/databases/connections/sqlite.mdindex ff9386dcdfd..b64ed65cdbc 100644--- a/docs/databases/connections/sqlite.md+++ b/docs/databases/connections/sqlite.md@@ -78,6 +78,6 @@ See [Danger zone](../danger-zone.md).## Further reading- [Managing databases](../../databases/connecting.md)-- [Metadata editing](../../data-modeling/metadata-editing.md)-- [Models](../../data-modeling/models.md)+- [Metadata editing](../../data-modeling/metadata/metadata-editing.md)+- [Models](../../data-modeling/models/models.md)- [Setting data access permissions](../../permissions/data.md)diff --git a/docs/databases/sync-scan.md b/docs/databases/sync-scan.mdindex dd9227ffa96..1080df45f5d 100644--- a/docs/databases/sync-scan.md+++ b/docs/databases/sync-scan.md@@ -13,11 +13,11 @@ Metabase periodically runs different types of queries on your data warehouse to## Initial sync, scan, and fingerprinting-When Metabase first connects to your database, it performs a [sync](#how-database-syncs-work) to determine the metadata of the columns in your tables and automatically assign each column a [semantic type](../data-modeling/semantic-types.md).+When Metabase first connects to your database, it performs a [sync](#how-database-syncs-work) to determine the metadata of the columns in your tables and automatically assign each column a [semantic type](../data-modeling/metadata/semantic-types.md).You can follow the progress of these queries from **grid icon** >**Admin** > **Tools** > **Tasks** and filtering by the various sync tasks.-Once the queries are done running, you can view and edit the synced metadata from **Admin** > **Table Metadata**. For more info, see [editing metadata](../data-modeling/metadata-editing.md).+Once the queries are done running, you can view and edit the synced metadata from **Admin** > **Table Metadata**. For more info, see [editing metadata](../data-modeling/metadata/metadata-editing.md).## Choose when syncs and scans happen@@ -50,7 +50,7 @@ Options include:- **Only when adding a new filter widget** is a great option if you want scan queries to run on demand. Turning this option **ON** means that Metabase will only scan and cache the values of the field(s) that are used when someone adds a new filter widget to a dashboard or SQL question (i.e., they add a parameter to their SQL query).- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large or which never have new values added. Use the [Re-scan field values](#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.-Regardless of which option you pick, if you [set a field to use a dropdown list in filter widgets](../data-modeling/metadata-editing.md#filtering), Metabase will need to get values for that dropdown. Whenever someone uses that filter widget, Metabase will first look for cached values (valid for fourteen days) to populate that dropdown; otherwise, it will re-scan that field for the most up-to-date values.+Regardless of which option you pick, if you [set a field to use a dropdown list in filter widgets](../data-modeling/metadata/metadata-editing.md#filtering), Metabase will need to get values for that dropdown. Whenever someone uses that filter widget, Metabase will first look for cached values (valid for fourteen days) to populate that dropdown; otherwise, it will re-scan that field for the most up-to-date values.## Manually syncing tables and columns@@ -87,7 +87,7 @@ You can also tell Metabase to forget the cached values for individual fields by## Disabling syncing and scanning for specific tables-To prevent Metabase from running syncs and scans against a specific table, change the [table visibility](../data-modeling/metadata-editing.md#table-visibility) to **Hidden**:+To prevent Metabase from running syncs and scans against a specific table, change the [table visibility](../data-modeling/metadata/metadata-editing.md#table-visibility) to **Hidden**:1. Go to **Admin** > **Table Metadata** > your database.2. Hover over the table name in the sidebar.diff --git a/docs/databases/uploads.md b/docs/databases/uploads.mdindex 0360acbeac4..3c08620fa08 100644--- a/docs/databases/uploads.md+++ b/docs/databases/uploads.md@@ -51,7 +51,7 @@ If Metabase is connected to a database using a database user account with writeWhen people upload a CSV to a collection, Metabase will:- Create a table to store that data in the database and schema that the Admin selected to store uploads.-- Create a [model](../data-modeling/models.md) that wraps the uploaded table, and save that model to the collection the person uploaded the CSV data to.+- Create a [model](../data-modeling/models/models.md) that wraps the uploaded table, and save that model to the collection the person uploaded the CSV data to.## Specify a prefix for Metabase to prepend to the uploaded tablesdiff --git a/docs/databases/users-roles-privileges.md b/docs/databases/users-roles-privileges.mdindex 90dd63c75ea..8f655c5999a 100644--- a/docs/databases/users-roles-privileges.md+++ b/docs/databases/users-roles-privileges.md@@ -96,7 +96,7 @@ This is a good option if you're connecting to a local database for development o## Privileges to enable actions and editable table data-Both [actions](../actions/introduction.md) and the [editable table data](../data-modeling/editable-tables.md) let Metabase write back to specific tables in your database.+Both [actions](../data-modeling/models/actions/introduction.md) and the [editable table data](../data-modeling/editable-tables.md) let Metabase write back to specific tables in your database.If you're using actions or editable tables, then in addition to the [minimum database privileges](#minimum-database-privileges), you'll need to grant write access to any tables you want to be able to write to.@@ -117,7 +117,7 @@ GRANT metabase_writer TO metabase;## Privileges to enable model persistence-[Model persistence](../data-modeling/model-persistence.md) lets Metabase save query results to a specific schema in your database. Metabase's database user will need the `CREATE` privilege to set up the dedicated schema for model persistence, as well as write access (`INSERT`, `UPDATE`, `DELETE`) to that schema.+[Model persistence](../data-modeling/models/model-persistence.md) lets Metabase save query results to a specific schema in your database. Metabase's database user will need the `CREATE` privilege to set up the dedicated schema for model persistence, as well as write access (`INSERT`, `UPDATE`, `DELETE`) to that schema.In addition to the [minimum database privileges](#minimum-database-privileges):@@ -144,7 +144,7 @@ GRANT metabase_model_persistence TO metabase;## Privileges to enable transforms-[Transforms](../data-studio/transforms/transforms-overview.md) let Metabase write query results back to your database. We suggest that you create a dedicated schema for your transforms. Metabase's database user will need to be able to create and drop transform tables. We recommend using a [writable connection](./writable-connection.md) and only granting write access to the user used for the writable connection.+[Transforms](../data-modeling/transforms/transforms-overview.md) let Metabase write query results back to your database. We suggest that you create a dedicated schema for your transforms. Metabase's database user will need to be able to create and drop transform tables. We recommend using a [writable connection](./writable-connection.md) and only granting write access to the user used for the writable connection.In addition to the [minimum database privileges](#minimum-database-privileges):diff --git a/docs/databases/writable-connection.md b/docs/databases/writable-connection.mdindex 0e7b6bbfc45..f66c43adc43 100644--- a/docs/databases/writable-connection.md+++ b/docs/databases/writable-connection.md@@ -7,7 +7,7 @@ redirect_from:# Writable connection-> Writable connection requires the [Advanced transforms add-on](../data-studio/transforms/addons.md)+> Writable connection requires the [Advanced transforms add-on](../data-modeling/transforms/addons.md)_Admin > Databases > Writable connection_@@ -47,11 +47,11 @@ Once writable connection is removed, Metabase will revert to using the main connWhen configured, writable connection will be used for:-- [Transforms](../data-studio/transforms/transforms-overview.md)+- [Transforms](../data-modeling/transforms/transforms-overview.md)- [CSV uploads](../databases/uploads.md)- [Editable tables](../data-modeling/editable-tables.md)-- [Actions](../actions/introduction.md)-- [Model persistence](../data-modeling/model-persistence.md)+- [Actions](../data-modeling/models/actions/introduction.md)+- [Model persistence](../data-modeling/models/model-persistence.md)Your writable connection will need to have the privileges required for these operations. See [Users, roles, and privileges](./users-roles-privileges.md).diff --git a/docs/documents/introduction.md b/docs/documents/introduction.mdindex 6d25672d1ba..f120f6aad27 100644--- a/docs/documents/introduction.md+++ b/docs/documents/introduction.md@@ -30,7 +30,7 @@ You can type `@` to mention items from your Metabase (mentions get a fancy littl## Add charts to documents-You can add [questions](../questions/start.md) and [models](../data-modeling/models.md) to a document. You can either insert existing questions from your collections or create new questions directly in the document.+You can add [questions](../questions/start.md) and [models](../data-modeling/models/models.md) to a document. You can either insert existing questions from your collections or create new questions directly in the document.### Creating new questions in documentsdiff --git a/docs/embedding/ai-chat.md b/docs/embedding/ai-chat.mdindex a5951a097a5..a73a6286a2a 100644--- a/docs/embedding/ai-chat.md+++ b/docs/embedding/ai-chat.md@@ -13,7 +13,7 @@ redirect_from:You can embed an AI chat in your app, so people can ask questions of their data in natural language. Embedded chat is a focused version of [Metabot](../ai/metabot.md): it builds a question in the query builder and charts the answer.-To build that question, embedded chat first searches your Metabase for the best thing to build on: a [metric](../data-modeling/metrics.md), a [model](../data-modeling/models.md), a saved question, or a table (tables drop out once you [scope the chat to a collection](#set-up-ai-chat-in-metabase)). Then it writes a query against whatever it picked. So embedded chat does look through your saved content, but as raw material for a new question, not as results to hand back. What people get back is always a new question they can drill into, and save if you [turn saving on](#let-people-save-questions-metabot-creates).+To build that question, embedded chat first searches your Metabase for the best thing to build on: a [metric](../data-modeling/semantic-layer/metrics.md), a [model](../data-modeling/models/models.md), a saved question, or a table (tables drop out once you [scope the chat to a collection](#set-up-ai-chat-in-metabase)). Then it writes a query against whatever it picked. So embedded chat does look through your saved content, but as raw material for a new question, not as results to hand back. What people get back is always a new question they can drill into, and save if you [turn saving on](#let-people-save-questions-metabot-creates).Embedded chat won't write SQL, build or edit dashboards, or create metrics and models — it builds on the ones you already have. It also won't work as a search box for finding existing content. For those, chat will suggest doing the work in Metabase itself.diff --git a/docs/embedding/browser.md b/docs/embedding/browser.mdindex de3257ab366..63af894eb62 100644--- a/docs/embedding/browser.md+++ b/docs/embedding/browser.md@@ -82,7 +82,7 @@ So a default `<metabase-browser>` gives people **New question** and nothing elseBecause **New question** ignores `read-only`, people on a read-only browser can open the query builder and explore, but they won't be able to save what they build, or overwrite an existing question.-The new question button opens the query builder with every table, model, and saved question people have access to. To narrow down the list of entity types people can choose, list the entity types you want in `data-picker-entity-types`. Limiting people to [models](../data-modeling/models.md), for example, means they build on your curated data rather than on raw tables:+The new question button opens the query builder with every table, model, and saved question people have access to. To narrow down the list of entity types people can choose, list the entity types you want in `data-picker-entity-types`. Limiting people to [models](../data-modeling/models/models.md), for example, means they build on your curated data rather than on raw tables:```html<metabase-browserdiff --git a/docs/embedding/sdk/actions.md b/docs/embedding/sdk/actions.mdindex 4edf62d0fa7..77e6f8dbd7b 100644--- a/docs/embedding/sdk/actions.md+++ b/docs/embedding/sdk/actions.md@@ -7,7 +7,7 @@ summary: Trigger Metabase actions from your embedded application with the `useAc{% include plans-blockquote.html feature="Modular embedding SDK" sdk=true %}-With the `useAction` hook, you can trigger an [action](../../actions/introduction.md) when someone clicks a button or submits a form in your app.+With the `useAction` hook, you can trigger an [action](../../data-modeling/models/actions/introduction.md) when someone clicks a button or submits a form in your app.The hook handles the HTTP request, exposes loading and error state as React state, and types the parameters the action expects. Basic CRUD and custom SQL actions are supported; HTTP-type actions are not. Always trigger actions through `useAction` — calling `POST /api/action/:id/execute` directly with `fetch` may be blocked in sandboxed embedding contexts.@@ -161,4 +161,4 @@ Display the error message verbatim. Don't replace the message with a generic "So## Related-- [Actions documentation](../../actions/introduction.md)+- [Actions documentation](../../data-modeling/models/actions/introduction.md)diff --git a/docs/embedding/sdk/plugins.md b/docs/embedding/sdk/plugins.mdindex 887bfde24e8..885449093f8 100644--- a/docs/embedding/sdk/plugins.md+++ b/docs/embedding/sdk/plugins.md@@ -54,7 +54,7 @@ The function receives a URL string. Return `{ handled: true }` to prevent defaulThe plugin `handleLink` can only be used [globally](#plugin-scope) on provider level. `handleLink` is also available in [modular embedding](../modular-embedding.md#page-level-config) via `pluginsConfig` in `defineMetabaseConfig`, with the same API.-To create clickable links in your table columns, set the column's formatting to [display as link](../../data-modeling/formatting.md#display-as).+To create clickable links in your table columns, set the column's formatting to [display as link](../../data-modeling/metadata/formatting.md#display-as).### `getNoDataIllustration` and `getNoObjectIllustration`diff --git a/docs/exploration-and-organization/collections.md b/docs/exploration-and-organization/collections.mdindex 1d0b736fe18..4c18cfd985a 100644--- a/docs/exploration-and-organization/collections.md+++ b/docs/exploration-and-organization/collections.md@@ -46,7 +46,7 @@ To add an Official badge to a collection, an admin can visit the collection andThe Library is a special collection that helps you create a source of truth for analytics by providing a centrally managed set of curated content. Use the Library to separate authoritative, reusable components from ad-hoc analyses.-See [Library organization](../data-studio/library.md#library-organization).+See [Library organization](../data-modeling/semantic-layer/library.md#library-organization).## Collection permissions@@ -149,4 +149,4 @@ You can upload data to collections. See [Uploading data](./uploads.md).- [Multiple environments](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/multi-env#one-collection-per-environment)[dashboards]: ../dashboards/introduction.md-[models]: ../data-modeling/models.md+[models]: ../data-modeling/models/models.mddiff --git a/docs/exploration-and-organization/content-verification.md b/docs/exploration-and-organization/content-verification.mdindex 213a7b423e5..d61eabd18a2 100644--- a/docs/exploration-and-organization/content-verification.md+++ b/docs/exploration-and-organization/content-verification.md@@ -43,8 +43,8 @@ Dashboard verification works a little differently (since there's no underlying qAdmins can verify the following items:- [Questions](../questions/start.md)-- [Models](../data-modeling/models.md)-- [Metrics](../data-modeling/metrics.md)+- [Models](../data-modeling/models/models.md)+- [Metrics](../data-modeling/semantic-layer/metrics.md)- [Dashboards](../dashboards/introduction.md)Dashboard verification status has no effect on its questions. Questions must be verified independently.@@ -52,4 +52,4 @@ Dashboard verification status has no effect on its questions. Questions must be## Further reading- [Official collections](./collections.md#official-collections)-- [Library](../data-studio/library.md)+- [Library](../data-modeling/semantic-layer/library.md)diff --git a/docs/exploration-and-organization/data-model-reference.md b/docs/exploration-and-organization/data-model-reference.mdindex 63d99e4a3f0..49fd86039b6 100644--- a/docs/exploration-and-organization/data-model-reference.md+++ b/docs/exploration-and-organization/data-model-reference.md@@ -26,7 +26,7 @@ You can open the data reference from:You can also visit `https://[your metabase here]/reference`.-Admins and [Data Analysts](../people-and-groups/managing.md#data-analysts) can get a more comfortable view of data reference in [Data Studio](../data-studio/overview.md).+Admins and [Data Analysts](../people-and-groups/managing.md#data-analysts) can get a more comfortable view of data reference in [Data Studio](../data-modeling/data-studio.md).## Databases@@ -47,7 +47,7 @@ For each table, you can view:- Questions about this table (if you have permission to view them)- Option to create an X-ray of the table-Admins can edit the metadata in this reference by clicking the **Edit** button in the upper right. Admins can also edit metabadata in the [Admin](../data-modeling/metadata-editing.md).+Admins can edit the metadata in this reference by clicking the **Edit** button in the upper right. Admins can also edit metabadata in the [Admin](../data-modeling/metadata/metadata-editing.md).## Glossary@@ -59,7 +59,7 @@ The glossary is particularly useful for [Metabot](../ai/metabot.md). When Metabo-If your admins have created any [segments](../data-modeling/segments.md), you can browse them in this section.+If your admins have created any [segments](../data-modeling/semantic-layer/segments.md), you can browse them in this section.## Data reference in the native editor@@ -67,7 +67,7 @@ Sometimes when you're writing a query, you might forget the exact names of diffeTo bring up the data reference panel in the native/SQL editor, click on the open book icon.-This panel lists all the databases you have access to, and the [models](../data-modeling/models.md) and tables, and the fields inside of them.+This panel lists all the databases you have access to, and the [models](../data-modeling/models/models.md) and tables, and the fields inside of them.@@ -79,4 +79,4 @@ If you click on a column you’re interested in, you’ll see a description of iIn the data reference sidebar in the native editor, under **Connections**, you can find a list of table relationships (defined by [foreign keys](https://www.metabase.com/glossary/foreign-key)).-If a foreign key relationship exists in your database, but doesn't show up in your Metabase, your admin will need to update your [Metabase table metadata](../data-modeling/metadata-editing.md).+If a foreign key relationship exists in your database, but doesn't show up in your Metabase, your admin will need to update your [Metabase table metadata](../data-modeling/metadata/metadata-editing.md).diff --git a/docs/exploration-and-organization/delete-and-restore.md b/docs/exploration-and-organization/delete-and-restore.mdindex 103124ff3e9..ffd1172afd5 100644--- a/docs/exploration-and-organization/delete-and-restore.md+++ b/docs/exploration-and-organization/delete-and-restore.md@@ -132,11 +132,11 @@ Snippets can be archived and unarchived. See [Archiving snippets](../questions/n## Deleting segments-Segments can be retired. See [Retiring Segments](../data-modeling/segments.md#editing-and-retiring-segments). Retiring segments is permanent.+See [Delete segments](../data-modeling/semantic-layer/segments.md#delete-segments). Deleting segments is permanent, but it won't break questions that use the segment.## Deleting measures-See [Delete measures](../data-studio/measures.md#delete-measures). Deleting measures is permanent.+See [Delete measures](../data-modeling/semantic-layer/measures.md#delete-measures). Deleting measures is permanent.## Deleting subscriptions and alertsdiff --git a/docs/exploration-and-organization/events-and-timelines.md b/docs/exploration-and-organization/events-and-timelines.mdindex 4988fa252fa..921ad0824f7 100644--- a/docs/exploration-and-organization/events-and-timelines.md+++ b/docs/exploration-and-organization/events-and-timelines.md@@ -47,7 +47,7 @@ You'll see an icon along the x-axis that plots the event. A vertical line will e-You can't add a timeline with events to the [Library](../data-studio/library.md).+You can't add a timeline with events to the [Library](../data-modeling/semantic-layer/library.md).## Adding events when viewing a questiondiff --git a/docs/exploration-and-organization/exploration.md b/docs/exploration-and-organization/exploration.mdindex c59ca3bc87c..5d96e8200fb 100644--- a/docs/exploration-and-organization/exploration.md+++ b/docs/exploration-and-organization/exploration.md@@ -51,7 +51,7 @@ You can search by:-The left sidebar lists your databases, [models](../data-modeling/models.md), and [metrics](../data-modeling/metrics.md).+The left sidebar lists your databases, [models](../data-modeling/models/models.md), and [metrics](../data-modeling/semantic-layer/metrics.md).[Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans include the ability to filter for [verified models and metrics](./content-verification.md).@@ -68,8 +68,8 @@ To learn more, see the [data reference](./data-model-reference.md).Your teammates might have pinned some items to the top of your collection.- [dashboards](../dashboards/introduction.md)-- [models](../data-modeling/models.md)-- [metrics](../data-modeling/metrics.md)+- [models](../data-modeling/models/models.md)+- [metrics](../data-modeling/semantic-layer/metrics.md)- [questions](../questions/start.md)Collections have a list of any other items that are saved within them, and you can see what other collections are saved inside of the current one by checking out the navigation sidebar.@@ -108,9 +108,9 @@ To see the details of an individual record when viewing unaggregated tables, cliTo expand the details sidebar to a full page, click "Open in full page". Every record has a dedicated details page which you can link to.-Admins and people with [table metadata permissions](../permissions/data.md#manage-table-metadata-permissions) can set specific fields to display only in this details view. See [Table metadata](../data-modeling/metadata-editing.md).+Admins and people with [table metadata permissions](../permissions/data.md#manage-table-metadata-permissions) can set specific fields to display only in this details view. See [Table metadata](../data-modeling/metadata/metadata-editing.md).-If your record has a field containing [an image link](../data-modeling/formatting.md), Metabase will show the image as the record's icon in the detail view. If the record has a field with the "Entity name" name semantic type, or a field called `Title` or `Name` , Metabase will show this field as the name of the record.+If your record has a field containing [an image link](../data-modeling/metadata/formatting.md), Metabase will show the image as the record's icon in the detail view. If the record has a field with the "Entity name" name semantic type, or a field called `Title` or `Name` , Metabase will show this field as the name of the record.## Bookmarks@@ -134,4 +134,4 @@ Some things to remember with bookmarks:[collections]: ./collections.md[dashboards]: ../dashboards/start.md-[models]: ../data-modeling/models.md+[models]: ../data-modeling/models/models.mddiff --git a/docs/exploration-and-organization/history.md b/docs/exploration-and-organization/history.mdindex a2b30ef2ab6..cb6b593cf6b 100644--- a/docs/exploration-and-organization/history.md+++ b/docs/exploration-and-organization/history.md@@ -30,7 +30,7 @@ Metabase will keep track of a version each time you save, move, revert, [move to### Viewing tracked changes-1. Go to your transform in [Data studio](../data-studio/transforms/transforms-overview.md).+1. Go to your transform in [Data studio](../data-modeling/transforms/transforms-overview.md).2. Click the **three dots** icon and select **History**3. The History tab will display the item's history of up to 15 versions.@@ -38,12 +38,12 @@ Any change to the transform's query or script will be recorded as "changed sourc### Reverting to previous versions-1. Go to your transform in [Data studio > Transforms](../data-studio/transforms/transforms-overview.md).+1. Go to your transform in [Data studio > Transforms](../data-modeling/transforms/transforms-overview.md).2. Click the **three dots** icon and select **History**.3. Click the **back arrow** beside a version to revert your item to that point in time.## History for segments and measures-1. Go to the table source for the segment or measure in [Data Studio > Tables](../data-studio/managing-tables.md).+1. Go to the table source for the segment or measure in [Data Studio > Tables](../data-modeling/metadata/managing-tables.md).2. Pick the segment or measure in the right sidebar.3. On the segment or measure's page, go to **Revision history** tab.diff --git a/docs/exploration-and-organization/uploads.md b/docs/exploration-and-organization/uploads.mdindex 3647bc98713..1b5635a9d99 100644--- a/docs/exploration-and-organization/uploads.md+++ b/docs/exploration-and-organization/uploads.md@@ -41,13 +41,13 @@ You can also add data from [Google Sheets](../cloud/google-sheets.md) (MetabaseWhen you upload a CSV file, Metabase may ask to select a destination for that upload (depending on whether there are other uploads).-If your CSV has the same columns as a model from a previously uploaded file, you can append data to that model. Otherwise, you can create a new [model](../data-modeling/models.md). You can:+If your CSV has the same columns as a model from a previously uploaded file, you can append data to that model. Otherwise, you can create a new [model](../data-modeling/models/models.md). You can:- Create a new model- [Append to an existing model created by an upload](#appending-to-a-model-created-by-an-upload)- [Replace the data for an existing model created by an upload](#replacing-the-data-of-an-uploaded-model)-Metabase will create a [model](../data-modeling/models.md) that contains that CSV data, as well as the model's underlying table.+Metabase will create a [model](../data-modeling/models/models.md) that contains that CSV data, as well as the model's underlying table.## Appending to a model created by an uploaddiff --git a/docs/installation-and-operation/remote-sync.md b/docs/installation-and-operation/remote-sync.mdindex 5fe4188912e..13f0817dc1a 100644--- a/docs/installation-and-operation/remote-sync.md+++ b/docs/installation-and-operation/remote-sync.md@@ -39,8 +39,8 @@ We'll cover [setting up Remote Sync](#setting-up-remote-sync), an [example dev-tYou can sync:-- Your [Library](../data-studio/library.md)-- [Transforms](../data-studio/transforms/transforms-overview.md)+- Your [Library](../data-modeling/semantic-layer/library.md)+- [Transforms](../data-modeling/transforms/transforms-overview.md)- Any top-level collection under Our Analytics.- If you use [tenants](../embedding/tenants.md), you can also sync [shared collections](../embedding/tenants.md#collection-types).@@ -210,7 +210,7 @@ At this point, you should be all set up. Exit Admin, then reload your browser. Y### 8. Configure transforms syncing (optional)-To version your data transformation logic, you can sync your [Transforms](../data-studio/transforms/transforms-overview.md), including all your tags and jobs. Some things to keep in mind:+To version your data transformation logic, you can sync your [Transforms](../data-modeling/transforms/transforms-overview.md), including all your tags and jobs. Some things to keep in mind:- **Transform syncing is all or nothing**: Metabase will sync your entire transforms namespace. You can't selectively sync specific transform folders.- **This setting only determines whether Metabase pushes transforms from Read-write mode.** When you _pull_ from a repository, all content present in the repo is loaded—including any transforms—regardless of this setting. Think of it like pulling a repo that has a new collection you hadn't previously synced: the setting doesn't filter what comes in, only what goes out.@@ -502,9 +502,9 @@ If you want to switch fully to Remote Sync, we recommend starting with a new rep3. Move the content you want to sync into a synced collection.4. Push up your changes to the new repo.-Remote Sync does NOT sync table metadata, so if you're importing and exporting your [table metadata](../data-modeling/metadata-editing.md), you should stick with serialization.+Remote Sync does NOT sync table metadata, so if you're importing and exporting your [table metadata](../data-modeling/metadata/metadata-editing.md), you should stick with serialization.## Further reading-- [Library](../data-studio/library.md)+- [Library](../data-modeling/semantic-layer/library.md)- [Serialization](./serialization.md)diff --git a/docs/installation-and-operation/serialization.md b/docs/installation-and-operation/serialization.mdindex f16304d0050..68426d88a86 100644--- a/docs/installation-and-operation/serialization.md+++ b/docs/installation-and-operation/serialization.md@@ -306,7 +306,7 @@ Type: Boolean.Default: Data model is included.-Excludes [table metadata](../data-studio/managing-tables.md) settings, which admins define in **Data Studio > Data structure**. Excluding the data model is useful for subsequent exports where you only want content changes.+Excludes [table metadata](../data-modeling/metadata/managing-tables.md) settings, which admins define in **Data Studio > Data structure**. Excluding the data model is useful for subsequent exports where you only want content changes.### Include field valuesdiff --git a/docs/monitor/dependency-diagnostics.md b/docs/monitor/dependency-diagnostics.mdindex e08a9524967..15dc8b05595 100644--- a/docs/monitor/dependency-diagnostics.md+++ b/docs/monitor/dependency-diagnostics.md@@ -23,13 +23,13 @@ Dependency diagnostics has two tabs: **Broken dependencies** and **Unreferenced-Broken dependencies lists items that other content depends on, where a dependent item references a column or field the item no longer provides. This can happen when a column is removed or renamed, or when a field is hidden from the query builder by setting Visibility to **Do not include** in [metadata editing](../data-modeling/metadata-editing.md).+Broken dependencies lists items that other content depends on, where a dependent item references a column or field the item no longer provides. This can happen when a column is removed or renamed, or when a field is hidden from the query builder by setting Visibility to **Do not include** in [metadata editing](../data-modeling/metadata/metadata-editing.md).The broken dependencies table includes:- Tables- [Questions](../questions/introduction.md)-- [Models](../data-modeling/models.md)+- [Models](../data-modeling/models/models.md)For each item, the list shows:@@ -48,7 +48,7 @@ Selecting an item opens a details panel with:- The item's name, owner, and creation date- A list of missing or invalid columns, with copy buttons to help fix references- Downstream items that are broken because of this specific issue. You can filter this list by entity type-- Quick links to open items or view them in the [dependency graph](../data-studio/dependencies/graph.md)+- Quick links to open items or view them in the [dependency graph](../data-modeling/tools/graph.md)For tables created by transforms, the sidebar also shows a link to the source transform.@@ -84,8 +84,8 @@ Unreferenced entities includes:- Tables- [Questions](../questions/introduction.md)-- [Models](../data-modeling/models.md)-- [Metrics](../data-modeling/metrics.md)+- [Models](../data-modeling/models/models.md)+- [Metrics](../data-modeling/semantic-layer/metrics.md)- Segments- Measures- [Snippets](../questions/native-editor/snippets.md)@@ -101,6 +101,6 @@ Selecting an item opens a details panel with:- Who created the item and when- When it was last edited-- Links to open the item or view it in the [dependency graph](../data-studio/dependencies/graph.md)+- Links to open the item or view it in the [dependency graph](../data-modeling/tools/graph.md)For tables, the sidebar also shows owners, descriptions, and links to open the schema or database. For tables created by transforms, the sidebar shows a link to the source transform.diff --git a/docs/monitor/model-persistence-log.md b/docs/monitor/model-persistence-log.mdindex 17db76dd931..f74288849c4 100644--- a/docs/monitor/model-persistence-log.md+++ b/docs/monitor/model-persistence-log.md@@ -5,7 +5,7 @@ summary: View the status of persisted models and refresh their cached results.# Model persistence log-The Model persistence log lists your [persisted models](../data-modeling/model-persistence.md) and the status of their refreshes.+The Model persistence log lists your [persisted models](../data-modeling/models/model-persistence.md) and the status of their refreshes.To open the Model persistence log:@@ -14,7 +14,7 @@ To open the Model persistence log:For each persisted model, Metabase shows the:-- **Model**: The [model](../data-modeling/models.md) being persisted+- **Model**: The [model](../data-modeling/models/models.md) being persisted- **Collection**: The collection that contains the model- **Status**: The status of the last refresh- **Last run at**: When the model's results were last refresheddiff --git a/docs/people-and-groups/managing.md b/docs/people-and-groups/managing.mdindex 6814027530b..b6f291135db 100644--- a/docs/people-and-groups/managing.md+++ b/docs/people-and-groups/managing.md@@ -190,17 +190,17 @@ It's important that your All Users group should never have _greater_ access for{% include plans-blockquote.html feature="Data Analysts group" %}-You can add non-admins to the special **Data Analysts** group to give them access to [Data Studio](../data-studio/overview.md).+You can add non-admins to the special **Data Analysts** group to give them access to [Data Studio](../data-modeling/data-studio.md).By default (and you can't change this), the Data Analyst group gets:-- Access to [Data Studio](../data-studio/overview.md).-- [Curate permissions](../permissions/collections.md#curate-access) for the [Library collection](../data-studio/library.md)+- Access to [Data Studio](../data-modeling/data-studio.md).+- [Curate permissions](../permissions/collections.md#curate-access) for the [Library collection](../data-modeling/semantic-layer/library.md)- [Manage table metadata permissions](../permissions/data.md#manage-table-metadata-permissions) for _all_ tables in all databases in your Metabase.Other than the fixed access listed above, you can assign data, collection, and application permissions to the Data Analyst group as you would normally.-By default, a person in a Data Analysts group will have only read-only access to [Transforms](../data-studio/transforms/transforms-overview.md) that use tables which the person otherwise can view. To give a Data Analyst the ability to _create_ and _run_ transforms, you'll need to give them [transform permissions](../permissions/data.md#transform-permissions) on appropriate tables.+By default, a person in a Data Analysts group will have only read-only access to [Transforms](../data-modeling/transforms/transforms-overview.md) that use tables which the person otherwise can view. To give a Data Analyst the ability to _create_ and _run_ transforms, you'll need to give them [transform permissions](../permissions/data.md#transform-permissions) on appropriate tables.## Creating a groupdiff --git a/docs/permissions/collections.md b/docs/permissions/collections.mdindex 2c30815bd6b..e83a4125fd9 100644--- a/docs/permissions/collections.md+++ b/docs/permissions/collections.md@@ -114,7 +114,7 @@ A personal collection works just like any other collection except that its permi### Library collection-See [Permissions for the Library and its subcollections](../data-studio/library.md#library-permissions).+See [Permissions for the Library and its subcollections](../data-modeling/semantic-layer/library.md#library-permissions).Do not use collection permissions for **Library > Data** to control access to data in published tables. Use [Data permissions](data.md) instead.diff --git a/docs/permissions/data.md b/docs/permissions/data.mdindex 40b96992ebf..825694d8356 100644--- a/docs/permissions/data.md+++ b/docs/permissions/data.md@@ -158,7 +158,7 @@ Downloads of native queries are only allowed if a group has download permissions{% include plans-blockquote.html feature="Data model permissions" is_plural=true %}-You can define whether a group can [edit table metadata](../data-modeling/metadata-editing.md). Options are:+You can define whether a group can [edit table metadata](../data-modeling/metadata/metadata-editing.md). Options are:- Yes (meaning, they can edit metadata for that data source).- No@@ -190,7 +190,7 @@ See [Upload permissions](../databases/uploads.md#add-people-to-a-group-with-data{% include plans-blockquote.html feature="Transform permissions" is_plural=true %}-Transform permissions control who can manage and run [transforms](../data-studio/transforms/transforms-overview.md) on a database. Transform permissions can only be set on a database level, not on a table level.+Transform permissions control who can manage and run [transforms](../data-modeling/transforms/transforms-overview.md) on a database. Transform permissions can only be set on a database level, not on a table level.A group can only have transform permissions for a database if they also have "View data" and "Query builder and native" permissions for _all_ the tables in a database.diff --git a/docs/permissions/database-routing.md b/docs/permissions/database-routing.mdindex 63e01f42ea9..059121f4606 100644--- a/docs/permissions/database-routing.md+++ b/docs/permissions/database-routing.md@@ -44,9 +44,9 @@ Database routing **can't be used** on databases with:- [Writable connections](../databases/writable-connection.md)- [Editable tables](../data-modeling/editable-tables.md)-- [Actions](../actions/introduction.md)+- [Actions](../data-modeling/models/actions/introduction.md)- [CSV uploads](../databases/uploads.md)-- [Model persistence](../data-modeling/model-persistence.md)+- [Model persistence](../data-modeling/models/model-persistence.md)With **guest embedding**, database queries will always be routed to the router database. This is because guest embed users don't have Metabase accounts, so there are no user attributes available to determine which destination database to route to.diff --git a/docs/permissions/row-and-column-security.md b/docs/permissions/row-and-column-security.mdindex a933a70797e..2ecd504b787 100644--- a/docs/permissions/row-and-column-security.md+++ b/docs/permissions/row-and-column-security.md@@ -317,7 +317,7 @@ If you can't use SQL casting in Metabase, create a view in your database that co#### Option 3: Use transforms-Use a [transform](../data-studio/transforms/transforms-overview.md) to create a table that casts the advanced data type to a basic type. Then set up row and column security on the transformed table instead. You'll also need to block the original table.+Use a [transform](../data-modeling/transforms/transforms-overview.md) to create a table that casts the advanced data type to a basic type. Then set up row and column security on the transformed table instead. You'll also need to block the original table.### People with row and column security can't create Slack subscriptions or alertsdiff --git a/docs/questions/exporting-results.md b/docs/questions/exporting-results.mdindex 40861318e9c..823577a30c3 100644--- a/docs/questions/exporting-results.md+++ b/docs/questions/exporting-results.md@@ -24,8 +24,8 @@ You can export the results of a question as:You can choose between downloading the results as:-- **Formatted**: With any [formatting changes](../data-modeling/formatting.md) you've applied in Metabase.-- **Unformatted**: Metabase will export the raw results of the question without applying any of the [formatting you applied](../data-modeling/formatting.md) to the columns in the question. For example, if you formatted a floating point number to display only the first two decimal digits in the table results, exporting the unformatted results would include additional decimal digits (if any) found in the raw results.+- **Formatted**: With any [formatting changes](../data-modeling/metadata/formatting.md) you've applied in Metabase.+- **Unformatted**: Metabase will export the raw results of the question without applying any of the [formatting you applied](../data-modeling/metadata/formatting.md) to the columns in the question. For example, if you formatted a floating point number to display only the first two decimal digits in the table results, exporting the unformatted results would include additional decimal digits (if any) found in the raw results.If you don't see the option to export results, you may not have [permissions to download results](../permissions/data.md#download-results-permissions).diff --git a/docs/questions/introduction.md b/docs/questions/introduction.mdindex 5b3b9ac7caa..3540add3676 100644--- a/docs/questions/introduction.md+++ b/docs/questions/introduction.md@@ -88,7 +88,7 @@ Click the **bookmark** icon to pin a question to your Metabase sidebar. See [Boo## Turning a question into a model-You can turn a question saved to a collection into a model to let others know that the results make a good starting point for new questions. (You can't turn a question saved to a _dashboard_ into a model; you'll first need to move the question to a collection). See [models](../data-modeling/models.md).+You can turn a question saved to a collection into a model to let others know that the results make a good starting point for new questions. (You can't turn a question saved to a _dashboard_ into a model; you'll first need to move the question to a collection). See [models](../data-modeling/models/models.md).## Caching question resultsdiff --git a/docs/questions/metrics-explorer.md b/docs/questions/metrics-explorer.mdindex b2427ce5342..96bfc076da5 100644--- a/docs/questions/metrics-explorer.md+++ b/docs/questions/metrics-explorer.md@@ -5,7 +5,7 @@ summary: Explore metrics and measures across dimensions and compare them side by# Metrics explorer-The metrics explorer is a space for ad-hoc analysis of [metrics](../data-modeling/metrics.md) and [measures](../data-studio/measures.md)+The metrics explorer is a space for ad-hoc analysis of [metrics](../data-modeling/semantic-layer/metrics.md) and [measures](../data-modeling/semantic-layer/measures.md)@@ -32,7 +32,7 @@ To open a **metric** in the Metrics Explorer:1. Navigate to the metric's home page.- To get to the metric's home page, you can click on a metric from its collection, from the [metrics browser](../data-modeling/metrics.md#see-all-metrics), or from search.+ To get to the metric's home page, you can click on a metric from its collection, from the [metrics browser](../data-modeling/semantic-layer/metrics.md#see-all-metrics), or from search.2. To view the metric in the explorer, click **Explore** in the top right corner.@@ -46,7 +46,7 @@ To open a **measure** in the metrics explorer:When you open a measure or metric in the Metrics explorer, Metabase plots it along the most appropriate dimension. To change how the metric is broken out, click the current breakout dimension in the bottom controls to open the **Break out** sidebar.-The sidebar lists the metric's or measure's [dimensions](../data-modeling/metrics.md#metric-dimensions), excluding primary key and foreign key dimensions. The heading reads **Dimensions** when you select a single metric or measure, or **Shared dimensions** when you [compare](#compare-metrics-and-measures) multiple metrics or measures.+The sidebar lists the metric's or measure's [dimensions](../data-modeling/semantic-layer/metrics.md#metric-dimensions), excluding primary key and foreign key dimensions. The heading reads **Dimensions** when you select a single metric or measure, or **Shared dimensions** when you [compare](#compare-metrics-and-measures) multiple metrics or measures.To see the total result without any dimensions, select **No breakout**.diff --git a/docs/questions/native-editor/filter-widgets.md b/docs/questions/native-editor/filter-widgets.mdindex 04136354d4c..248f2b87fd7 100644--- a/docs/questions/native-editor/filter-widgets.md+++ b/docs/questions/native-editor/filter-widgets.md@@ -18,7 +18,7 @@ Date fields will either have a simple date filter (for date variables) or a dynaID parameters also support all three widget types (input box, search box, and dropdown list), so you can power an ID filter with a dropdown or search box instead of a plain input box.-If you want to change the default filter widget for a particular field, you'll need to ask an admin to update that field in [the Table Metadata](../../data-modeling/metadata-editing.md) and set the desired "Filtering on this field" option.+If you want to change the default filter widget for a particular field, you'll need to ask an admin to update that field in [the Table Metadata](../../data-modeling/metadata/metadata-editing.md) and set the desired "Filtering on this field" option.For dropdown lists and search boxes, you can also customize values available in the list. See below.diff --git a/docs/questions/native-editor/referencing-saved-questions-in-queries.md b/docs/questions/native-editor/referencing-saved-questions-in-queries.mdindex 9f05a2a96df..49a5d4d473f 100644--- a/docs/questions/native-editor/referencing-saved-questions-in-queries.md+++ b/docs/questions/native-editor/referencing-saved-questions-in-queries.md@@ -62,10 +62,10 @@ FROM## Further reading-- [Models](../../data-modeling/models.md)+- [Models](../../data-modeling/models/models.md)- [Snippets](./snippets.md)- [Snippets vs Saved Questions vs. Views](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/sql-in-metabase/organizing-sql)- [SQL troubleshooting guide](../../troubleshooting-guide/sql.md).[cte]: https://www.metabase.com/learn/sql/working-with-sql/sql-cte-[model]: ../../data-modeling/models.md+[model]: ../../data-modeling/models/models.mddiff --git a/docs/questions/native-editor/snippets.md b/docs/questions/native-editor/snippets.mdindex e8a6fc99dab..ee6f5cee4a2 100644--- a/docs/questions/native-editor/snippets.md+++ b/docs/questions/native-editor/snippets.md@@ -13,7 +13,7 @@ redirect_from:For example, if you frequently write queries that involve multiple tables, you can save the SQL code that joins those tables as a snippet so that you (and others in your organization) can reuse that code in multiple questions.-You can use snippets to define standardized KPIs and filters using SQL, just like you do with [metrics](../../data-modeling/metrics.md) and [segments](../../data-modeling/segments.md) in the query builder. For example, you may want to store exactly how you calculate revenue, or what constitutes an active user.+You can use snippets to define standardized KPIs and filters using SQL, just like you do with [metrics](../../data-modeling/semantic-layer/metrics.md) and [segments](../../data-modeling/semantic-layer/segments.md) in the query builder. For example, you may want to store exactly how you calculate revenue, or what constitutes an active user.You can also use snippets to define a set of reusable filters for SQL questions.@@ -185,7 +185,7 @@ Snippets are good for:How does your organization define a popular product? Is it by number of units sold? Or by reviews with an average rating greater than 4? You can define those qualifications for a popular product and codify them in a Snippet, `{% raw %}{{snippet: popular products}}{% endraw %}`, and have that code populate in every question that uses that snippet. If down the line this definition needs to change, simply update the snippet’s SQL, and the change will propagate to all questions that use that snippet.- Similar to how [segments](../../data-modeling/segments.md) (a named filter or set of filters) and [metrics](../../data-modeling/models.md) (a named computation) can standardize analytics in your organization, snippets offer a way to ensure correctness and consistency of SQL across teams.+ Similar to how [segments](../../data-modeling/semantic-layer/segments.md) (a named filter or set of filters) and [metrics](../../data-modeling/models/models.md) (a named computation) can standardize analytics in your organization, snippets offer a way to ensure correctness and consistency of SQL across teams.- **Efficiency**diff --git a/docs/questions/native-editor/table-variables.md b/docs/questions/native-editor/table-variables.mdindex 00ae5f778d8..4fee288a9b4 100644--- a/docs/questions/native-editor/table-variables.md+++ b/docs/questions/native-editor/table-variables.md@@ -110,7 +110,7 @@ In each question, open the Variables sidebar and map `{% raw %}{{table}}{% endra- **Not available as dashboard filter parameters.** You can't connect a table variable to a dashboard filter widget. Table variables must be set directly on each question.- **SQL queries only.** Table variables are available in native SQL queries, not in the query builder.- **No input widget.** There's no input widget for people to plug in a table. You must select the table to insert into the variable from the variables sidebar.-- **Not supported in transforms.** Table variables aren't available in [transforms](../../data-studio/transforms/transforms-overview.md) yet.+- **Not supported in transforms.** Table variables aren't available in [transforms](../../data-modeling/transforms/transforms-overview.md) yet.## Further readingdiff --git a/docs/questions/native-editor/writing-sql.md b/docs/questions/native-editor/writing-sql.mdindex 59dec8a3d28..a9ab6e0d201 100644--- a/docs/questions/native-editor/writing-sql.md+++ b/docs/questions/native-editor/writing-sql.md@@ -108,7 +108,7 @@ On databases that use [impersonation](../../permissions/impersonation.md), Metab## Question version history-For questions, [dashboards](../../dashboards/start.md), and [models](../../data-modeling/models.md), Metabase keeps a version history for the previous fifteen versions of that item.+For questions, [dashboards](../../dashboards/start.md), and [models](../../data-modeling/models/models.md), Metabase keeps a version history for the previous fifteen versions of that item.See [History](../../exploration-and-organization/history.md).diff --git a/docs/questions/query-builder/editor.md b/docs/questions/query-builder/editor.mdindex c0b62ec5acf..982ed6d97e5 100644--- a/docs/questions/query-builder/editor.md+++ b/docs/questions/query-builder/editor.md@@ -31,11 +31,11 @@ To the right of each step in the query builder is a **Preview** button (looks li## Pick data-To start building a question with the query builder, you need to select the data you want to work with. You can pick a table from a database, a [model](../../data-modeling/models.md), a [metric](../../data-modeling/metrics.md), or another saved question. You can search by typing, or browse your databases and collections.+To start building a question with the query builder, you need to select the data you want to work with. You can pick a table from a database, a [model](../../data-modeling/models/models.md), a [metric](../../data-modeling/semantic-layer/metrics.md), or another saved question. You can search by typing, or browse your databases and collections.-If your Metabase has the [Library collection](../../data-studio/library.md), then by default you'll only see the Data (tables) and Metrics from the library. To query other data sources, select "Browse all".+If your Metabase has the [Library collection](../../data-modeling/semantic-layer/library.md), then by default you'll only see the Data (tables) and Metrics from the library. To query other data sources, select "Browse all".diff --git a/docs/questions/query-builder/expressions.md b/docs/questions/query-builder/expressions.mdindex bc0418460fc..b8af4f47fc4 100644--- a/docs/questions/query-builder/expressions.md+++ b/docs/questions/query-builder/expressions.md@@ -91,7 +91,7 @@ You can refer to columns in the current table, or to columns that are linked via## Referencing Segments and Metrics-You can refer to saved [metrics](../../data-modeling/metrics.md) and [segments](../../data-modeling/segments.md) that are present in the currently selected table. You write these out the same as with columns, like this: `[Valid User Sessions]`.+You can refer to saved [metrics](../../data-modeling/semantic-layer/metrics.md) and [segments](../../data-modeling/semantic-layer/segments.md) that are present in the currently selected table. You write these out the same as with columns, like this: `[Valid User Sessions]`.## Filter expressions and conditionalsdiff --git a/docs/questions/query-builder/expressions/coalesce.md b/docs/questions/query-builder/expressions/coalesce.mdindex 2edf2d370bd..254a0be0033 100644--- a/docs/questions/query-builder/expressions/coalesce.md+++ b/docs/questions/query-builder/expressions/coalesce.md@@ -172,7 +172,7 @@ coalesce([Notes], [Comments] "No notes or comments.")- [Custom expressions tutorial][custom-expressions-learn][case-to-coalesce]: ./case.md#coalesce-[cast-data-type]: ../../../data-modeling/metadata-editing.md#cast-to-a-specific-data-type+[cast-data-type]: ../../../data-modeling/metadata/metadata-editing.md#cast-to-a-specific-data-type[custom-expressions-doc]: ../expressions.md[custom-expressions-learn]: https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/questions/custom-expressions[data-types]: https://www.metabase.com/learn/grow-your-data-skills/data-fundamentals/data-types-overview#examples-of-data-typesdiff --git a/docs/questions/query-builder/expressions/concat.md b/docs/questions/query-builder/expressions/concat.mdindex ac986f6b43e..9c264e263e8 100644--- a/docs/questions/query-builder/expressions/concat.md+++ b/docs/questions/query-builder/expressions/concat.md@@ -24,7 +24,7 @@ concat(value1, value2, ...)### Metabase will use unformatted values for non-string columns-When you use non-string columns in `concat`, Metabase will ignore any [formatting](../../../data-modeling/formatting.md) that you applied to the columns when converting the column to a string.+When you use non-string columns in `concat`, Metabase will ignore any [formatting](../../../data-modeling/metadata/formatting.md) that you applied to the columns when converting the column to a string.For example, if you formatted a number to display only the first two decimal digits in the table results, the results of `concat` would still include additional decimal digits (if any) found in the raw results.diff --git a/docs/questions/query-builder/expressions/converttimezone.md b/docs/questions/query-builder/expressions/converttimezone.mdindex dcce7ca1800..49ddb18526c 100644--- a/docs/questions/query-builder/expressions/converttimezone.md+++ b/docs/questions/query-builder/expressions/converttimezone.md@@ -100,7 +100,7 @@ For more gory details, see [Limitations](#limitations).We use "timestamp" and "datetime" to talk about any temporal data type that's supported by Metabase.-If your timestamps are stored as strings or numbers in your database, an admin can [cast them to timestamps](../../../data-modeling/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page.+If your timestamps are stored as strings or numbers in your database, an admin can [cast them to timestamps](../../../data-modeling/metadata/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page.To use `convertTimezone` without running into errors or pesky undetectable mistakes, you should know that there are a few varieties of `timestamp` data types:diff --git a/docs/questions/query-builder/expressions/datetimeadd.md b/docs/questions/query-builder/expressions/datetimeadd.mdindex 67d95aed50f..b01bc260e08 100644--- a/docs/questions/query-builder/expressions/datetimeadd.md+++ b/docs/questions/query-builder/expressions/datetimeadd.md@@ -85,7 +85,7 @@ case(between(now, [Opened On], [Finish By]), "Yes", "No")We use "timestamp" and "datetime" to talk about any temporal data type that's supported by Metabase. For more info about these data types in Metabase, see [Timezones](../../../configuring-metabase/timezones.md#data-types).-If your timestamps are stored as strings or numbers in your database, an admin can [cast them to timestamps](../../../data-modeling/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page.+If your timestamps are stored as strings or numbers in your database, an admin can [cast them to timestamps](../../../data-modeling/metadata/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page.## Limitationsdiff --git a/docs/questions/query-builder/expressions/datetimediff.md b/docs/questions/query-builder/expressions/datetimediff.mdindex 432e41cb485..0d6a2183939 100644--- a/docs/questions/query-builder/expressions/datetimediff.md+++ b/docs/questions/query-builder/expressions/datetimediff.md@@ -70,7 +70,7 @@ datetimeDiff([Aging Start], now, "day")We use "timestamp" and "datetime" to talk about any temporal data type that's supported by Metabase. For more info about these data types in Metabase, see [Timezones](../../../configuring-metabase/timezones.md#data-types).-If your timestamps are stored as strings or numbers in your database, an admin can [cast them to timestamps](../../../data-modeling/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page.+If your timestamps are stored as strings or numbers in your database, an admin can [cast them to timestamps](../../../data-modeling/metadata/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page.## Limitationsdiff --git a/docs/questions/query-builder/expressions/datetimesubtract.md b/docs/questions/query-builder/expressions/datetimesubtract.mdindex ef87f7f569a..0d74ba54b55 100644--- a/docs/questions/query-builder/expressions/datetimesubtract.md+++ b/docs/questions/query-builder/expressions/datetimesubtract.md@@ -85,7 +85,7 @@ case(between(now, [Depart At], [Arrive By]), "Yes", "No")We use "timestamp" and "datetime" to talk about any temporal data type that's supported by Metabase. For more info about these data types in Metabase, see [Timezones](../../../configuring-metabase/timezones.md#data-types).-If your timestamps are stored as strings or numbers in your database, an admin can [cast them to timestamps](../../../data-modeling/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page.+If your timestamps are stored as strings or numbers in your database, an admin can [cast them to timestamps](../../../data-modeling/metadata/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page.## Limitationsdiff --git a/docs/questions/query-builder/filters.md b/docs/questions/query-builder/filters.mdindex bead8d7fb4c..3c93ba5d8c0 100644--- a/docs/questions/query-builder/filters.md+++ b/docs/questions/query-builder/filters.md@@ -23,7 +23,7 @@ Depending on the data type of the column, Metabase will present different filter- **Numeric columns** let you add filters to only include rows in your table where this number is between two specific values, or is greater or less than a specific value, or is exactly equal to something.- **Text or category columns** let you specify that you only want to include data where this column is or isn't a specific option, whether it contains, starts with, or ends with a substring, or whether the row is empty or not.- **Date columns** give you a lot of options to filter by specific date ranges, relative date ranges, and more.-- **Structured data columns**, typically JSON or XML, can only be filtered by "Is empty" or "Not empty". Some databases, however, support [JSON unfolding](../../data-modeling/json-unfolding.md), which allows you to split up JSON data into separate columns, which you can then filter on.+- **Structured data columns**, typically JSON or XML, can only be filtered by "Is empty" or "Not empty". Some databases, however, support [JSON unfolding](../../data-modeling/metadata/json-unfolding.md), which allows you to split up JSON data into separate columns, which you can then filter on.- **Latitude and longitude columns** will have the same options as numeric columns, but also a special "Inside" filter type that will let you filter on both latitude and longitude simultaneously.## Filtering by date@@ -43,4 +43,4 @@ Learn more about writing [expressions](./expressions.md) or skip right to the [l## Filtering by a segment-If your Metabase administrators have created special named filters for the table you're viewing, they’ll appear at the top of the filter dropdown in purple text with a star next to them. These are called [**Segments**](../../data-modeling/segments.md), and they're shortcuts to a combination of filters that are commonly used in your organization. They might be called things like “Active Users,” or “Most Popular Products.”+If your Metabase administrators have created special named filters for the table you're viewing, they’ll appear at the top of the filter dropdown in purple text with a star next to them. These are called [**Segments**](../../data-modeling/semantic-layer/segments.md), and they're shortcuts to a combination of filters that are commonly used in your organization. They might be called things like “Active Users,” or “Most Popular Products.”diff --git a/docs/questions/query-builder/summarizing-and-grouping.md b/docs/questions/query-builder/summarizing-and-grouping.mdindex de8111310dc..b37478448ec 100644--- a/docs/questions/query-builder/summarizing-and-grouping.md+++ b/docs/questions/query-builder/summarizing-and-grouping.md@@ -48,7 +48,7 @@ If you summarize and add a grouping you can then summarize _again_. You can alsoYou can also add metrics and groupings on the results page in a sidebar: the top of the sidebar is where you pick the number ("metric") you want to see, and the part below is where you pick how to group that number (or how to "break it out").-If your admins have created any named [metrics](../../data-modeling/metrics.md) or [measures](../../data-studio/measures.md) that are specific to your company or organization, they will be in this dropdown under the **Metrics** or **Measures** section. These might be things like your company’s official way of calculating revenue.+If your admins have created any named [metrics](../../data-modeling/semantic-layer/metrics.md) or [measures](../../data-modeling/semantic-layer/measures.md) that are specific to your company or organization, they will be in this dropdown under the **Metrics** or **Measures** section. These might be things like your company’s official way of calculating revenue.By default, Metabase will limit the number of aggregated rows displayed to 10,000 rows. You can change this limit with the environment variable [`MB_AGGREGATED_QUERY_ROW_LIMIT`](../../configuring-metabase/environment-variables.md#mb_aggregated_query_row_limit).diff --git a/docs/questions/visualizations/drill-through.md b/docs/questions/visualizations/drill-through.mdindex 6bac1083555..ee671606b8c 100644--- a/docs/questions/visualizations/drill-through.md+++ b/docs/questions/visualizations/drill-through.md@@ -126,13 +126,13 @@ A custom click behavior replaces the drill-through menu with an action you defin### 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.md) and build the user-facing question with the query builder.+If you need native SQL but also want to use the full drill-through menu, write your SQL query as a [transform](../../data-modeling/transforms/transforms-overview.md) 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.md).+> To create transforms, you must have transform permissions. If you use Metabase Cloud, you must also have the [transform add-on](../../data-modeling/transforms/addons.md).## Drill-through and embeddingdiff --git a/docs/questions/visualizations/map.md b/docs/questions/visualizations/map.mdindex 3ec5f907d9a..583c7a351c7 100644--- a/docs/questions/visualizations/map.md+++ b/docs/questions/visualizations/map.md@@ -13,7 +13,7 @@ Metabase has three types of map visualization:- [**Grid map**](#grid-map) for distributing a large number of points over a specified area.- [**Region map**](#region-maps) for data broken out by regions, like countries or states. Metabase comes with two built-in maps, but you can upload your own custom regions.-When you select the **Map** visualization setting, Metabase will automatically try and pick the best kind of map to use based on the table or result set, as long as the columns with the geographic data have the [right metadata](../../data-modeling/metadata-editing.md).+When you select the **Map** visualization setting, Metabase will automatically try and pick the best kind of map to use based on the table or result set, as long as the columns with the geographic data have the [right metadata](../../data-modeling/metadata/metadata-editing.md).@@ -38,7 +38,7 @@ To create a pin map:1. Build a query with latitude and longitude columns for each data point (either in the query builder or using SQL);2. Select **Visualization**, and pick **Map**;-3. If your query results have columns whose field type is set to latitude/longitude in [table metadata](../../data-modeling/metadata-editing.md#semantic-type), Metabase should build a pin map automatically.+3. If your query results have columns whose field type is set to latitude/longitude in [table metadata](../../data-modeling/metadata/metadata-editing.md#semantic-type), Metabase should build a pin map automatically.Otherwise, click on the **Gear** icon to go to visualization settings, choose **Map type: Pin map**, and pick columns that contain latitude and longitude coordinates.@@ -83,7 +83,7 @@ To create a grid map:1. Build a query with summary by binned latitude and longitude columns (either in the query builder or using SQL);2. Select **Visualization**, and pick **Map**;-3. If your query results have columns whose field type is set to latitude/longitude in [table metadata](../../data-modeling/metadata-editing.md#semantic-type), Metabase should build a grid map automatically.+3. If your query results have columns whose field type is set to latitude/longitude in [table metadata](../../data-modeling/metadata/metadata-editing.md#semantic-type), Metabase should build a grid map automatically.Otherwise, click on the **Gear** icon to go to visualization settings, choose **Map type: grid map**, and pick columns that contain latitude and longitude coordinates.@@ -135,7 +135,7 @@ To visualize your results in the format of a map of the world broken out by counThe country codes in the query results must match the two-letter codes exactly: if the country codes are lowercase or contain extra spaces, Metabase won't recognize them.-If your query result has columns with [semantic type](../../data-modeling/metadata-editing.md#semantic-type) "Country", Metabase should build a world map automatically. Otherwise, you can choose which columns to use as the country name in the **Region field** visualization setting.+If your query result has columns with [semantic type](../../data-modeling/metadata/metadata-editing.md#semantic-type) "Country", Metabase should build a world map automatically. Otherwise, you can choose which columns to use as the country name in the **Region field** visualization setting.You can connect the country column in the world region map to a "Location" type dashboard filter.@@ -150,7 +150,7 @@ Creating a map of the United States from your data requires your results to cont| Texas | 34 || Illinois | 67 |-If your query result has columns with [semantic type](../../data-modeling/metadata-editing.md#semantic-type) "State", Metabase should build a US map automatically. Otherwise, you can choose which columns to use as the country name in the visualization settings.+If your query result has columns with [semantic type](../../data-modeling/metadata/metadata-editing.md#semantic-type) "State", Metabase should build a US map automatically. Otherwise, you can choose which columns to use as the country name in the visualization settings.You can connect the state column in the US region map to a "Location" type dashboard filter.diff --git a/docs/questions/visualizations/pivot-table.md b/docs/questions/visualizations/pivot-table.mdindex 3e2d7971d5a..1987fdb0f2f 100644--- a/docs/questions/visualizations/pivot-table.md+++ b/docs/questions/visualizations/pivot-table.md@@ -102,4 +102,4 @@ There are special considerations when exporting pivot tables as XLSX files. See- Pivot tables are only available for questions built with the query builder.- The query builder question must have a summary block.-If you must use SQL, and your SQL query doesn't have parameters, you can save that SQL query, then use its [results as the starting point](../native-editor/writing-sql.md#explore-sql-question-results-using-the-query-builder) for a query builder question to build a question. The trick here is to do your aggregation and grouping in the query builder. That is, use the SQL question to grab the raw data you want to work with (maybe [create a model](../../data-modeling/models.md)), then start a new question in the query builder to filter, summarize, and group that data.+If you must use SQL, and your SQL query doesn't have parameters, you can save that SQL query, then use its [results as the starting point](../native-editor/writing-sql.md#explore-sql-question-results-using-the-query-builder) for a query builder question to build a question. The trick here is to do your aggregation and grouping in the query builder. That is, use the SQL question to grab the raw data you want to work with (maybe [create a model](../../data-modeling/models/models.md)), then start a new question in the query builder to filter, summarize, and group that data.diff --git a/docs/questions/visualizations/table.md b/docs/questions/visualizations/table.mdindex b86dbe14c13..e2f65d5afb3 100644--- a/docs/questions/visualizations/table.md+++ b/docs/questions/visualizations/table.md@@ -20,7 +20,7 @@ When viewing tables, you can click on the **gear** icon in the bottom left to br-Admins (and people in groups with access to table metadata) can hide columns across your entire Metabase by marking them as hidden in the [table metadata settings](../../data-modeling/metadata-editing.md#field-visibility).+Admins (and people in groups with access to table metadata) can hide columns across your entire Metabase by marking them as hidden in the [table metadata settings](../../data-modeling/metadata/metadata-editing.md#field-visibility).> **Hiding columns should _not_ be used to secure sensitive information**. Hiding columns in table visualization settings only affects the visibility of the columns _in the visualization_, not in the query results. Even people with view-only permissions to the question will be able to change the visualization settings and unhide columns. To exclude a column from the results of a specific query, uncheck the column in the "Data" block of the query builder.diff --git a/docs/questions/visualizations/tooltips.md b/docs/questions/visualizations/tooltips.mdindex 320418415b5..b5d89ecd924 100644--- a/docs/questions/visualizations/tooltips.md+++ b/docs/questions/visualizations/tooltips.md@@ -14,7 +14,7 @@ When you hover over a data point on a chart in Metabase, you'll see a tooltip abOn line, bar, and area charts, you can display the values from multiple metrics either on the chart, or in the tooltips that Metabase adds to the data points on hover.-For example, if you have a question with two metrics (i.e., two summarizations - they don't have to be Metabase [metrics](../../data-modeling/metrics.md)), like this question that has both the count and average of subtotal:+For example, if you have a question with two metrics (i.e., two summarizations - they don't have to be Metabase [metrics](../../data-modeling/semantic-layer/metrics.md)), like this question that has both the count and average of subtotal:diff --git a/docs/questions/visualizations/visualizing-results.md b/docs/questions/visualizations/visualizing-results.mdindex 7a55f1b634b..437bd62245c 100644--- a/docs/questions/visualizations/visualizing-results.md+++ b/docs/questions/visualizations/visualizing-results.md@@ -186,7 +186,7 @@ You can access formatting options for the columns used in a chart. Just open theOptions differ depending on the chart, and can include settings for the chart's data, its display, and its axes.-See also [Formatting defaults](../../data-modeling/formatting.md).+See also [Formatting defaults](../../data-modeling/metadata/formatting.md).## Further readingdiff --git a/docs/troubleshooting-guide/cant-see-tables.md b/docs/troubleshooting-guide/cant-see-tables.mdindex bfe4be20548..df70bba006c 100644--- a/docs/troubleshooting-guide/cant-see-tables.md+++ b/docs/troubleshooting-guide/cant-see-tables.md@@ -6,7 +6,7 @@ title: I can't see my tablesYou've connected Metabase to a database, but:-- you don't see the tables in the [Table Metadata](../data-modeling/metadata-editing.md) section of the Admin Panel,+- you don't see the tables in the [Table Metadata](../data-modeling/metadata/metadata-editing.md) section of the Admin Panel,- the tables don't appear in the [Data Browser](../exploration-and-organization/data-model-reference.md),- the tables don't show up as possible data sources when you create a query using the Query Builder, or- you can no longer see tables that you used to be able to see.@@ -85,7 +85,7 @@ MongoDB lets you "successfully connect" to any collection name, even if the coll## Related topics-- [Table visibility](../data-modeling/metadata-editing.md#table-visibility).+- [Table visibility](../data-modeling/metadata/metadata-editing.md#table-visibility).- [Row and column security isn't working](./row-and-column-security.md)- [I can't view or edit a question or dashboard](./cant-view-or-edit.md).- [My visualizations are wrong](./visualization.md).diff --git a/docs/troubleshooting-guide/filters.md b/docs/troubleshooting-guide/filters.mdindex e5913d27fb9..de830795e90 100644--- a/docs/troubleshooting-guide/filters.md+++ b/docs/troubleshooting-guide/filters.md@@ -32,7 +32,7 @@ If a question filter is giving you no results or the wrong results:- asking your database admin.3. Ask your Metabase admin to help you check if:- Metabase is [up to date](../databases/sync-scan.md) with your database,- - the column is [visible](../data-modeling/metadata-editing.md#field-visibility) in Metabase,+ - the column is [visible](../data-modeling/metadata/metadata-editing.md#field-visibility) in Metabase,- you have the correct [data permissions](../permissions/data.md) to access the column.### Special cases@@ -62,10 +62,10 @@ To debug dashboard and question filters that involve timestamps, UUIDs, or numer1. Find the [data type](https://www.metabase.com/learn/grow-your-data-skills/data-fundamentals/data-types-overview) of the column that you want to filter on. You can find this info from:- the [Data reference](../exploration-and-organization/data-model-reference.md),- - the [Table Metadata page](../data-modeling/metadata-editing.md) (admins only), or+ - the [Table Metadata page](../data-modeling/metadata/metadata-editing.md) (admins only), or- directly from the database.2. Cast the column to a data type that matches the desired [filter type](../questions/query-builder/filters.md#filter-types). You can:- - [cast strings or numbers to dates](../data-modeling/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page, or+ - [cast strings or numbers to dates](../data-modeling/metadata/metadata-editing.md#cast-to-a-specific-data-type) from the Table Metadata page, or- change the data type of the column in your database, and [re-sync](../databases/sync-scan.md#manually-syncing-tables-and-columns) the database schema.If you're not a Metabase admin, you might have to ask your admin to help you with some of these steps.@@ -100,7 +100,7 @@ Metabase [scans](../databases/sync-scan.md#how-database-scans-work) get the valu- [Troubleshooting linked filters](./linked-filters.md)- [Troubleshooting SQL variables and field filters](./sql.md#sql-variables-and-field-filters)- [Troubleshooting dates and times](./timezones.md)-- [Creating dropdown filters](../data-modeling/metadata-editing.md#changing-a-search-box-filter-to-a-dropdown-filter)+- [Creating dropdown filters](../data-modeling/metadata/metadata-editing.md#changing-a-search-box-filter-to-a-dropdown-filter)- [Creating SQL filters](../questions/native-editor/sql-parameters.md)## Are you still stuck?diff --git a/docs/troubleshooting-guide/models.md b/docs/troubleshooting-guide/models.mdindex 0c8cba27c97..c0535e683ec 100644--- a/docs/troubleshooting-guide/models.md+++ b/docs/troubleshooting-guide/models.md@@ -68,8 +68,8 @@ If you can’t solve your problem using the troubleshooting guides:[limit-data-learn]: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/making-dashboards-faster#ask-for-less-data[materialize-views-learn]: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/making-dashboards-faster#materialize-views-create-new-tables-to-store-query-results[model-button-image]: ./images/model-icon.png-[model-docs]: ../data-modeling/models.md+[model-docs]: ../data-modeling/models/models.md[replicate-database-learn]: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/making-dashboards-faster#replicate-your-database[sql-explain-learn]: https://www.metabase.com/learn/sql/working-with-sql/sql-best-practices#explain[summary-tables-learn]: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/making-dashboards-faster#aggregate-data-ahead-of-time-with-summary-tables-[model-persistence]: ../data-modeling/model-persistence.md+[model-persistence]: ../data-modeling/models/model-persistence.mddiff --git a/docs/troubleshooting-guide/permissions.md b/docs/troubleshooting-guide/permissions.mdindex 7ac2b6bea3c..3dd2e85c570 100644--- a/docs/troubleshooting-guide/permissions.md+++ b/docs/troubleshooting-guide/permissions.md@@ -50,8 +50,8 @@ If you can’t solve your problem using the troubleshooting guides:[collection-permissions]: ../permissions/collections.md[collections-restricted-data]: ./data-permissions.md#a-user-group-can-view-collections-that-contain-restricted-data[connecting-database]: ../databases/connecting.md+[data-model]: ../data-modeling/metadata/metadata-editing.md[data-browser]: ../exploration-and-organization/data-model-reference.md-[data-model]: ../data-modeling/metadata-editing.md[data-permissions]: ../permissions/data.md[discourse]: https://discourse.metabase.com/[group-permissions]: ../permissions/introduction.md#key-points-regarding-permissionsdiff --git a/docs/troubleshooting-guide/row-and-column-security.md b/docs/troubleshooting-guide/row-and-column-security.mdindex a0af9aa48ca..716824b4b4f 100644--- a/docs/troubleshooting-guide/row-and-column-security.md+++ b/docs/troubleshooting-guide/row-and-column-security.md@@ -166,8 +166,8 @@ The administrator can [create a new group][groups] to capture precisely who's al[authenticating-with-saml]: ../people-and-groups/authenticating-with-saml.md[cant-see-tables]: cant-see-tables.md+[data-model]: ../data-modeling/metadata/metadata-editing.md[column-permissions]: https://www.metabase.com/learn/metabase-basics/administration/permissions/column-permissions-[data-model]: ../data-modeling/metadata-editing.md[data-permissions]: https://www.metabase.com/learn/metabase-basics/administration/permissions/data-permissions[groups]: ../people-and-groups/managing.md#groups[jwt-auth]: ../people-and-groups/authenticating-with-jwt.mddiff --git a/docs/troubleshooting-guide/sql.md b/docs/troubleshooting-guide/sql.mdindex 6d3d12cea66..05f695ef6bd 100644--- a/docs/troubleshooting-guide/sql.md+++ b/docs/troubleshooting-guide/sql.md@@ -14,7 +14,7 @@ title: Troubleshooting SQL questions## SQL variables and field filters-- [Filter widget doesn't display a dropdown menu of values](../data-modeling/metadata-editing.md#changing-a-search-box-filter-to-a-dropdown-filter).+- [Filter widget doesn't display a dropdown menu of values](../data-modeling/metadata/metadata-editing.md#changing-a-search-box-filter-to-a-dropdown-filter).- [SQL query contains table aliases](../questions/native-editor/field-filters.md#specifying-the-table-and-field-alias).- [SQL syntax error: missing `FROM` clause](../questions/native-editor/field-filters.md#field-filters-must-be-connected-to-database-fields-included-in-the-query).- [I don't know the SQL variable type](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/sql-in-metabase/sql-variables)diff --git a/docs/troubleshooting-guide/sync-fingerprint-scan.md b/docs/troubleshooting-guide/sync-fingerprint-scan.mdindex 71dfd448519..0faf2c19bf9 100644--- a/docs/troubleshooting-guide/sync-fingerprint-scan.md+++ b/docs/troubleshooting-guide/sync-fingerprint-scan.md@@ -99,7 +99,7 @@ LIMIT 1000A failed scan is caused by a failed scan query---you can look at the logs to debug the query similar to other queries you'd run directly against your database.-Note that when you [change a search box filter to a dropdown filter](../data-modeling/metadata-editing.md#changing-a-search-box-filter-to-a-dropdown-filter) from the Table Metadata, you'll trigger a scan query for that field. If you have a dropdown filter that isn't picking up all the values in a field, remember that Metabase only samples the first 1,000 unique values per field, and stores a maximum of 100 kilobytes of text. If you've got more than 1,000 unique values in a column, or a lot of text-heavy data (like long URLs or survey responses), you can:+Note that when you [change a search box filter to a dropdown filter](../data-modeling/metadata/metadata-editing.md#changing-a-search-box-filter-to-a-dropdown-filter) from the Table Metadata, you'll trigger a scan query for that field. If you have a dropdown filter that isn't picking up all the values in a field, remember that Metabase only samples the first 1,000 unique values per field, and stores a maximum of 100 kilobytes of text. If you've got more than 1,000 unique values in a column, or a lot of text-heavy data (like long URLs or survey responses), you can:- Use a search box filter for that field.- Clean up the data further in your [ETL or ELT](https://www.metabase.com/learn/grow-your-data-skills/data-landscape/etl-landscape) process.diff --git a/docs/util/data/nav.yml b/docs/util/data/nav.ymlindex fa18e8020d4..2d8c295aa94 100644--- a/docs/util/data/nav.yml+++ b/docs/util/data/nav.yml@@ -153,76 +153,6 @@ categories:- name: "AI privacy"url: "ai/privacy"- - name: "Data modeling"- url: "data-modeling/start"- pages:- - name: "Models"- url: "data-modeling/models"- - name: "Model persistence"- url: "data-modeling/model-persistence"- - name: "Metrics"- url: "data-modeling/metrics"- - name: "Table metadata settings"- url: "data-modeling/metadata-editing"- - name: "Data and semantic types"- url: "data-modeling/semantic-types"- - name: "Editable tables"- url: "data-modeling/editable-tables"- - name: "Formatting defaults"- url: "data-modeling/formatting"- - name: "Working with JSON"- url: "data-modeling/json-unfolding"- - name: "Segments"- url: "data-modeling/segments"- - name: "Actions"- pages:- - name: "Overview"- url: "actions/introduction"- - name: "Basic actions"- url: "actions/basic"- - name: "Custom actions"- url: "actions/custom"-- - name: "Data Studio"- url: "data-studio/overview"- pages:- - name: "Overview"- url: "data-studio/overview"- - name: "Library"- url: "data-studio/library"- - name: "Managing tables"- url: "data-studio/managing-tables"- - name: "Measures"- url: "data-studio/measures"- - name: "Segments"- url: "data-studio/segments"- - name: "Glossary"- url: "exploration-and-organization/data-model-reference#glossary"- - name: "Dependencies"- pages:- - name: "Dependency graph"- url: "data-studio/dependencies/graph"- - name: "Dependency diagnostics"- url: "monitor/dependency-diagnostics"- - name: "Replace data sources"- url: "data-studio/dependencies/replace-data-sources"- - name: "Transforms"- pages:- - name: "Overview"- url: "data-studio/transforms/transforms-overview"- - name: "Query transforms"- url: "data-studio/transforms/query-transforms"- - name: "Python transforms"- url: "data-studio/transforms/python-transforms"- - name: "Python runner"- url: "data-studio/transforms/python-runner"- - name: "Jobs and runs"- url: "data-studio/transforms/jobs-and-runs"- - name: "Transform inspector"- url: "data-studio/transforms/transform-inspector"- - name: "Add-ons"- url: "data-studio/transforms/addons"-- name: "Organization"url: "exploration-and-organization/start"pages:@@ -245,6 +175,73 @@ categories:- name: "Delete and restore"url: "exploration-and-organization/delete-and-restore"+ - name: "Data modeling"+ pages:+ - name: "Data studio"+ url: "data-modeling/data-studio"+ - name: "Transforms"+ pages:+ - name: "Overview"+ url: "data-modeling/transforms/transforms-overview"+ - name: "Query transforms"+ url: "data-modeling/transforms/query"+ - name: "Python transforms"+ url: "data-modeling/transforms/python"+ - name: "Python runner"+ url: "data-modeling/transforms/python-runner"+ - name: "Jobs and runs"+ url: "data-modeling/transforms/jobs-and-runs"+ - name: "Transform inspector"+ url: "data-modeling/transforms/inspector"+ - name: "Add-ons"+ url: "data-modeling/transforms/addons"+ - name: "Metadata"+ pages:+ - name: "Managing tables"+ url: "data-modeling/metadata/managing-tables"+ - name: "Metadata settings"+ url: "data-modeling/metadata/metadata-editing"+ - name: "Data and semantic types"+ url: "data-modeling/metadata/semantic-types"+ - name: "Formatting defaults"+ url: "data-modeling/metadata/formatting"+ - name: "Working with JSON"+ url: "data-modeling/metadata/json-unfolding"+ - name: "Semantic layer"+ pages:+ - name: "Library"+ url: "data-modeling/semantic-layer/library"+ - name: "Metrics"+ url: "data-modeling/semantic-layer/metrics"+ - name: "Measures"+ url: "data-modeling/semantic-layer/measures"+ - name: "Segments"+ url: "data-modeling/semantic-layer/segments"+ - name: "Tools"+ pages:+ - name: "Schema viewer"+ url: "data-modeling/tools/schema-viewer"+ - name: "Dependency graph"+ url: "data-modeling/tools/graph"+ - name: "Replace data sources"+ url: "data-modeling/tools/replace-data-sources"+ - name: "Editable tables"+ url: "data-modeling/editable-tables"+ - name: "Models"+ pages:+ - name: "Overview"+ url: "data-modeling/models/models"+ - name: "Model persistence"+ url: "data-modeling/models/model-persistence"+ - name: "Actions"+ pages:+ - name: "Overview"+ url: "data-modeling/models/actions/introduction"+ - name: "Basic actions"+ url: "data-modeling/models/actions/basic"+ - name: "Custom actions"+ url: "data-modeling/models/actions/custom"+- name: "Embedding"url: "embedding/start"pages: