Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

docs: data studio redesign - draft (#83392)

Alex Yarosh7efe272763c9
diff --git a/docs/ai/metabot.md b/docs/ai/metabot.md
index d76845354ca..85fbbadd888 100644
--- a/docs/ai/metabot.md
+++ b/docs/ai/metabot.md
@@ -47,7 +47,7 @@ Some tips:
- Whenever you want Metabot to do something completely different, you should reset the conversation, as Metabot might find that irrelevant historical context to be confusing.
- Once Metabot creates a question for you, you can follow up with more questions or take over yourself. You can drill through the chart or step into the editor to tweak the query (both in the query builder and the SQL editor).
- Metabot works best with English prompts. While it might understand other languages, you'll get the most reliable results by asking your questions in English.
-- Define domain-specific terms in the [glossary](../exploration-and-organization/data-model-reference.md#glossary) to help Metabot understand your organization's terminology.
+- Define domain-specific terms in the [glossary](../data-modeling/semantic-layer/glossary.md) to help Metabot understand your organization's terminology.
### Metabot response menu
diff --git a/docs/ai/settings.md b/docs/ai/settings.md
index 357672c472d..ff440ca2716 100644
--- a/docs/ai/settings.md
+++ b/docs/ai/settings.md
@@ -217,7 +217,7 @@ Metabase will try to set semantic types automatically, but you should confirm th
### Define domain-specific terms in the glossary
-Add your organization's terminology, acronyms, and business-specific terms to the [glossary](../exploration-and-organization/data-model-reference.md#glossary). When you submit a prompt, Metabot can look up terms in the glossary to better understand your request.
+Add your organization's terminology, acronyms, and business-specific terms to the [glossary](../data-modeling/semantic-layer/glossary.md). Metabot can look up terms in the glossary to better understand your request.
For example, if you define "MRR" as "Monthly Recurring Revenue" in your glossary, Metabot will know what you mean when you ask "What's our MRR for Q4?" This is especially helpful for industry-specific jargon, internal product names, or abbreviations unique to your organization.
diff --git a/docs/data-modeling/data-studio.md b/docs/data-modeling/data-studio.md
index efd08baab74..a6b5e1c2d5e 100644
--- a/docs/data-modeling/data-studio.md
+++ b/docs/data-modeling/data-studio.md
@@ -19,15 +19,29 @@ Data Studio provides tools to shape and track your data so everyone can trust th
## What's in Data Studio
-- **[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.
+The first time you open Data Studio, you'll land on the **Guide**: a quick tour of what you can do in Data Studio. You can come back to the Guide any time from the top of the left sidebar.
+
+### Data
+
+- **[Connected data](./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.
+- **[Data transformation](./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.
+
+### Library
+
+- **[Semantic layer](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.
+- **[Glossary](./semantic-layer/glossary.md)**: Define terms relevant to your business, both for people and agents trying to understand your data.
+
+### Tools
+
- **[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.
+
+### Remote sync and settings
+
+- **[Remote sync](../installation-and-operation/remote-sync.md)**\*: Click **Set up remote sync** to connect a Git repository and sync your Library and transforms.
+- **Settings**: Turn [transforms](./transforms/transforms-overview.md) on or off for your Metabase. Settings only appear once you've [enabled transforms](./transforms/transforms-overview.md#enable-transforms).
\* Available on [Pro and Enterprise plans](https://www.metabase.com/pricing).
diff --git a/docs/data-modeling/metadata/managing-tables.md b/docs/data-modeling/metadata/managing-tables.md
index 6b434e06756..d3d24018cd1 100644
--- a/docs/data-modeling/metadata/managing-tables.md
+++ b/docs/data-modeling/metadata/managing-tables.md
@@ -9,11 +9,11 @@ redirect_from:
# Managing tables
-_Data Studio > Tables_
+_Data Studio > Connected data_
![Data structure](../images/data-structure.png)
-You can manage table settings metadata to make it easier for people to work with your data in **Data Studio > Tables**.
+You can manage table settings and metadata to make it easier for people to work with your data in **Data Studio > Connected data**.
You can do things like:
@@ -26,45 +26,41 @@ You can do things like:
- Set data formatting settings
- Create measures and segments
-## Permissions for managing tables in Data Studio
-
-To access the Tables area of Data Studio, you need to be a member of the Admin group or the Data Analyst group (Data Analyst group is only available on Pro/Enterprise plans).
-
-People in the Data Analyst group will have table metadata and data structure access to _all_ tables in your Metabase, even if they have limited View Data permissions for those tables. If you only want to give someone access to table metadata for some - but not all - tables, use the table metadata permissions and access the Table Metadata through Admin > Table metadata instead of Data Studio.
-
## Browse tables
-_Data Studio > Tables_
+_Data Studio > Connected data_
-You can see all tables in all databases connected to your Metabase in **Data Studio > Tables**, together with their owner, visibility layer, row count, and published state. For now, Metabase only displays row counts for PostgreSQL tables.
+You can see all tables in all databases connected to your Metabase in **Data Studio > Connected data**, together with their owner, visibility layer, row count, and published state. For now, Metabase only displays row counts for PostgreSQL tables.
You can search for table names, but the search will only match beginnings of words in table names. So for example, if you search for "base", results will include names like "Baseball stats" and "All your base are belong to us", but the results won't include tables like "Metabase secrets".
-You 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 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. To find tables that nothing else in your Metabase uses, select **Table isn't referenced by anything**. On Pro and Enterprise plans, you can also select **Published tables only**.
-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.
+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 unpublish them, change their [sync settings](#sync-settings), or assign attributes (including visibility) to multiple tables at once.
## Publishing and unpublishing tables
-_Data Studio > Tables > Details_
+_Data Studio > Connected data > Details_
-![Publishing a table from Data structure](../images/data-structure-publish.png)
+![Publishing a table from Connected data](../images/data-structure-publish.png)
{% 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.
+Once you select a table in **Data Studio > Connected data**, you can click **Publish** on the table's **Details** tab to add the table 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](../semantic-layer/library.md#publishing-tables) in the [Library docs](../semantic-layer/library.md).
+See [Published tables](../semantic-layer/published-tables.md).
## Find and replace tables
-You can replace every occurrence of a table as a data source with another table. See [Replace data sources](../tools/replace-data-sources.md).
+{% include plans-blockquote.html feature="Replacing data sources" %}
+
+Admins can replace every occurrence of a table as a data source with another table. Select the table in **Data Studio > Connected data**, click the **three-dot** menu on the table's **Details** tab, and select **Find and replace**. See [Replace data sources](../tools/replace-data-sources.md).
## Sync settings
-_Data Studio > Tables > Details_
+_Data Studio > Connected data > Details_
-You can trigger manual re-sync of the table schema in **Data Studio > Tables** in the **Details** tab. Re-syncing can be useful if you have added or removed columns from the table, and you don't see those changes reflected in Metabase.
+You can trigger manual re-sync of the table schema in **Data Studio > Connected data** in the **Details** tab. Re-syncing can be useful if you have added or removed columns from the table, and you don't see those changes reflected in Metabase.
You 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.
@@ -72,9 +68,9 @@ See [syncs and scans](../../databases/sync-scan.md) for more information.
## Table attributes
-_Data Studio > Tables > Details_
+_Data Studio > Connected data > Details_
-You can configure table attributes in **Data Studio > Tables** in the **Details** tab.
+You can configure table attributes in **Data Studio > Connected data** in the **Details** tab.
### Owner
@@ -108,7 +104,7 @@ Metabase will automatically assign the source "Metabase transforms" to tables cr
## Table and field metadata
-_Data Studio > Tables > Fields_
+_Data Studio > Connected data > 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`.
@@ -122,6 +118,14 @@ Segments are saved filters on a table that people can use in the query builder.
Measures are saved aggregations on a table that people can use in the query builder. See [Measures](../semantic-layer/measures.md).
+## Permissions for managing tables
+
+You need to be a member of the Admin group or the Data Analyst group (Data Analyst group is only available on Pro/Enterprise plans) to be able to manage table attributes, publish tables, or create measures and segments.
+
+People in the Data Analyst group will have table metadata and data structure access to _all_ tables in your Metabase, even if they have limited View Data permissions for those tables.
+
+If you only want to give someone access to table metadata for some - but not all - tables, use the table metadata permissions and access the Table Metadata through Admin > Table metadata instead of Data Studio.
+
## Further reading
- [Table metadata editing](./metadata-editing.md)
diff --git a/docs/data-modeling/metadata/metadata-editing.md b/docs/data-modeling/metadata/metadata-editing.md
index a53614e03a3..6f30059ad4f 100644
--- a/docs/data-modeling/metadata/metadata-editing.md
+++ b/docs/data-modeling/metadata/metadata-editing.md
@@ -7,7 +7,7 @@ redirect_from:
# Table metadata editing
-> Prefer using [Data Studio > Tables](./managing-tables.md) for metadata editing. The page _Admin > Table Metadata_ will be removed in future versions of Metabase.
+> Prefer using [Data Studio > Connected data](./managing-tables.md) for metadata editing. The page _Admin > Table Metadata_ will be removed in future versions of Metabase.
_Admin > Table metadata_
diff --git a/docs/data-modeling/semantic-layer/glossary.md b/docs/data-modeling/semantic-layer/glossary.md
index fb7988b5250..186d296c943 100644
--- a/docs/data-modeling/semantic-layer/glossary.md
+++ b/docs/data-modeling/semantic-layer/glossary.md
@@ -5,7 +5,23 @@ summary: Define terms to help your team and Metabot understand your data.
# Glossary
-The glossary is a place where anyone can define terms relevant to your data.
+_Data Studio > Glossary_
+
+The glossary is a place to define terms relevant to your data. Example:
+
+```txt
+Credit note: An amount applied after the invoice total to reduce what is due. Excluded from ARR; recognized as a one-time revenue impact in accounting, and avoided where possible.
+```
+Everyone in your Metabase can read the glossary, but only admins and people in the [Data Analysts](../../people-and-groups/managing.md#data-analysts) group can add, edit, or delete terms.
+
+To see the glossary in Data Reference:
+
+1. If the left navigation sidebar is hidden, open it by clicking on the **three lines** icon in top left.
+2. In the left navigation sidebar, click **Databases**.
+3. Click "Learn about our data" above the list of databases. This will open [Data Reference](../../exploration-and-organization/data-model-reference.md).
+4. In Data Reference, click **Glossary** in the left sidebar.
+
+ ![Glossary in data reference](images/glossary-in-data-reference.png)
## Use the glossary to give Metabot context
@@ -15,31 +31,24 @@ The glossary is particularly useful for [Metabot](../../ai/metabot.md). When Met
## Manage the glossary
-You can manage the glossary in [Data Studio](../data-studio.md). You need to be an admin or in the Data Analyst group to access Data Studio.
+You can manage the glossary in [Data Studio](../data-studio.md). You need to be an admin or in the Data Analysts group to access Data Studio.
1. Click on the **grid** icon in the top right and select **Data Studio**.
2. In the left sidebar, click on **Glossary**.
-3. To add a new term, click **+ New term**. Add the term name and its definitions, then click the checkmark to save the term to the glossary.
+3. To add a new term, click **+ New term**. Add the term name and its definitions, then click the checkmark to save the term to the glossary.
- To remove a glossary term, hover over it and click on the **X** icon.
-
- To edit a glossary term or definition, click on the term or definition.
+ To remove a glossary term, hover over it, click the **trash** icon, and confirm.
+ To edit a glossary term or definition, click on the term or definition.
Metabot will start using glossary terms automatically.
-## Glossary outside Data Studio
-
-In addition to Data Studio, everyone in your Metabase can browse and add terms to the glossary if they have access to [Data Reference](../../exploration-and-organization/data-model-reference.md).
-
-To see the glossary in Data Reference:
-1. If the left navigation sidebar is hidden, open it by clicking on the **three lines** icon in top left.
-2. In the left navigation sidebar, click **Databases**.
-3. Click "Learn about our data" above the list of databases. This will open [Data Reference](../../exploration-and-organization/data-model-reference.md).
-4. In Data Reference, click **Glossary** in the left sidebar.
+## Glossary terms sync with the Library
- ![Glossary in data reference](images/glossary-in-data-reference.png)
+If you [sync the Library to Git](./library.md#versioning-the-library) with [Remote sync](../../installation-and-operation/remote-sync.md), Metabase syncs your glossary terms along with the rest of the Library.
+## Glossary outside Data Studio
+In addition to Data Studio, everyone in your Metabase can browse the glossary if they have access to [Data Reference](../../exploration-and-organization/data-model-reference.md). Admins and Data Analysts can also edit the glossary from Data Reference.
diff --git a/docs/data-modeling/semantic-layer/library.md b/docs/data-modeling/semantic-layer/library.md
index 866ea1566dd..c2ef84a9461 100644
--- a/docs/data-modeling/semantic-layer/library.md
+++ b/docs/data-modeling/semantic-layer/library.md
@@ -1,13 +1,13 @@
---
title: Library
-summary: Create a source of truth for analytics with curated tables, metrics, and SQL snippets that your team can trust.
+summary: Create a source of truth for analytics with curated tables, metrics, SQL snippets, and glossary terms that your team can trust.
redirect_from:
- /docs/latest/data-studio/library
---
# Library
-{% include plans-blockquote.html feature="Library" %}
+{% include plans-blockquote.html feature="Some features of the library" is_plural=true%}
"I have always imagined that Paradise will be a kind of library."
@@ -15,103 +15,99 @@ redirect_from:
![Library in the main navigation sidebar](./images/library-in-sidebar.png)
-The Library 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.
+The Library helps you create a source of truth for analytics by providing a centrally managed set of curated content and shared definitions. Use the Library to separate authoritative, reusable components from ad-hoc analyses and definitions.
## How the Library works
![The Library in Data Studio](./images/library-in-data-studio.png)
-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.
+The Library has two parts, both of which you manage in [Data Studio](../data-studio.md):
-## Adding items to the Library
-
-To add items to the Library:
+- **[Semantic layer](#semantic-layer)**: Curated tables, metrics, and SQL snippets.
+- **[Glossary](#glossary)**: Definitions of your business terms.
-1. Click the grid icon in the upper right.
-2. Select **Data Studio**.
-3. In the **Library** tab, click **+ New**.
+Once you [create the Library](#create-the-library):
-You can:
+- A **Library** section appears in the navigation sidebar of the main app, listing the tables and metrics in your semantic layer.
+- The data picker in the query builder defaults to showing tables and metrics from the Library to encourage people to use your vetted content.
+- If you turn on Metabot's [Verified or curated content](../../ai/settings.md#verified-content) setting, Metabot will only use content that's verified, in an official collection, or published to the Library.
+- You can [sync the Library to Git](#versioning-the-library) to version your semantic layer and glossary.
-- [Publish a table](#publishing-tables)
-- [Create a metric](#metrics)
-- [Create a SQL snippet or folder](#sql-snippets)
-- [Create a subcollection or snippet folder](#library-organization)
+### Semantic layer
-## Library organization
+_Data Studio > Semantic layer_
-![Library organization](./images/library-org.png)
+The semantic layer is a collection of curated tables (together with their [segments](segments.md) and [measures](measures.md)), [metrics](metrics.md), and [SQL snippets](../../questions/native-editor/snippets.md) that people and AI can use to build authoritative questions and dashboards.
-Library is essentially a special collection. It has three special "subcollections":
+The semantic layer is what people see in the **Library** section of the main app's navigation sidebar, and in the data picker.
-- **Data** - for [published tables](#publishing-tables);
-- **Metrics** - for [official metrics](#metrics);
-- **Snippets** - for all the [SQL snippets](#sql-snippets) on your instance.
+### Glossary
-These special collections are predefined. You can't rename or archive them, (but you can use [ permissions](#library-permissions) to control who sees these collections).
+_Data Studio > Glossary_
-Each of these special collections can have further subcollections. For example, if your Metabase has a lot of published tables, you might want to organize the **Library > Data** collection into "Sales", "Marketing", "Product" subcollections.
+The [Glossary](glossary.md) is a place for your team to define revelant business terms.
-People will see the Library structure in the navigation sidebar and in the data picker in the query builder:
+## Create the Library
-![Library organization](./images/library-data-picker.png)
+Before you can add items to the semantic layer, you'll need to create the Library:
-To create a new subcollection for one of the Library's special collections:
+1. Click the **grid** icon in the upper right and select **Data Studio**.
+2. In the left sidebar, click **Semantic layer**.
+3. Click **Create my Library**.
-1. Go to **Data Studio > Library**.
-2. Click **+ New** in the top right corner.
-3. Under **Collection it's saved in**, select the parent collection.
-4. Add the name and description for the collection and click **Create**.
+Metabase will create the Library with its **Data** and **Metrics** collections. By default, everyone can view the Library, and people in the Data Analysts group can curate it. See [Library permissions](#library-permissions).
-## Publishing tables
+If you try to [publish a table](published-tables.md) from **Connected data** before you've created the Library, Metabase will ask you to create the Library first.
-![Starting data](./images/starting-data.png)
+## Adding items to the Library
-Tables published to the Library appear first in the Data section when people choose data sources, nudging them toward trusted data.
+To add items to the Library:
-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).
+1. Click the **grid** icon in the upper right and select **Data Studio**.
+2. In the left sidebar, click **Semantic layer**.
+3. Click **+ New**.
-Tables published to the Library remain available via the data browser as well.
+The **+ New** menu has options to:
-To publish a table to the library:
+- **Published table**: [Publish a table](published-tables.md#publish-a-table-from-the-semantic-layer) to the Library.
+- **Metric**: [Create a metric](#metrics) in the Library.
+- **Snippet**: [Create a SQL snippet](#sql-snippets).
+- **Collection**: [Create a subcollection or snippet folder](#library-organization).
-1. Go to **Data Studio > Library**
+To manage the glossary, see [Glossary](glossary.md).
-### Managing tables
+## Library organization
-Once a table is published, you can view and manage its metadata, and more.
+![Library organization](./images/library-org.png)
-- Overview
-- Fields
-- [Segments](segments.md)
-- [Measures](measures.md)
-- [Dependencies](../tools/graph.md)
+The semantic layer lives in a special collection called Library, which has three root sections:
-To query a table from the Library in Data Studio:
+- **Data**: For [published tables](published-tables.md).
+- **Metrics**: For [official metrics](#metrics).
+- **SQL snippets**: For all the [SQL snippets](#sql-snippets) on your instance.
-1. Click the table.
-2. Click the three-dot menu.
-3. Select **View**.
+These root sections are predefined. You can't rename or archive them, but you can use [permissions](#library-permissions) to control who sees them.
-### Published tables can't have dependencies outside of the Library
+Each of these sections can have subcollections. For example, if your Metabase has a lot of published tables, you might want to organize the **Library > Data** collection into "Sales", "Marketing", and "Product" subcollections.
-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.
+![Library organization](./images/library-data-picker.png)
-### Unpublishing tables
+To create a subcollection in one of the Library's sections:
-![Unpublishing a table from the Library](./images/library-unpublish.png)
+1. Go to **Data Studio > Semantic layer**.
+2. Click **+ New** and select **Collection**.
+3. Under **Collection it's saved in**, select the parent collection.
+4. Add the name and description for the collection and click **Create**.
-To unpublish a table from the Library:
+## Publishing tables
-1. Visit the table in Data Studio in the Library tab.
-2. Click on the three-dot menu next to the table's name.
-3. Click **Unpublish**.
+![Starting data](./images/starting-data.png)
-If other tables depend on the table you want to unpublish, Metabase will unpublish those tables as well. You'll get a confirmation message explaining which tables Metabase would unpublish.
+Tables published to the Library appear first in the Data section when people choose data sources, nudging them toward trusted data.
-Unpublishing a table just removes the table from the Library. That table will still be available via the data browser and data pickers.
+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).
-> **Archiving a subcollection unpublishes its tables.** If you archive a Data subcollection, Metabase will automatically unpublish all tables inside it, including tables in any nested subcollections.
+See [Published tables](published-tables.md).
## Metrics
@@ -121,7 +117,7 @@ Metrics can live in any collection, but metrics in the Library will be prioritiz
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](./metrics.md#create-a-metric) for more on building metrics.
+To create a new Library metric, go to **Data Studio > Semantic layer** and select **+ New > Metric**. See [creating metrics](./metrics.md#create-a-metric) for more on building metrics.
## SQL snippets
@@ -129,11 +125,11 @@ To create a new Library metric, go to **Data Studio > Library** and select **+ N
## 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. When you sync the Library, Metabase also syncs your SQL snippets and [glossary](glossary.md) terms.
## 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).
+The semantic layer lives in a special collection called Library. Metabase uses the standard [collection permissions](../../permissions/collections.md) to determine who can view and edit items in the Library collection, 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). Collection permissions don't apply to the [glossary](glossary.md#manage-the-glossary).
![Library collection permissions](./images/library-permissions.png)
@@ -141,7 +137,7 @@ To configure permissions for the library:
1. Go to **Admin > Permissions**.
2. Switch to **Collections** in the left sidebar.
-3. Select **Curate**, **View**, or **No access** permissions for the Library and its subcollecitons.
+3. Select **Curate**, **View**, or **No access** permissions for the Library and its subcollections.
See below for the access that each permission level provides for each part of the Library.
@@ -161,29 +157,29 @@ Controls whether a group can view the Library and its items.
Groups 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 collection permissions to **Library > Data** to block access to tables - use [data permissions](../../permissions/data.md) instead.
### Permissions to edit the Library
Admins and people in the Data Analyst group always have Curate access to the Library.
-There are some caveats through, depending on which part of the Library you're working with.
+There are some caveats though, depending on which part of the Library you're working with.
- **Data** (published tables):
- 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.
+ - 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 Data Studio.
- **Metrics**:
- - [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.
+ - [Admins and data analysts](../../people-and-groups/managing.md) can always manage metrics in the Library and its subcollections;
+ - 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 subcollections do _not_ give access to Data Studio.
- **Snippets**
- 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.
+The root sections (Data, Metrics, SQL snippets) have fixed properties and can't be renamed or deleted. Subcollections you create follow the normal collection permission rules.
## Permissions to use Library content
@@ -191,7 +187,7 @@ People who have View or Curate collection permissions to the **Library** subcoll
- **Data** (published tables):
- - 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).
+ - People who have View or Curate collection permissions to **Library > Data** or its subcollections will be able to see published tables 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.
@@ -201,7 +197,7 @@ People who have View or Curate collection permissions to the **Library** subcoll
- **Metrics**:
- - Only people who have View or Curate collection permissions to **Library > Metrics** or its subcollections will be able use the metrics from the appropriate collections. Removing collection access to a **Library > Metrics** subcollection also blocks any usage of metric there.
+ - Only people who have View or Curate collection permissions to **Library > Metrics** or its subcollections will be able to use the metrics from the appropriate collections. Removing collection access to a **Library > Metrics** subcollection also blocks any usage of metric there.
- **Snippets**:
@@ -209,6 +205,8 @@ People who have View or Curate collection permissions to the **Library** subcoll
## Further reading
+- [Published tables](./published-tables.md)
+- [Glossary](./glossary.md)
- [Dependency graph](../tools/graph.md)
- [Remote sync](../../installation-and-operation/remote-sync.md)
- [Metrics](./metrics.md)
diff --git a/docs/data-modeling/semantic-layer/measures.md b/docs/data-modeling/semantic-layer/measures.md
index 79a3cce1dfa..3821e373080 100644
--- a/docs/data-modeling/semantic-layer/measures.md
+++ b/docs/data-modeling/semantic-layer/measures.md
@@ -13,6 +13,8 @@ People will see measures as options in the Summarize block of the [query builder
![Measure in the query builder](./images/measure.png)
+You can define measures on any table. Measures on [published tables](published-tables.md) are part of your [semantic layer](library.md#semantic-layer).
+
## 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.
@@ -20,7 +22,7 @@ People will see measures as options in the Summarize block of the [query builder
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.
+2. In Data Studio, go to **Connected data** in the left sidebar, and select the table to define a measure on.
3. In the right sidebar for the table, select **Measures**.
![Find measures](./images/find-measures.png)
@@ -56,7 +58,7 @@ Measures are only available to questions that directly query the measure's table
Deleting a measure won't break questions using it. The questions that use the deleted measure will "revert" to using the measure's (now unnamed) aggregation formula.
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**, and select the measure's table.
+2. In Data Studio, go to **Connected data**, and select the measure's table.
3. In the right sidebar for the table, select **Measures**.
4. Choose the measure you want to delete.
5. On the measure's page, click on the **three dots** icon next to the measure's name and select **Remove measure**.
@@ -67,7 +69,7 @@ You can explore measures along dimensions and compare several measures in the [M
![Explore a measure](./images/explore-measure.png)
-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.
+To see all measures on a table, select the table in [Data Studio > Connected data](../metadata/managing-tables.md) and switch to the **Measures** tab.
## Permissions for measures
diff --git a/docs/data-modeling/semantic-layer/published-tables.md b/docs/data-modeling/semantic-layer/published-tables.md
new file mode 100644
index 00000000000..fe1d1e09139
--- /dev/null
+++ b/docs/data-modeling/semantic-layer/published-tables.md
@@ -0,0 +1,98 @@
+---
+title: Published tables
+summary: "Publish tables to the Library to give people (and AI agents) a curated, authoritative set of tables to start their questions from."
+---
+
+# Published tables
+
+_Data Studio > Semantic layer_
+
+{% include plans-blockquote.html feature="Publishing tables to the Library" %}
+
+Published tables are the tables you add to your [semantic layer](library.md#semantic-layer). They live in the **Data** collection.
+
+Published tables also show up in the **Library** section of the main app's navigation sidebar. When people pick data for a new question, Metabase shows published tables first. You can also tell [Metabot](../../ai/metabot.md) to only use [curated content](../../ai/settings.md#verified-content) like published tables, and you can [sync published tables to Git](library.md#versioning-the-library), along with their metadata, segments, and measures.
+
+We use the word "publish" because the tables in your Library should 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).
+
+## Publish a table from the semantic layer
+
+1. Click the **grid** icon in the top right and select **Data Studio**.
+2. In the left sidebar, click **Semantic layer**.
+3. Click **+ New** and select **Published table**.
+4. Pick the table you want to publish and click **Publish**. Tables that are already published are grayed out.
+5. In the publishing modal, under **Publish to**, pick **Data** or one of its subcollections. By default, Metabase publishes tables to **Library > Data**.
+6. Click **Publish this table**.
+
+If you haven't created the Library yet, see [Create the Library](library.md#create-the-library).
+
+## Publish tables from Connected data
+
+To publish a single table:
+
+1. In Data Studio, click **Connected data** in the left sidebar.
+2. Select the table.
+3. On the table's **Details** tab, click **Publish**.
+
+To publish several tables at once, check the boxes next to the tables (or whole schemas or databases) in **Connected data**, then click **Publish** in the right sidebar.
+
+If you haven't created the Library yet, Metabase will ask you to create it first. See [Managing tables](../metadata/managing-tables.md) for more on Connected data.
+
+## Organize published tables
+
+You can only put published tables in the **Data** section of the semantic layer. To keep a lot of published tables organized, you can create subcollections in **Data**, like "Sales", "Marketing", and "Product". Go to **Data Studio > Semantic layer**, click **+ New**, and select **Collection**. See [Library organization](library.md#library-organization).
+
+Once you've created subcollections, you can publish tables to them, or [move published tables](#view-and-edit-published-tables) into them.
+
+## 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. The publishing modal lists the tables that Metabase will publish along with your table.
+
+## View and edit published tables
+
+To see a published table in Data Studio, go to **Data Studio > Semantic layer**, expand **Data** (and any subcollections), and click the table. The table's page has tabs for:
+
+- **Overview**: The table's description and attributes like its owner and source. On Metabase Cloud, or if your plan includes [usage analytics](../../usage-and-performance-tools/usage-analytics.md), the overview also shows who published the table and when.
+- **Fields**: The table's [field metadata](../metadata/metadata-editing.md).
+- **Segments**: [Segments](segments.md) defined on the table.
+- **Measures**: [Measures](measures.md) defined on the table.
+- **Dependencies**: The table's [dependency graph](../tools/graph.md).
+
+To query a published table, click the **three-dot** menu next to the table's name and select **View**. Metabase will open the table in the query builder in a new tab.
+
+To move a published table to a different subcollection in **Data**, click the **three-dot** menu next to the table's name and select **Move**.
+
+## Unpublish tables
+
+![Unpublishing a table from the Library](./images/library-unpublish.png)
+
+To unpublish a table:
+
+1. Go to **Data Studio > Semantic layer** and find the table under **Data**.
+2. Click the **three-dot** menu next to the table's name.
+3. Click **Unpublish**.
+
+You can also unpublish tables:
+
+- **In bulk from the semantic layer**: Check the boxes next to the tables, then click **Unpublish**.
+- **From Connected data**: Select the table and click **Unpublish** on its **Details** tab, or check the boxes next to several tables and click **Unpublish** in the right sidebar.
+
+If other tables depend on the table you want to unpublish, Metabase will unpublish those tables as well. You'll get a confirmation message explaining which tables Metabase would unpublish.
+
+Unpublishing a table just removes the table from the Library. That table will still be available via the data browser and data pickers.
+
+**Archiving a subcollection unpublishes its tables.** If you archive a Data subcollection, Metabase will automatically unpublish all tables inside it, including tables in any nested subcollections.
+
+## Published table permissions
+
+- **Who can publish**: Only [admins and data analysts](../../people-and-groups/managing.md) can publish and unpublish tables.
+- **Collection permissions control what people see, _not_ what data they can query**: Collection permissions on **Library > Data** and its subcollections only control where people see published tables (in the navigation sidebar, the data picker, and search). To restrict access to the data in a table, use [data permissions](../../permissions/data.md).
+- **Publishing a table can grant query access**: Like with models, publishing a table gives query access to that table to groups with view access to the database, even if those groups have **Create queries** set to **No** for that table.
+
+See [Permissions to use Library content](library.md#permissions-to-use-library-content).
+
+## Further reading
+
+- [Library](./library.md)
+- [Managing tables](../metadata/managing-tables.md)
+- [Library permissions](./library.md#library-permissions)
diff --git a/docs/data-modeling/semantic-layer/segments.md b/docs/data-modeling/semantic-layer/segments.md
index 44772544592..4234ac38755 100644
--- a/docs/data-modeling/semantic-layer/segments.md
+++ b/docs/data-modeling/semantic-layer/segments.md
@@ -8,15 +8,19 @@ redirect_from:
# Segments
+_Data Studio > Connected data > Segments_
+
Segments 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).
![Segment in the query builder](./images/segment.png)
+You can define segments on any table. Segments on [published tables](published-tables.md) are part of your [semantic layer](library.md#semantic-layer).
+
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](../metadata/managing-tables.md) and switch to the **Segments** tab.
+To see all segments on a table, select the table in **Data Studio > Connected data** and switch to the **Segments** tab.
## Create segments
@@ -25,7 +29,7 @@ To see all segments on a table, select the table in [Managing tables](../metadat
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.
+2. In Data Studio, go to **Connected data** in the left sidebar, and select the table to define a segment on.
3. In the right sidebar for the table, select **Segments**.
4. Click on **+ New Segment**. You'll see an abridged version of Metabase's query builder.
5. Add the filters describing the segment (e.g. `Active = true`) and name the segment.
@@ -51,7 +55,7 @@ Segments will only appear in questions that use the segment's table as the prima
Deleting a segment will not break questions using it. The questions that use the segment will keep using the same filters as before.
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**, and select the segment's table.
+2. In Data Studio, go to **Connected data**, and select the segment's table.
3. In the right sidebar for the table, switch to **Segments** tab
4. Choose the segment you want to delete.
5. On the segment's page, click on the **three dots** icon next to the segment's name and select **Remove segment**.
diff --git a/docs/data-modeling/tools/graph.md b/docs/data-modeling/tools/graph.md
index 933d958c8ce..8f46668c191 100644
--- a/docs/data-modeling/tools/graph.md
+++ b/docs/data-modeling/tools/graph.md
@@ -8,6 +8,8 @@ redirect_from:
# Dependency graph
+_Data Studio > Dependency graph_
+
{% include plans-blockquote.html feature="Dependency graph" %}
![Dependency graph](../images/dependency-graph.png)
@@ -41,7 +43,7 @@ To open the full dependency graph:
This opens a canvas view where you can search for and visualize the dependencies of any item across your entire Metabase instance.
-You can also view the dependency graph from any item in Data Studio by switching to the Dependencies tab.
+You can also view an item's dependencies from its page in Data Studio. Published tables, metrics, snippets, segments, measures, and transforms have a **Dependencies** tab. For tables in **Connected data**, click the **Dependency graph** button on the table's **Details** tab.
## What the dependency graph shows
diff --git a/docs/data-modeling/tools/replace-data-sources.md b/docs/data-modeling/tools/replace-data-sources.md
index aa198f9d6a5..8eb303db8e0 100644
--- a/docs/data-modeling/tools/replace-data-sources.md
+++ b/docs/data-modeling/tools/replace-data-sources.md
@@ -7,6 +7,8 @@ redirect_from:
# Replace data sources
+_Data Studio > Dependency graph_
+
{% include plans-blockquote.html feature="Replacing data sources" %}
Admins can swap out a table, model, or question and replace it with a different one across your entire Metabase.
@@ -81,6 +83,9 @@ To find and replace all entities that depend on a data source:
2. In Data Studio, click **Dependency graph** in the sidebar and search for the table, model, or question you want to replace.
3. Click the card for the data source and in the info panel on the right, click the **Find and replace** icon.
![Find and replace](../images/find-and-replace.png)
+
+ To replace a table, you can also go to **Data Studio > Connected data**, select the table, click the **three-dot** menu on the table's **Details** tab, and select **Find and replace**.
+
4. In the left sidebar, select replacement data source.
5. If Metabase can't go ahead with replacement, you'll see error messages next to data sources, and [compatibility requirements](#compatibility-requirements) errors in the "Column comparison table".
diff --git a/docs/util/data/nav.yml b/docs/util/data/nav.yml
index c38fa4915fc..4f055b83741 100644
--- a/docs/util/data/nav.yml
+++ b/docs/util/data/nav.yml
@@ -213,6 +213,8 @@ categories:
pages:
- name: "Library"
url: "data-modeling/semantic-layer/library"
+ - name: "Published tables"
+ url: "data-modeling/semantic-layer/published-tables"
- name: "Metrics"
url: "data-modeling/semantic-layer/metrics"
- name: "Measures"