diff --git a/_docs/master/api.html b/_docs/master/api.html
index 961f58ca75..5c8c7536d2 100644
--- a/_docs/master/api.html
+++ b/_docs/master/api.html
@@ -16909,7 +16909,7 @@
}
}, {
"in" : "query",
- "name" : "payload_type",
+ "name" : "pyaload_type",
"required" : false,
"schema" : {
"type" : "string",
diff --git a/_docs/master/dashboards/filters.md b/_docs/master/dashboards/filters.md
index 2376e30205..b59f923df1 100644
--- a/_docs/master/dashboards/filters.md
+++ b/_docs/master/dashboards/filters.md
@@ -212,7 +212,7 @@ You might want to require a filter value if:
To edit a filter's settings:
1. Click the **pencil** icon to enter dashboard editing mode.
-2. Click the filter you want to edit.
+2. Click the **gear** icon on the filter you want to edit.
From this filter editing view, you can wire up dashboard cards to the filter, or use the filter settings sidebar to:
@@ -226,14 +226,14 @@ From this filter editing view, you can wire up dashboard cards to the filter, or
### Rename filter
-1. In dashboard edit mode, click the fiter you want to edit.
+1. In dashboard edit mode, click your filter's **gear** icon.
2. Change the label text.
Renaming the filter only affects the filter's display; the label has no effect on which columns Metabase filters.
### Set filter input type
-1. In dashboard edit mode, click the fiter you want to edit.
+1. In dashboard edit mode, click your filter's **gear** icon.
2. From the filter settings sidebar, set **How should people filter on this column?**:
- [Dropdown list](#dropdown-list)
@@ -263,14 +263,14 @@ Useful for looking up partial matches (such as the ["contains" filter](#text-or-
### Set a default filter value
-1. In dashboard edit mode, click the filter you want to edit.
+1. In dashboard edit mode, click your filter's **gear** icon.
2. From the sidebar, choose a value from the **Default value** input field.
For example, you might want to set a default filter value like "Active", so that when people load your dashboard, they only see data for "Active" records (not "Inactive", "Cancelled", etc).
### Remove a filter
-1. In dashboard edit mode, click the fiter you want to edit.
+1. In dashboard edit mode, click your filter's **gear** icon.
2. From the sidebar, click **Remove**.
If you accidentally remove a filter, just click **Cancel** in the top-right to exit dashboard edit mode without saving your changes.
@@ -281,14 +281,14 @@ In dashboard edit mode, click on the grabber handle (six dots) on the left side
### Make a multi-select filter
-1. In dashboard edit mode, click the fiter you want to edit.
+1. In dashboard edit mode, click your filter's **gear** icon.
2. From the sidebar, find **People can pick** and select "Multiple values".
A multi-select filter with the widget type [Dropdown list](#dropdown-list) or [Search box](#search-box) will display a list of values with checkboxes.
### Change a filter's selectable values
-1. In dashboard edit mode, click the fiter you want to edit.
+1. In dashboard edit mode, click your filter's **gear** icon.
2. From the sidebar, find **How should users filter on this column?**.
3. Select "Dropdown list".\*
4. Click **Edit** (to the right of "Dropdown list") to specify where the values should come from:
diff --git a/_docs/master/developers-guide/driver-changelog.md b/_docs/master/developers-guide/driver-changelog.md
index 8900473622..1bfeb9d407 100644
--- a/_docs/master/developers-guide/driver-changelog.md
+++ b/_docs/master/developers-guide/driver-changelog.md
@@ -36,11 +36,13 @@ layout: new-docs
- Added the driver multi-method `driver/set-database-used!` for drivers to set a database on the connection with statements like `USE DATABASE`.
+- Added the driver features `:transforms/table`, `:transforms/view`, and `:transforms/matarialized-view` for drivers
+ that support transforms with table, view, and materialized view as target, respectively.
+
## Metabase 0.55.9
- Add multi-method `driver/do-with-resilient-connection` for executing functions in a context where closed connections may be automatically reopened
-
## Metabase 0.55.0
- Add the multi-method `->date` that allows the driver to control how to cast strings and temporal types to dates.
diff --git a/_docs/master/embedding/embedded-analytics-js.md b/_docs/master/embedding/embedded-analytics-js.md
deleted file mode 100644
index c05d20f09b..0000000000
--- a/_docs/master/embedding/embedded-analytics-js.md
+++ /dev/null
@@ -1,355 +0,0 @@
----
-version: master
-has_magic_breadcrumbs: true
-show_category_breadcrumb: true
-show_title_breadcrumb: true
-category: Embedding
-title: 'Embedded Analytics JS'
-source_url: 'https://github.com/metabase/metabase/blob/master/docs/embedding/embedded-analytics-js.md'
-layout: new-docs
-summary: 'Getting started with Embedded Analytics JS for embedding Metabase entities into external applications'
----
-
-# Embedded Analytics JS
-
-Embedded analytics JS allows you to embed Metabase entities like questions, dashboards, or even the query builder into your own application using customizable components.
-
-Embedded Analytics JS is a JavaScript library built on top of Metabase's [Embedded Analytics React SDK](./sdk/introduction). But it does not require using React or setting up full SDK embedding.
-Unlike with [interactive embedding](./interactive-embedding), where you embed the entire Metabase app in an iframe, Embedded Analytics JS lets you choose from a set of predefined components like a single chart, a dashboard with optional drill-through, or query builder, and customize those components.
-
-Embedded Analytics JS leverages [JWT SSO](../people-and-groups/authenticating-with-jwt) to authenticate people and automatically apply permissions to show people the right data upon sign-in.
-
-Currently you can choose to embed:
-
-- A dashboard
-- A question (chart). You can embed both questions built with the query builder and questions built with SQL.
-- Full graphical [query builder](../questions/query-builder/editor) to enable people to build their own charts and explorations.
-
-## Quickstart
-
-### 1. Enable Embedded Analytics JS
-
-1. In Metabase, go to **Admin Settings > Embedding > Modular embedding**.
-2. Toggle on **Embedded Analytics JS**.
-3. Under **Cross-Origin Resource Sharing (CORS)**, add the URLs of the websites where you want to embed Metabase (such as `https://*.example.com`). For testing embeds, you can use `localhost` which is always included in CORS policy.
-
-### 2. Create a new embed
-
-1. In Metabase, click on **+ New** button in top right corner and select **Embed**. Note that this will only be visible to admins.
-2. Choose the type of entity to embed. Currently the available types are dashboard, question, and exploration (which will embed the Metabase query builder).
-3. Next, select the entity you want to embed.
-
-Once you selected what you want to embed, click Next to customize your embed.
-
-### 3. Customize your embed
-
-The exact customization options you see will depend on what type of entity you're embedding. You will see live preview of how the embed will look with your chosen options. See [Customizing embeds](#customizing-embeds) for more information on customization options.
-
-
-
-You'll also be be able to pick brand, text, and background color used for all your embeds. To configure other colors (e.g. secondary colors, query builder colors etc), as well as font, you' can specify a theme in your embed code snippet, see [Theming](#theming).
-
-All the customization options you select in this interactive flow will be reflected in the parameter values in the embed code, so you'll be able to adjust them later by editing the embed snippet.
-
-Once you're done customizing your embed, click "Next".
-
-### 4. Select authentication method
-
-You'll get a choice between "Existing Metabase session" and "Single sign-on (SSO)".
-
-- If you select **Existing Metabase session**, you'll be able to preview your embeds as the user you're currently logged into Metabase, and only in the same browser as your current session. Not all browsers are supported - we recommend using Google Chrome. To test out embedding in other contexts, you can use [API keys](#use-api-keys-to-test-embeds) instead. For production usage, use [SSO](#set-up-sso).
-
-- If you set up JWT in your Metabase instance, you'll be able to select **Single sign-on (SSO)**, see [Set up SSO](#set-up-sso).
-
-### 5. Add the embedding script into your app
-
-Metabase will generate a code snippet that you can copy and paste into your app, see [Embed code snippets](#embed-code-snippets) for an example. You can later modify this code snippet to specify additional appearance options or change the behavior of some components.
-
-Add the code snippet into your app, and refresh the page.
-
-## Embed code snippets
-
-The code snippets to embed Metabase entities using Embedded Analytics JS should have three parts:
-
-1. Loading the Embedded Analytics JS library from your Metabase instance.
-2. Global configuration settings to be used for all embeds, like the URL of your Metabase instance, appearance themes, etc. See [Configuring embeds](#configuring-embeds).
-3. Components for Metabase entities to be embedded, with their parameters. See [Components](#components).
-
-Here's an example of a script:
-
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-Note the `defer` attribute and the reference to your Metabase URL in the script that loads `embed.js` library.
-
-If you're embedding multiple entities on the same page, you only need to include the `
-```
-
-For the full list of theme settings, see [Appearance](../sdk/appearance).
-
-## Authentication
-
-### Use existing user session to test embeds
-
-> Existing sessions can only be used for testing embeds locally. To make your embeds production-ready, you will need to implement SSO.
-
-If you are signed into Metabase, you can leverage that existing session cookie to preview and test the embeds. This will only work in the same browser as you're using for your Metabase session.
-
-To use the add `useExistingUserSession: true` to `defineMetabaseConfig()` in your embed code, see [Configuring embeds](#configuring-embeds).
-
-```html
-
-```
-
-Note that this will not work in some browsers, or in incognito mode. We recommend using Chrome if you'd like to use existing Metabase sessions to test your embeds.
-
-### Use API keys to test embeds
-
-> API keys can only be used for testing embeds locally. To make your embeds production-ready or deploy them to another domain, you will need to implement SSO.
-
-To use an API key to test your embeds:
-
-1. Create an [API key](../../people-and-groups/api-keys)
-2. Add `apiKey: "YOUR_API_KEY"` to `defineMetabaseConfig()`:
-
-```html
-
-```
-
-Keep in mind that API keys should only be used for testing with trusted users. Anyone with access to the front-end can grab the API key and use it to make requests against the Metabase API. For this reason, we only allow using API keys on localhost.
-
-### Set up SSO
-
-SSO is required to embed in a domain other than localhost.
-
-### 1. In Metabase, configure [JWT SSO](../people-and-groups/authenticating-with-jwt).
-
-### 2. In your app's backend, add a new endpoint to handle authentication.
-
-You’ll need add a library to your backend to sign your JSON Web Tokens.
-
-For Node.js, we recommend jsonwebtoken:
-
-```sh
-npm install jsonwebtoken --save
-```
-
-Next, set up an endpoint on your backend (e.g., `/sso/metabase`) that uses your Metabase JWT shared secret to generate a JWT for the authenticated user. **This endpoint must return a JSON object with a `jwt` property containing the signed JWT.** For example: `{ "jwt": "your-signed-jwt" }`.
-
-This example code for Node.js sets up an endpoint using Express:
-
-```js
-import express from "express";
-import cors from "cors";
-import session from "express-session";
-import jwt from "jsonwebtoken";
-import fetch from "node-fetch";
-
-// Replace this with your Metabase URL
-const METABASE_INSTANCE_URL = "YOUR_METABASE_URL_HERE";
-// Replace this with the JWT signing secret you generated when enabling
-// JWT SSO in your Metabase.
-const METABASE_JWT_SHARED_SECRET = "YOUR_SECRET_HERE";
-
-const app = express();
-
-app.get("/sso/metabase", async (req, res) => {
- // Usually, you would grab the user from the current session
- // Here it's hardcoded for demonstration purposes
- // Example:
- // const { user } = req.session;
- const user = {
- email: "rene@example.com",
- firstName: "Rene",
- lastName: "Descartes",
- group: "Customer",
- };
-
- if (!user) {
- console.log("no user");
- res.status(401).json({
- status: "error",
- message: "not authenticated",
- });
-
- return;
- }
-
- const token = jwt.sign(
- {
- email: user.email,
- first_name: user.firstName,
- last_name: user.lastName,
- groups: [user.group],
- exp: Math.round(Date.now() / 1000) + 60 * 10, // 10 minutes expiration
- },
- METABASE_JWT_SHARED_SECRET,
- );
- // The user backend should return a JSON object with the JWT.
- res.status(200).json({ jwt: token });
-});
-```
-
-See more examples in the [Embedding SDK docs](./sdk/authentication#2-add-a-new-endpoint-to-your-backend-to-handle-authentication).
-
-### 3. Embeds will use SSO automatically by default
-
-Metabase will use JWT SSO by default if no other auth method is specified. Make sure you don't use `apiKey` or `useExistingUserSession` in your configuration to enable SSO use.
-
-## Components
-
-There are different components available that enable different experiences for the end-user.
-
-> While you can use some component parameters to show or hide part of the embedded component, these parameters are not a substitute for setting up to prevent unwanted access to data or collections. Use these options as a way to streamline the user experience. Users could obtain their token from the front-end and use it to query the Metabase API.
-
-### Dashboard
-
-```html
-
-
-```
-
-Renders a dashboard.
-
-**Required parameters:**
-
-- `dashboard-id` - This can be a regular ID or an entity ID. [Using Entity IDs](../installation-and-operation/serialization#entity-ids-work-with-embedding) in your embeds will ensure sure that the IDs are stable when exporting from one Metabase and importing to another Metabase.
-
-**Optional parameters:**
-
-- `with-title` (default is true) - show dashboard title in the embed
-- `with-downloads` (default is false) - show the button to download dashboard as PDF, and download results of questions
-- `drills` (default is true) - lets you drill-through the dashboard
-- `initial-parameters` - default value for dashboard filters, e.g. `{ 'productId': '42' }`.
-
- Make sure to use single quotes if you are surrounding your attribute value with double quotes:
-
- ```html
-
- ```
-
-- `hidden-parameters` - list of filter names to hide from the dashboard, e.g. `['productId;]`
-
- Make sure to use single quotes if you are surrounding your attribute value with double quotes:
-
- ```html
-
- ```
-
-### Question
-
-```html
-
-```
-
-Renders a question (chart).
-
-**Required parameters:**
-
-- `question-id` - This can be a regular ID or an entity ID. [Using Entity IDs](../installation-and-operation/serialization#entity-ids-work-with-embedding) in your embeds will ensure sure that the IDs are stable when exporting from one Metabase and importing to another Metabase.
-
- Use `question-id="new"` to embed the query builder exploration interface.
-
-**Optional parameters:**
-
-- `drills` (default is true) - lets you drill-through the question
-- `with-title` (default is true) - render the title or not
-- `with-downloads` (default is false) - render the downloads or not
-- `initial-sql-parameters` - default value for SQL parameters, only applicable to native SQL questions. e.g. `{ "productId": "42" }`
-- `is-save-enabled` (default is false)
-- `target-collection` - this is to enforce saving into a particular collection. Values: regular ID, entity ID, `"personal”`, `"root”`
diff --git a/_docs/master/embedding/images/embed-flow-options.png b/_docs/master/embedding/images/embed-flow-options.png
deleted file mode 100644
index fa4c6163d6..0000000000
Binary files a/_docs/master/embedding/images/embed-flow-options.png and /dev/null differ
diff --git a/_docs/master/embedding/interactive-embedding-quick-start-guide.md b/_docs/master/embedding/interactive-embedding-quick-start-guide.md
index d81accee7e..3c039213e0 100644
--- a/_docs/master/embedding/interactive-embedding-quick-start-guide.md
+++ b/_docs/master/embedding/interactive-embedding-quick-start-guide.md
@@ -176,9 +176,7 @@ You'll map this string in the `groups` key to a Metabase group, so that when the
In Metabase's admin section, go to **Settings** > **Authentication**. Scroll to the **JWT** card and click **Edit**.
-In the **Group schema** section, toggle on **Synchronize group memberships**. If the names of groups in the `groups` array match Metabase group names exactly (e.g. both are `"Customer Acme"`), then the groups will be mapped automatically.
-
-If the JWT group names and Metabase group names don't match, then for each group you want to sync, add a group mapping. When you click **New mapping**, enter "Customer-Acme", the string that you included in the `groups` array in your JWT payload. You can then associate that group name with the Metabase group "Customer Acme" that we created earlier.
+In the **Group schema** section, toggle on **Synchronize group memberships**. For each group you want to sync, add a group mapping. When you click **New mapping**, enter "Customer-Acme", the string that you included in the `groups` array in your JWT payload. You can then associate that group name with the Metabase group "Customer Acme" that we created earlier.
diff --git a/_docs/master/embedding/sdk/api/MetabaseCollectionItem.html b/_docs/master/embedding/sdk/api/MetabaseCollectionItem.html
index fc00fa36cc..d415994415 100644
--- a/_docs/master/embedding/sdk/api/MetabaseCollectionItem.html
+++ b/_docs/master/embedding/sdk/api/MetabaseCollectionItem.html
@@ -10,11 +10,11 @@
---
MetabaseCollectionItem | Embedded analytics SDK API{% include docs/embedded-analytics-sdk-metadata.html %}
The CollectionItem entity
-