Skip to content

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

docs: it's writable not writeable (#70877)

Alex Yarosh106a707fcc30
diff --git a/docs/data-studio/transforms/transforms-overview.md b/docs/data-studio/transforms/transforms-overview.md
index 0eb670824eb..76f5e424254 100644
--- a/docs/data-studio/transforms/transforms-overview.md
+++ b/docs/data-studio/transforms/transforms-overview.md
@@ -35,7 +35,7 @@ Currently, Metabase can create transforms on the following databases:
You can't create transforms on databases that have [Database routing](../../permissions/database-routing.md) enabled, or on Metabase's Sample Database.
-Transforms will create tables in your database, so the database user you use for your connection must have appropriate privileges. See [Database users, roles, and privileges](../../databases/users-roles-privileges.md).
+Transforms will create tables in your database, so the database user you use for your connection must have appropriate privileges. See [Database users, roles, and privileges](../../databases/users-roles-privileges.md). We suggest using a [Writable connection](../../databases/writable-connection.md) option for your database.
## Types of transforms
diff --git a/docs/databases/connections/athena.md b/docs/databases/connections/athena.md
index 7e5602457d4..b6ca4244152 100644
--- a/docs/databases/connections/athena.md
+++ b/docs/databases/connections/athena.md
@@ -209,9 +209,9 @@ If Metabase also needs to create tables, you'll need additional AWS Glue permiss
}
```
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/bigquery.md b/docs/databases/connections/bigquery.md
index 8c4d4d44566..d043d419c57 100644
--- a/docs/databases/connections/bigquery.md
+++ b/docs/databases/connections/bigquery.md
@@ -161,9 +161,9 @@ FROM [my_dataset.my_table]
If you're having trouble with your BigQuery connection, you can check out this [troubleshooting guide](../../troubleshooting-guide/bigquery-drive.md) that covers BigQuery issues, [this one](../../troubleshooting-guide/db-connection.md) on data warehouse connections, or visit [Metabase's discussion forum](https://discourse.metabase.com/search?q=bigquery) to see if someone has encountered and resolved a similar issue.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/clickhouse.md b/docs/databases/connections/clickhouse.md
index 3a5c7b72607..b1762f1993c 100644
--- a/docs/databases/connections/clickhouse.md
+++ b/docs/databases/connections/clickhouse.md
@@ -101,9 +101,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/databricks.md b/docs/databases/connections/databricks.md
index 38f263e8c0c..fbc9805e7f9 100644
--- a/docs/databases/connections/databricks.md
+++ b/docs/databases/connections/databricks.md
@@ -101,9 +101,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/druid.md b/docs/databases/connections/druid.md
index 8f511d04dad..4536edce8c6 100644
--- a/docs/databases/connections/druid.md
+++ b/docs/databases/connections/druid.md
@@ -64,9 +64,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/mariadb.md b/docs/databases/connections/mariadb.md
index a5f6d5afc81..f8114d24c86 100644
--- a/docs/databases/connections/mariadb.md
+++ b/docs/databases/connections/mariadb.md
@@ -101,9 +101,9 @@ JSON schema inference doesn't work with MariaDB, due to implementation differenc
If your password contains characters that aren't UTF-8, then you might need to add an additional variable to the connection string `passwordCharacterEncoding=<your_encoding_here>`. This ensures that MariaDB understands the special characters in the password during authentication.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Database routing
diff --git a/docs/databases/connections/mongodb.md b/docs/databases/connections/mongodb.md
index 8b79ad453c8..fde5131ffdd 100644
--- a/docs/databases/connections/mongodb.md
+++ b/docs/databases/connections/mongodb.md
@@ -130,9 +130,9 @@ Instead, Metabase gets a sample of the fields in a collection by scanning a samp
If you're not seeing all of the fields show up for a collection in Metabase, one workaround is to include all possible keys in the first document of the collection, and give those keys null values. That way, Metabase will be able to recognize the correct schema for the entire collection.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Database routing
diff --git a/docs/databases/connections/mysql.md b/docs/databases/connections/mysql.md
index d8617540b2d..7e85a0a71eb 100644
--- a/docs/databases/connections/mysql.md
+++ b/docs/databases/connections/mysql.md
@@ -187,9 +187,9 @@ mysql:
If your password contains characters that aren't UTF-8, then you might need to add an additional variable to the connection string `passwordCharacterEncoding=<your_encoding_here>`. This ensures that MySQL understands the special characters in the password during authentication.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/oracle.md b/docs/databases/connections/oracle.md
index 459348004a8..d39f2a5549f 100644
--- a/docs/databases/connections/oracle.md
+++ b/docs/databases/connections/oracle.md
@@ -131,9 +131,9 @@ For example, if you're running Metabase from a directory called `/app/`, you sho
The process for adding plugins when running via Docker is similar, but you'll need to mount the `plugins` directory. Refer to instructions [here](../../installation-and-operation/running-metabase-on-docker.md#adding-external-dependencies-or-plugins) for more details.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Danger zone
diff --git a/docs/databases/connections/postgresql.md b/docs/databases/connections/postgresql.md
index baeaaba3a26..70ebbde0697 100644
--- a/docs/databases/connections/postgresql.md
+++ b/docs/databases/connections/postgresql.md
@@ -186,9 +186,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/presto.md b/docs/databases/connections/presto.md
index 160fa165736..c75062bb09c 100644
--- a/docs/databases/connections/presto.md
+++ b/docs/databases/connections/presto.md
@@ -94,9 +94,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Database routing
diff --git a/docs/databases/connections/redshift.md b/docs/databases/connections/redshift.md
index 57e5a743840..46a050db698 100644
--- a/docs/databases/connections/redshift.md
+++ b/docs/databases/connections/redshift.md
@@ -98,9 +98,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/snowflake.md b/docs/databases/connections/snowflake.md
index 24c9a30d1f1..87792b5737e 100644
--- a/docs/databases/connections/snowflake.md
+++ b/docs/databases/connections/snowflake.md
@@ -133,9 +133,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/sparksql.md b/docs/databases/connections/sparksql.md
index ba3fac40e91..517497b62b5 100644
--- a/docs/databases/connections/sparksql.md
+++ b/docs/databases/connections/sparksql.md
@@ -77,9 +77,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Danger zone
diff --git a/docs/databases/connections/sql-server.md b/docs/databases/connections/sql-server.md
index 0b86974cd6e..96a935ce0f9 100644
--- a/docs/databases/connections/sql-server.md
+++ b/docs/databases/connections/sql-server.md
@@ -97,9 +97,9 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
To connect to Azure SQL, you'll need to set the port to 1433.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Database routing
diff --git a/docs/databases/connections/sqlite.md b/docs/databases/connections/sqlite.md
index 0bdd190ef2d..67ae9971a1f 100644
--- a/docs/databases/connections/sqlite.md
+++ b/docs/databases/connections/sqlite.md
@@ -61,9 +61,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Database routing
diff --git a/docs/databases/connections/starburst.md b/docs/databases/connections/starburst.md
index 858cab40934..1c53a069966 100644
--- a/docs/databases/connections/starburst.md
+++ b/docs/databases/connections/starburst.md
@@ -91,9 +91,9 @@ Turn this option **ON** to scan a sample of values every time Metabase runs a [s
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/connections/vertica.md b/docs/databases/connections/vertica.md
index 5934f5c0dac..d64a966fdb2 100644
--- a/docs/databases/connections/vertica.md
+++ b/docs/databases/connections/vertica.md
@@ -41,9 +41,9 @@ For example, if you're running Metabase from a directory called `/app/`, you sho
The process for adding plugins when running via Docker is similar, but you'll need to mount the `plugins` directory. Refer to instructions [here](../../installation-and-operation/running-metabase-on-docker.md#adding-external-dependencies-or-plugins) for more details.
-## Writeable connection
+## Writable connection
-Set up an additional connection used for write operations. See [Writeable connections](../writeable-connection.md).
+Set up an additional connection used for write operations. See [Writable connections](../writable-connection.md).
## Model features
diff --git a/docs/databases/users-roles-privileges.md b/docs/databases/users-roles-privileges.md
index 70f8171f0fb..7870a668bee 100644
--- a/docs/databases/users-roles-privileges.md
+++ b/docs/databases/users-roles-privileges.md
@@ -21,7 +21,7 @@ Bundling your privileges into roles based on use cases makes it easier to manage
- Use the same `analytics` role for other BI tools in your [data stack](https://www.metabase.com/learn/grow-your-data-skills/data-fundamentals/data-landscape) that need read-only access to the analytics tables in your database.
- Revoke the write access for `metabase_model_persistence` without affecting the write access for `metabase_actions`.
-For operations that require write access, we recommend using separate [writeable connections](./writeable-connection.md).
+For operations that require write access, we recommend using separate [writable connections](./writable-connection.md).
## Minimum database privileges
@@ -102,7 +102,7 @@ if you're using actions or editable tables, then in addition to the [minimum dat
- Create a new role called `metabase_writer`.
- Give the role `INSERT`, `UPDATE`, and `DELETE` privileges to the relevant tables.
-- Give the `metabase_writer` role to the user used for your database connection. We recommend using a [writeable connection](./writeable-connection.md) and only granting this role to the user used for the writeable connection.
+- Give the `metabase_writer` role to the user used for your database connection. We recommend using a [writable connection](./writable-connection.md) and only granting this role to the user used for the writable connection.
```sql
-- Create a role to bundle database privileges for Metabase writing to your database.
@@ -124,7 +124,7 @@ In addition to the [minimum database privileges](#minimum-database-privileges):
- Create a new role called `metabase_model_persistence`.
- Give the role `CREATE` access to the database.
- Give the role `INSERT`, `UPDATE`, and `DELETE` privileges to the schema used for model persistence.
-- Give the `metabase_model_persistence` role to the user used for your database connection. We recommend using a [writeable connection](./writeable-connection.md) and only granting this role to the user used for the writeable connection.
+- Give the `metabase_model_persistence` role to the user used for your database connection. We recommend using a [writable connection](./writable-connection.md) and only granting this role to the user used for the writable connection.
```sql
-- Create a role to bundle database privileges for Metabase model persistence.
@@ -144,20 +144,20 @@ GRANT metabase_model_persistence TO metabase;
## Privileges to enable transforms
-[Transforms](../data-studio/transforms/transforms-overview.md) let Metabase write query results back to your database. We suggest that you create a dedicated schema for your transforms. Metabase's database user will need to be able to create and drop transform tables. We recommend using a [writeable connection](./writeable-connection.md) and only granting write access to the user used for the writeable connection.
+[Transforms](../data-studio/transforms/transforms-overview.md) let Metabase write query results back to your database. We suggest that you create a dedicated schema for your transforms. Metabase's database user will need to be able to create and drop transform tables. We recommend using a [writable connection](./writable-connection.md) and only granting write access to the user used for the writable connection.
In addition to the [minimum database privileges](#minimum-database-privileges):
- Create a new role called `metabase_transforms`.
- Create a dedicated schema for transforms.
- Give the `metabase_transforms` role `CREATE TABLE` / `ALTER` / `DROP` privileges for the specified schema.
-- Give the `metabase_transforms` role to the user used for your database connection. We recommend using a [writeable connection](./writeable-connection.md) and only granting this role to the user used for the writeable connection.
+- Give the `metabase_transforms` role to the user used for your database connection. We recommend using a [writable connection](./writable-connection.md) and only granting this role to the user used for the writable connection.
In certain cases, Metabase will give you an option to create new schemas for transforms, in which case you'll also need `CREATE SCHEMA` privileges for your metabase users (or `CREATE DATABASE` for ClickHouse).
## Privileges to enable uploads
-You can [upload CSVs](../databases/uploads.md) to supported databases. Metabase's database user should have write access (`INSERT`, `UPDATE`, `DELETE`) to the schema where you want to store the uploads. We recommend using a [writeable connection](./writeable-connection.md) and only granting write access to the user used for the writeable connection.
+You can [upload CSVs](../databases/uploads.md) to supported databases. Metabase's database user should have write access (`INSERT`, `UPDATE`, `DELETE`) to the schema where you want to store the uploads. We recommend using a [writable connection](./writable-connection.md) and only granting write access to the user used for the writable connection.
You'll first need to create a schema to store uploads (or use an existing schema) and tell Metabase that you want to [use that schema to store uploads](./uploads.md#select-the-database-and-schema-that-you-want-to-store-the-data-in).
@@ -228,7 +228,7 @@ We recommend bundling privileges into roles based on use cases per customer. Tha
## Further reading
-- [Writeable connections](./writeable-connection.md)
+- [Writable connections](./writable-connection.md)
- [Permissions strategies](https://www.metabase.com/learn/metabase-basics/administration/permissions/strategy)
- [Permissions introduction](../permissions/introduction.md)
- [People overview](../people-and-groups/start.md)
diff --git a/docs/databases/writable-connection.md b/docs/databases/writable-connection.md
new file mode 100644
index 00000000000..f51a5902878
--- /dev/null
+++ b/docs/databases/writable-connection.md
@@ -0,0 +1,62 @@
+---
+title: Writable connection
+summary: Add an optional separate database connection for write operations like transforms or editable tables to keep the main Metabase connection read-only for analytics.
+redirect_from:
+ - /docs/latest/databases/writeable-connection
+---
+
+## Writable connection
+
+> Writable connection requires the **Advanced transforms (SQL + Python)** add-on
+
+_Admin > Databases > Writable connection_
+
+Writable connection is an optional connection that Metabase will use for functionality that involves writing into the database (for example, transforms or CSV uploads). This allows you to keep your main Metabase connection read-only, and only to switch to connection with write permissions for the operations that require write access.
+
+![Writable connection in database settings](./images/writeable-connection.png)
+
+## How writable connection works
+
+Writable connection is an additional connection option added to an existing database connection.
+
+When a writable connection is configured for a database, Metabase automatically switches between connections behind the scenes based on what people are doing with the database. The main connection is used for querying, and the writable connection is used for [features that require writes](#features-that-use-writable-connection).
+
+Writable connection can use a different database user than the main connection, or even connect to a different database. For example, your main connection (used for querying) can go to a read replica, but the writable connection can be to a primary database.
+
+## Add a writable connection
+
+To add a writable connection to a database:
+
+1. Go to **Admin > Databases**.
+2. Select the database to add a writable connection to.
+3. Under **Writable connection**, click **Add writable connection**.
+4. Metabase will pre-fill some fields with information from your main connection. Input the credentials for the writable connection.
+5. Click **Save**. Metabase will try to connect using the new connection.
+
+## Remove a writable connection
+
+To remove a writable connection from a database:
+
+1. Go to **Admin > Databases**.
+2. Select the database you want to remove the writable connection from.
+3. Under **Writable connection**, click **Remove writable connection**.
+
+Once writable connection is removed, Metabase will revert to using the main connection for [features that need write access](#features-that-use-writable-connection), so your main connection will need to have appropriate database permissions, see [Users, roles, and privileges](./users-roles-privileges.md)
+
+## Features that use writable connection
+
+When configured, writable connection will be used for:
+
+- [Transforms](../data-studio/transforms/transforms-overview.md)
+- [CSV uploads](../databases/uploads.md)
+- [Editable tables](../data-modeling/editable-tables.md)
+- [Actions](../actions/introduction.md)
+- [Model persistence](../data-modeling/model-persistence.md)
+
+Your writable connection will need to have the privileges required for these operations. See [Users, roles, and privileges](./users-roles-privileges.md).
+
+## Limitations
+
+- Writable connection can't be used with [database routing](../permissions/database-routing.md).
+
+- Writable connection must use the same database engine as the primary connection - so for example, if the primary connection is to a PostgreSQL database, the writable connection must be to a PostgreSQL database as well.
diff --git a/docs/databases/writeable-connection.md b/docs/databases/writeable-connection.md
deleted file mode 100644
index a6cc62eca23..00000000000
--- a/docs/databases/writeable-connection.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Writeable connections
-summary: Add an optional separate database connection for write operations like transforms or editable tables to keep the main Metabase connection read-only for analytics.
----
-
-## Writeable connections
-
-> Writeable connection requires the **Advanced transforms (SQL + Python)** add-on
-
-_Admin > Databases > Writeable connection_
-
-Writeable connection is an optional connection that Metabase will use for functionality that involves writing into the database (for example, transforms or CSV uploads). This allows you to keep your main Metabase connection read-only, and only to switch to connection with write permissions for the operations that require write access.
-
-![Writeable connection in database settings](./images/writeable-connection.png)
-
-## How writeable connection works
-
-Writeable connection is an additional connection option added to an existing database connection.
-
-When a writeable connection is configured for a database, Metabase automatically switches between connections behind the scenes based on what people are doing with the database. The main connection is used for querying, and the writeable connection is used for [features that require writes](#features-that-use-writeable-connection).
-
-Writeable connection can use a different database user than the main connection, or even connect to a different database. For example, your main connection (used for querying) can go to a read replica, but the writeable connection can be to a primary database.
-
-## Add a writeable connection
-
-To add a writeable connection to a database:
-
-1. Go to **Admin > Databases**.
-2. Select the database to add a writeable connection to.
-3. Under **Writeable connection**, click **Add writeable connection**.
-4. Metabase will pre-fill some fields with information from your main connection. Input the credentials for the writeable connection.
-5. Click **Save**. Metabase will try to connect using the new connection.
-
-## Remove a writeable connection
-
-To remove a writeable connection from a database:
-
-1. Go to **Admin > Databases**.
-2. Select the database you want to remove the writeable connection from.
-3. Under **Writeable connection**, click **Remove writeable connection**.
-
-Once writeable connection is removed, Metabase will revert to using the main connection for [features that need write access](#features-that-use-writeable-connection), so your main connection will need to have appropriate database permissions, see [Users, roles, and privileges](./users-roles-privileges.md)
-
-## Features that use writeable connection
-
-When configured, writeable connection will be used for:
-
-- [Transforms](../data-studio/transforms/transforms-overview.md)
-- [CSV uploads](../databases/uploads.md)
-- [Editable tables](../data-modeling/editable-tables.md)
-- [Actions](../actions/introduction.md)
-- [Model persistence](../data-modeling/model-persistence.md)
-
-Your writeable connection will need to have the privileges required for these operations. See [Users, roles, and privileges](./users-roles-privileges.md).
-
-## Limitations
-
-- Writeable connection can't be used with [database routing](../permissions/database-routing.md).
-
-- Writeable connection must use the same database engine as the primary connection - so for example, if the primary connection is to a PostgreSQL database, the writeable connection must be to a PostgreSQL database as well.
diff --git a/docs/permissions/database-routing.md b/docs/permissions/database-routing.md
index c4d9420a669..7cd5e596fc0 100644
--- a/docs/permissions/database-routing.md
+++ b/docs/permissions/database-routing.md
@@ -40,7 +40,7 @@ Different database have different setups, so _what_ you can route between (datab
Database routing **can't be used** on databases with:
-- [Writeable connections](../databases/writeable-connection.md)
+- [Writable connections](../databases/writable-connection.md)
- [Editable tables](../data-modeling/editable-tables.md)
- [Actions](../actions/introduction.md)
- [CSV uploads](../databases/uploads.md)