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 actions (#85578)

Jeff Bruemmer2ff5e131ccf6
diff --git a/docs/dashboards/actions.md b/docs/dashboards/actions.md
index e646fce69bc..fc931f56c69 100644
--- a/docs/dashboards/actions.md
+++ b/docs/dashboards/actions.md
@@ -10,7 +10,7 @@ You can add buttons to dashboards to perform [actions](../data-modeling/models/a
## 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](../data-modeling/models/actions/introduction.md).
+To add an action button to a dashboard, an admin first needs to create an action on a model. See [Model actions](../data-modeling/models/actions/introduction.md).
## Add an action button to a dashboard
diff --git a/docs/data-modeling/data-actions.md b/docs/data-modeling/data-actions.md
new file mode 100644
index 00000000000..947126b931c
--- /dev/null
+++ b/docs/data-modeling/data-actions.md
@@ -0,0 +1,110 @@
+---
+title: Data actions
+summary: Data actions insert, update, or delete rows in your database. You can run them in Data Studio or share them as public forms.
+---
+
+# Data actions
+
+_Data Studio > Data actions_
+
+Data actions let people change the data in your database. For example, a data action can approve a request, or mark an order as refunded.
+
+Each data action does one job: it inserts, updates, or deletes rows. An admin sets up the action once, and people can only make the changes that the action allows.
+
+You can run data actions in two ways:
+
+- **In Data Studio**, to test an action or make a one-off change. See [Run a data action](#run-a-data-action).
+- **As a public form**, to collect data from people outside Metabase, like event sign-ups or feedback. See [Share a data action as a public form](#share-a-data-action-as-a-public-form).
+
+Unlike [model actions](./models/actions/introduction.md), data actions don't belong to a [model](./models/models.md). You don't need to create a model first, and data actions stay put when someone moves a model to the trash. But you can't add data actions to [dashboard buttons](../dashboards/actions.md). For a dashboard button, use a model action.
+
+If you [sync the Library](./semantic-layer/library.md#versioning-the-library) with [Remote Sync](../installation-and-operation/remote-sync.md), your data actions sync with it.
+
+## Create a data action
+
+Only admins can create data actions. Data actions only work on PostgreSQL and MySQL databases. The **New** button only shows up if an admin has [turned on data actions](./models/actions/introduction.md#enabling-actions-for-a-database) for at least one of these databases.
+
+You can create a data action in two ways:
+
+- **[Write SQL](#create-a-data-action-with-sql)** for changes that need your own logic, like updating every order for a customer.
+- **[Pick a table](#create-a-data-action-that-changes-one-row)** for an action that adds, updates, or deletes one row.
+
+### Create a data action with SQL
+
+1. Go to [Data Studio](./data-studio.md#get-to-data-studio) > **Data actions**.
+2. Click **New** > **SQL query**.
+3. Write your SQL. Each {% raw %}{{ variable }}{% endraw %} in the SQL becomes a field on the action's form. For examples, see [Example custom actions](./models/actions/custom.md#example-custom-actions).
+4. Click **Save**, enter a **Name**, pick a **Folder**, and click **Save** again.
+
+### Create a data action that changes one row
+
+Pick a table and an operation, and Metabase builds the form from the table's columns. The table must have exactly one primary key.
+
+1. Go to [Data Studio](./data-studio.md#get-to-data-studio) > **Data actions**.
+2. Click **New** > **Table**, and pick a table. The picker only lists tables in databases with data actions turned on.
+3. Under **Operation**, pick **Insert** to add a row, **Update** to change a row, or **Delete** to remove a row. Update and Delete find the row by its primary key, and Update keeps the current value of any field you leave empty.
+4. Click **Save**, enter a **Name** (Metabase suggests one, like "Insert Orders"), pick a **Folder**, and click **Save** again.
+
+![A table action that inserts a row into the Products table](./images/add-product-data-action.png)
+
+## Run a data action
+
+1. Go to **Data Studio** > **Data actions** and click the action.
+2. Go to the **Run** tab and click the **Run** button.
+3. Fill out the form and submit it. Metabase makes the change in your database.
+
+If the **Run** button is grayed out, data actions are turned off for the action's database, or you don't have access to that database.
+
+![The form for the Add product action](./images/data-action-form.png)
+
+## Edit a data action
+
+Go to **Data Studio** > **Data actions** and click the action.
+
+- **To change what the action does**, go to the **Definition** tab. For a SQL action, click **Edit definition**. For a table action, click **Change table** or pick another **Operation**.
+- **To change the action's form**, go to the **Fields** tab and click a field to change its type, input, default value, and more. A SQL action has one field for each {% raw %}{{ variable }}{% endraw %} in the SQL. A table action has one field for each column that it writes (for Delete, only the primary key), and you can only show or hide these fields. If you turn off **Show field**, the action uses the field's default value.
+
+## Share a data action as a public form
+
+A public form lets anyone with the link run the action without signing in to Metabase.
+
+1. Open the action and go to the **Settings** tab.
+2. Turn on **Make public**, and copy the **Public link**.
+3. Optional: Enter a **Success message** that people see after they submit the form.
+
+Only admins can make an action public, and [public sharing](../embedding/public-links.md) must be on.
+
+Public forms don't check [row and column security](../permissions/row-and-column-security.md#people-with-row-and-column-security-cant-run-actions). Anyone with the link can run the action, even on a database where row and column security applies to some groups.
+
+## Check what uses a data action before you change it
+
+{% include plans-blockquote.html feature="Dependency graph" %}
+
+Open the action and go to the **Dependencies** tab to see the action's [dependency graph](./tools/graph.md).
+
+## Use folders to control who can run data actions
+
+Anyone who can view a folder can run the actions in it. So use folders to give each group the actions it needs. For example, put the actions that your support team uses in a "Support" folder, and give only the Support group view access to that folder.
+
+- **Create a folder**: Click **New** > **Collection**.
+- **Change who can run a folder's actions**: Click the **three-dot** menu next to the folder, and select **Change permissions**. For actions that aren't in a folder, click the **three-dot** menu next to the **New** button, and select **Change permissions**.
+- **Move an action to another folder**: Open the action, click the **three-dot** menu next to its name, and select **Move**.
+
+## Archive and unarchive data actions
+
+- **Archive an action**: Open the action, click the **three-dot** menu next to its name, and select **Archive**. Public forms that use an archived action stop working until you unarchive the action.
+- **Archive a folder**: Click the **three-dot** menu next to the folder, and select **Archive**. Metabase archives the folder's actions with it.
+- **Unarchive an action or folder**: Click the **three-dot** menu next to the **New** button, select **View archived actions**, and click the **Unarchive action** or **Unarchive folder** icon. Unarchiving a folder brings back the actions that Metabase archived with it, but not actions that someone archived on their own.
+
+## Data action permissions
+
+Anyone who can view a data action's folder can run the action. To run an action in Data Studio, people also need [access to Data Studio](./data-studio.md#permissions-for-data-studio). People without access to Data Studio can run an action through a [public form](#share-a-data-action-as-a-public-form).
+
+Only admins can create, edit, move, archive, or unarchive data actions and their folders. You can't give other groups [Curate access](../permissions/collections.md#collection-permission-levels) to data actions folders.
+
+## Further reading
+
+- [Introduction to actions](./models/actions/introduction.md)
+- [Basic actions](./models/actions/basic.md)
+- [Custom actions](./models/actions/custom.md)
+- [Data Studio](./data-studio.md)
diff --git a/docs/data-modeling/data-studio.md b/docs/data-modeling/data-studio.md
index 4a4ddf18d65..7f59a689d42 100644
--- a/docs/data-modeling/data-studio.md
+++ b/docs/data-modeling/data-studio.md
@@ -31,6 +31,7 @@ The first time you open Data Studio, you'll land on the **Guide**: a quick tour
### Library
- **[Semantic layer](semantic-layer/library.md)**\*: A curated space for your organization's most trusted analytics content—tables, metrics, dashboards, and SQL snippets that your data team recommends.
+- **[Data actions](./data-actions.md)**: Set up actions that insert, update, or delete rows in your database.
- **[Data apps](../data-apps/manage.md)**\*: Manage your [data apps](../data-apps/start.md), the custom apps that an AI coding agent builds on your semantic layer. Admins see what each app reads and writes, take apps offline, and choose which groups can open each app. Only admins see Data apps.
- **[Glossary](./semantic-layer/glossary.md)**: Define terms relevant to your business, both for people and agents trying to understand your data.
diff --git a/docs/data-modeling/images/add-product-data-action.png b/docs/data-modeling/images/add-product-data-action.png
new file mode 100644
index 00000000000..378512a679c
Binary files /dev/null and b/docs/data-modeling/images/add-product-data-action.png differ
diff --git a/docs/data-modeling/images/data-action-form.png b/docs/data-modeling/images/data-action-form.png
new file mode 100644
index 00000000000..deaaaa153d6
Binary files /dev/null and b/docs/data-modeling/images/data-action-form.png differ
diff --git a/docs/data-modeling/models/actions/basic.md b/docs/data-modeling/models/actions/basic.md
index 77f2b4c9ac4..b3eb05cafc4 100644
--- a/docs/data-modeling/models/actions/basic.md
+++ b/docs/data-modeling/models/actions/basic.md
@@ -12,11 +12,11 @@ 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/models.md) that only wraps a single database table.
+Only admins can create basic actions. 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.
-3. Click on the **...** next to the **New Action** and select **Create basic actions**.
+1. Visit the model and click the **info** button.
+2. Click **Actions**.
+3. Click the **...** next to **New action**, and select **Create basic actions**.
### Basic action limitations
@@ -58,9 +58,15 @@ The Update basic action requires you to pass a value for the entity key.
See [Actions in dashboards](../../../dashboards/actions.md).
-## Archiving basic actions
+## Disable basic actions
-Because basic actions are made of magic, you cannot archive them. You can just toggle them on or off. From the model detail page, next to the **New action** button, click on the **...** menu and click **Disable basic actions**.
+You can't archive basic actions, or delete them one at a time. Instead, admins can turn off all of a model's basic actions at once:
+
+1. Visit the model, click the **info** button, and click **Actions**.
+2. Click the **...** next to **New action**, and select **Disable basic actions**.
+3. Click **Disable**.
+
+Disabling basic actions also removes any dashboard buttons that use them.
## Basic actions from object detail view
diff --git a/docs/data-modeling/models/actions/custom.md b/docs/data-modeling/models/actions/custom.md
index 0eb1b18a941..a829a969a14 100644
--- a/docs/data-modeling/models/actions/custom.md
+++ b/docs/data-modeling/models/actions/custom.md
@@ -12,11 +12,14 @@ Write SQL to update records in your databases.
## Creating a custom action
-> You must be in a group with Native query editing access to create an action.
+Only admins can create custom actions.
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.
+2. Visit the model and click the **info** button.
+3. Click **Actions**.
+4. Click **New action**.
+
+To write an action without a model, see [Data actions](../../data-actions.md).
In the action editor, you can write your own code to create an action, like writing an action that would only update a subset of the columns in a table. See [Example actions](#example-custom-actions).
@@ -60,12 +63,14 @@ The appearance tab in the action editor modal will display a preview of the vari
## Action settings
-From the model detail page, click on the **three dot menu** (...) next to the action. Once in the action editor, click on the **gear** icon to bring up the action settings.
+To change an action's settings, open the action and click the **gear** icon (**Action settings**).
### Make public
Creates a publicly shareable link to the action form. Anyone with access to that link can fill out the form and run the action. Useful for creating surveys.
+Only admins can make an action public, and [public sharing](../../../embedding/public-links.md) must be on.
+
![Public action form](./images/public-form.png)
### Set a success message
@@ -74,6 +79,14 @@ Here you can edit the success message, which is the message Metabase will displa
If something goes wrong, Metabase will display the error message it received from the database.
+## Deleting a custom action
+
+Only admins can delete a custom action. Deleting it also removes any dashboard buttons and public forms that use it. Moving the model to the trash also deletes its actions; see [Deleting a model deletes its actions](./introduction.md#deleting-a-model-deletes-its-actions).
+
+1. Visit the model, click the **info** button, and click **Actions**.
+2. Click the **...** next to the action, and select **Delete**.
+3. Confirm by clicking **Delete**.
+
## Example custom actions
### Example `UPDATE` action
diff --git a/docs/data-modeling/models/actions/introduction.md b/docs/data-modeling/models/actions/introduction.md
index 3e59aafaa18..13d72c81d1d 100644
--- a/docs/data-modeling/models/actions/introduction.md
+++ b/docs/data-modeling/models/actions/introduction.md
@@ -22,7 +22,7 @@ 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/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)).
+Actions can belong to a [model](../../../data-modeling/models/models.md), or stand on their own as [data actions](../../data-actions.md). Either way, actions only run on the raw tables in your database (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).
@@ -30,13 +30,13 @@ If you're an admin who just wants to edit data in your tables, check out [Editab
For actions to work, you'll first need to do the following two things:
-1. **Enable data 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 **Data 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.
+1. **Enable data 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. In the **Data actions** section, turn on the **Data actions** toggle. 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. This toggle covers both model actions and [data actions](../../data-actions.md).
+2. **For actions on models, create at least one model from that database.** Model 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 them. [Data actions](../../data-actions.md) don't need a model.
## 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 run an action**, all you need is view access to the action's model or dashboard (or a link to a public action).
+- **To create, edit, or delete an action**, you must be an admin. But people with Curate access to a model's collection can delete the model's actions by [moving the model to the trash](#deleting-a-model-deletes-its-actions).
+- **To run an action**, all you need is view access to the action's model or [data actions](../../data-actions.md) folder (or a link to a public action). To run an action from a [dashboard button](../../../dashboards/actions.md), you also need view access to the dashboard. But people with [row and column security](../../../permissions/row-and-column-security.md#people-with-row-and-column-security-cant-run-actions) on any table in a database can't run actions on that database.
## Types of actions
@@ -52,6 +52,21 @@ There are multiple ways to run actions:
- [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 the **Run** tab of a [data action](../../data-actions.md#run-a-data-action).
+
+## Deleting a model deletes its actions
+
+A model's actions don't outlive the model. Metabase deletes all of a model's actions, and the dashboard buttons that use them, when someone:
+
+- Moves the model to the trash.
+- Moves the collection that the model is in to the trash.
+- Turns the model back into a saved question.
+
+This includes people who aren't admins: anyone with [Curate access](../../../permissions/collections.md#curate-access) to the model's collection can do these things.
+
+Restoring the model from the trash doesn't bring its actions back.
+
+[Data actions](../../data-actions.md) don't belong to a model, so they work differently: when you archive a data actions folder, Metabase archives its actions too, and unarchiving the folder brings them back. See [Archive and unarchive data actions](../../data-actions.md#archive-and-unarchive-data-actions).
## Auditing actions
@@ -61,7 +76,7 @@ Metabase records every action run in the [Query log](../../../usage-and-performa
## Actions change data in tables, which affect models
-Just something to clarify here: actions, even though they are added to models, make their changes to the underlying table that a model queries. Which means that anyone who has access to the underlying table, or to questions or other models based on that table, will be able to see the effects of an action. Tools other than Metabase that are connected to that database will also pick up these changes.
+Just something to clarify here: actions, even when they belong to models, make their changes to the underlying table that a model queries. Which means that anyone who has access to the underlying table, or to questions or other models based on that table, will be able to see the effects of an action. Tools other than Metabase that are connected to that database will also pick up these changes.
In this sense, models are containers for actions; models are a way to organize actions. In fact, you could (in theory) add a [custom action](./custom.md) to a model that performs some update unrelated to its model's data. For example, you could write a custom action that updates the `Accounts` table, and add that action to a model that only queries an unrelated table (e.g., the `Orders` table). But, you know, maybe don't do that (unless you have a good reason). [Basic actions](./basic.md), however, are only available for models that wrap a single raw table.
diff --git a/docs/data-modeling/models/actions/start.md b/docs/data-modeling/models/actions/start.md
index f45471f0a0c..0686c376f47 100644
--- a/docs/data-modeling/models/actions/start.md
+++ b/docs/data-modeling/models/actions/start.md
@@ -24,6 +24,10 @@ Metabase will create basic actions that auto-track a model's schema.
Write SQL to create new actions.
+## [Data actions](../../data-actions.md)
+
+Create actions that you can run in Data Studio, or share as public forms.
+
## [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/semantic-layer/library.md b/docs/data-modeling/semantic-layer/library.md
index 40c331c8774..6aceab67a44 100644
--- a/docs/data-modeling/semantic-layer/library.md
+++ b/docs/data-modeling/semantic-layer/library.md
@@ -154,7 +154,7 @@ If you [duplicate a dashboard](../../dashboards/introduction.md#duplicating-a-da
## 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. When you sync the Library, Metabase also syncs your SQL snippets and [glossary](glossary.md) terms.
+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, [data actions](../data-actions.md), and [glossary](glossary.md) terms.
## Library permissions
diff --git a/docs/data-modeling/tools/graph.md b/docs/data-modeling/tools/graph.md
index f9f92960111..0fa0fec2551 100644
--- a/docs/data-modeling/tools/graph.md
+++ b/docs/data-modeling/tools/graph.md
@@ -44,7 +44,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 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.
+You can also view an item's dependencies from its page in Data Studio. Published tables, metrics, snippets, segments, measures, transforms, and [data actions](../data-actions.md) 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/databases/connections/athena.md b/docs/databases/connections/athena.md
index 601e7436aa7..5456eba4715 100644
--- a/docs/databases/connections/athena.md
+++ b/docs/databases/connections/athena.md
@@ -213,10 +213,6 @@ If Metabase also needs to create tables, you'll need additional AWS Glue permiss
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
-
-There aren't (yet) any model features available for Athena.
-
## Database routing
With database routing, an admin can build a question once using a single data connection, and the question will run its query against a different data connection with the same schema depending on who is viewing the question.
diff --git a/docs/databases/connections/bigquery.md b/docs/databases/connections/bigquery.md
index 4a5d26bc343..acc131409c7 100644
--- a/docs/databases/connections/bigquery.md
+++ b/docs/databases/connections/bigquery.md
@@ -165,10 +165,6 @@ If you're having trouble with your BigQuery connection, you can check out this [
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
-
-There aren't (yet) any model features available for BigQuery.
-
## Database routing
With database routing, an admin can build a question once using one database, and the question will run its query against a different database with the same schema depending on who is viewing the question.
diff --git a/docs/databases/connections/clickhouse.md b/docs/databases/connections/clickhouse.md
index 20310ede5a3..dc91ef06f81 100644
--- a/docs/databases/connections/clickhouse.md
+++ b/docs/databases/connections/clickhouse.md
@@ -111,10 +111,6 @@ Metabase supports [CSV uploads](../uploads.md) to ClickHouse Cloud and self-host
For self-hosted deployments, the database user must be able to read the `system.clusters` table, as well as create tables and insert data.
-## Model features
-
-There aren't (yet) any model features for ClickHouse.
-
## Danger zone
See [Danger zone](../danger-zone.md).
diff --git a/docs/databases/connections/databricks.md b/docs/databases/connections/databricks.md
index 4d17efa3546..32a67ce76f8 100644
--- a/docs/databases/connections/databricks.md
+++ b/docs/databases/connections/databricks.md
@@ -105,10 +105,6 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
-
-There aren't (yet) any model features available for Databricks.
-
## Database routing
With database routing, an admin can build a question once using one database, and the question will run its query against a different database with the same schema depending on who is viewing the question.
diff --git a/docs/databases/connections/druid.md b/docs/databases/connections/druid.md
index 1b504c31472..6e236e8e16f 100644
--- a/docs/databases/connections/druid.md
+++ b/docs/databases/connections/druid.md
@@ -62,10 +62,6 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
-
-There aren't (yet) any model features available for Druid.
-
## Database routing
With database routing, an admin can build a question once using one database, and the question will run its query against a different database with the same schema depending on who is viewing the question.
diff --git a/docs/databases/connections/mysql.md b/docs/databases/connections/mysql.md
index 954bb24e3a9..c5c8668f6ce 100644
--- a/docs/databases/connections/mysql.md
+++ b/docs/databases/connections/mysql.md
@@ -191,15 +191,11 @@ If your password contains characters that aren't UTF-8, then you might need to a
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
+## Data actions
-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.
+Turn on **Data actions** to let people run actions on this database: both [actions on models](../../data-modeling/models/actions/introduction.md) and [data actions](../../data-modeling/data-actions.md). Actions can read, write, and delete data, so your database user needs write permissions.
-### Data actions
-
-Turn this setting on to allow [actions](../../data-modeling/models/actions/introduction.md) that use this database to be run. Actions can read, write, and delete data. Your database user will need write permissions.
-
-### Model persistence
+## Model persistence
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.
diff --git a/docs/databases/connections/postgresql.md b/docs/databases/connections/postgresql.md
index 2bf31dcc587..509a86e03ce 100644
--- a/docs/databases/connections/postgresql.md
+++ b/docs/databases/connections/postgresql.md
@@ -190,15 +190,11 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
+## Data actions
-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.
+Turn on **Data actions** to let people run actions on this database: both [actions on models](../../data-modeling/models/actions/introduction.md) and [data actions](../../data-modeling/data-actions.md). Actions can read, write, and delete data, so your database user needs write permissions.
-### Data actions
-
-Turn this setting on to allow [actions](../../data-modeling/models/actions/introduction.md) that use this database to be run. Actions can read, write, and delete data. Your database user will need write permissions.
-
-### Model persistence
+## Model persistence
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.
diff --git a/docs/databases/connections/redshift.md b/docs/databases/connections/redshift.md
index 3e06f613fef..a7c8513c83f 100644
--- a/docs/databases/connections/redshift.md
+++ b/docs/databases/connections/redshift.md
@@ -102,11 +102,7 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
-
-Choose whether to enable features related to Metabase models. These will often require a write connection.
-
-### Model persistence
+## Model persistence
You 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.
diff --git a/docs/databases/connections/snowflake.md b/docs/databases/connections/snowflake.md
index c33d37b071d..97e553cacff 100644
--- a/docs/databases/connections/snowflake.md
+++ b/docs/databases/connections/snowflake.md
@@ -170,10 +170,6 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
-
-There aren't (yet) any model features available for Snowflake.
-
## Database routing
With database routing, an admin can build a question once using one database, and the question will run its query against a different database with the same schema depending on who is viewing the question.
diff --git a/docs/databases/connections/starburst.md b/docs/databases/connections/starburst.md
index 7ff6c89c140..693629b1580 100644
--- a/docs/databases/connections/starburst.md
+++ b/docs/databases/connections/starburst.md
@@ -95,10 +95,6 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
-
-There aren't (yet) any model features for Starburst.
-
## Database routing
With database routing, an admin can build a question once using one database (data catalog), and the question will run its query against a different data catalog with the same schema depending on who is viewing the question.
diff --git a/docs/databases/connections/vertica.md b/docs/databases/connections/vertica.md
index 7ce6db038e8..8adf77ee6ae 100644
--- a/docs/databases/connections/vertica.md
+++ b/docs/databases/connections/vertica.md
@@ -45,10 +45,6 @@ The process for adding plugins when running via Docker is similar, but you'll ne
Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
-## Model features
-
-There aren't (yet) any model features for Vertica.
-
## Danger zone
See [Danger zone](../danger-zone.md).
diff --git a/docs/exploration-and-organization/delete-and-restore.md b/docs/exploration-and-organization/delete-and-restore.md
index ffd1172afd5..97b2f525a68 100644
--- a/docs/exploration-and-organization/delete-and-restore.md
+++ b/docs/exploration-and-organization/delete-and-restore.md
@@ -91,11 +91,13 @@ What happens to related items when you delete a dashboard?
What happens to related items when you delete a model?
-| Related item | In Trash | Permanently deleted | Restored |
-| ---------------------------------- | -------------- | ---------------------------------- | -------------- |
-| Question based on deleted question | Works normally | Breaks with `Card not found` error | Reactivated |
-| Dashboard | Card removed | Card removed | Card restored |
-| Action | Works normally | Deleted | Works normally |
+| Related item | In Trash | Permanently deleted | Restored |
+| ---------------------------------- | -------------- | ---------------------------------- | ------------- |
+| Question based on deleted question | Works normally | Breaks with `Card not found` error | Reactivated |
+| Dashboard | Card removed | Card removed | Card restored |
+| Action | Deleted | Deleted | Not restored |
+
+Metabase also removes the dashboard buttons that use the model's actions. The same happens when you move the collection that the model is in to the trash. See [Deleting a model deletes its actions](../data-modeling/models/actions/introduction.md#deleting-a-model-deletes-its-actions).
## Collections
diff --git a/docs/installation-and-operation/remote-sync.md b/docs/installation-and-operation/remote-sync.md
index 7107c17aa58..721c0569726 100644
--- a/docs/installation-and-operation/remote-sync.md
+++ b/docs/installation-and-operation/remote-sync.md
@@ -10,7 +10,7 @@ description: Version control your dashboards, questions, and transforms. Sync yo
Remote Sync lets you develop analytics content in your Metabase and automatically deploy it to a read-only production Metabase through Git. Remote Sync can sync:
- Top-level collections (dashboards, questions, models, metrics)
-- Library content (published tables with their segments and measures, plus metrics, dashboards, snippets, and the glossary)
+- Library content (published tables with their segments and measures, plus metrics, dashboards, snippets, data actions, and the glossary)
- Transforms
- [Data apps](../data-apps/build.md#what-syncs-with-a-data-app), with their bundles and collections
@@ -372,7 +372,7 @@ Remote Sync uses the same serialization format as the [Metabase CLI serializatio
- Documents
- Timelines and events
- Collection structure and metadata
-- Library content (published tables, metrics, dashboards, snippets, segments, measures, glossary)
+- Library content (published tables, metrics, dashboards, snippets, data actions, segments, measures, glossary)
- Transforms (including tags, tests, and folders)
- [Data apps](../data-apps/build.md#what-syncs-with-a-data-app), with their bundles and collections
diff --git a/docs/permissions/row-and-column-security.md b/docs/permissions/row-and-column-security.md
index 2ecd504b787..3b84bd15b93 100644
--- a/docs/permissions/row-and-column-security.md
+++ b/docs/permissions/row-and-column-security.md
@@ -323,6 +323,12 @@ Use a [transform](../data-modeling/transforms/transforms-overview.md) to create
People in groups with row and column security can't create Slack [alerts](../questions/alerts.md) or [dashboard subscriptions](../dashboards/subscriptions.md). Email alerts and subscriptions are still available. See [Notification permissions](./notifications.md).
+### People with row and column security can't run actions
+
+If row and column security applies to a person on any table in a database, that person can't run [actions](../data-modeling/models/actions/introduction.md) on that database. Actions write to tables directly, so they would get around the row and column security. For basic actions and data actions made from a table, Metabase shows the error **You can't run actions on this database because row and column security applies to your data access.** For actions written in SQL, Metabase shows a generic permissions error.
+
+[Public action forms](../data-modeling/models/actions/custom.md#make-public) don't check row and column security. An admin can make any action public, even on a database where row and column security applies to some groups, and anyone with the link can then run the action. Before you make an action public, make sure that it's OK for anyone to make that change to your data.
+
## Further reading
- [Row and column security examples](./row-and-column-security-examples.md)
diff --git a/docs/util/data/nav.yml b/docs/util/data/nav.yml
index 7577a43b3f7..a3d9f0a3737 100644
--- a/docs/util/data/nav.yml
+++ b/docs/util/data/nav.yml
@@ -243,6 +243,8 @@ categories:
url: "data-modeling/tools/graph"
- name: "Replace data sources"
url: "data-modeling/tools/replace-data-sources"
+ - name: "Data actions"
+ url: "data-modeling/data-actions"
- name: "Editable tables"
url: "data-modeling/editable-tables"
- name: "Models"