From f0db81fccd1f167de8259eb6c2252afae8876195 Mon Sep 17 00:00:00 2001
From: Alex Yarosh <alexandra@metabase.com>
Date: Wed, 19 Jun 2024 11:28:12 -0400
Subject: [PATCH] docs: change paid to pro/enterprise (#44383)
* docs: change paid to pro/enterprise
* Apply suggestions from code review
Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>
---------
Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>
---
docs/api-documentation.md | 23 +++++++++----------
docs/configuring-metabase/config-file.md | 4 ++--
docs/configuring-metabase/fonts.md | 3 +--
.../setting-up-metabase.md | 2 +-
docs/configuring-metabase/start.md | 2 +-
docs/databases/connecting.md | 2 +-
docs/databases/encrypting-details-at-rest.md | 2 +-
docs/embedding/interactive-embedding.md | 2 +-
.../running-metabase-on-docker.md | 19 ++++++++-------
.../running-metabase-on-podman.md | 6 +----
.../running-the-metabase-jar-file.md | 4 ++--
.../activating-the-enterprise-edition.md | 10 ++++----
docs/paid-features/overview.md | 8 +++----
docs/paid-features/start.md | 8 +++----
docs/people-and-groups/google-and-ldap.md | 8 +++----
docs/people-and-groups/managing.md | 2 +-
docs/people-and-groups/start.md | 2 +-
docs/permissions/collections.md | 2 +-
docs/permissions/introduction.md | 2 +-
docs/questions/sharing/answers.md | 2 +-
docs/questions/sharing/public-links.md | 4 ++--
.../troubleshooting-guide/data-permissions.md | 20 ++++++++--------
docs/troubleshooting-guide/db-performance.md | 2 +-
docs/troubleshooting-guide/loading-from-h2.md | 2 +-
.../my-dashboard-is-slow.md | 2 +-
25 files changed, 68 insertions(+), 75 deletions(-)
diff --git a/docs/api-documentation.md b/docs/api-documentation.md
index 887640accd7..2db464aa0b0 100644
--- a/docs/api-documentation.md
+++ b/docs/api-documentation.md
@@ -25,22 +25,21 @@ Create keys to authenticate programmatic requests to your Metabase. See [API key
## API endpoints
-_* indicates endpoints used for features available on [paid plans](https://www.metabase.com/pricing)._
-
+_\* indicates endpoints used for features available on [Pro and Enterprise](https://www.metabase.com/pricing)._
- [Action](api/action.md)
- [Activity](api/activity.md)
-- [Advanced config logs*](api/ee/advanced-config-logs.md)
-- [Advanced permissions application*](api/ee/advanced-permissions-application.md)
-- [Advanced permissions impersonation*](api/ee/advanced-permissions-impersonation.md)
+- [Advanced config logs\*](api/ee/advanced-config-logs.md)
+- [Advanced permissions application\*](api/ee/advanced-permissions-application.md)
+- [Advanced permissions impersonation\*](api/ee/advanced-permissions-impersonation.md)
- [Alert](api/alert.md)
- [API key](api/api-key.md)
-- [Audit app user*](api/ee/audit-app-user.md)
+- [Audit app user\*](api/ee/audit-app-user.md)
- [Automagic dashboards](api/automagic-dashboards.md)
- [Bookmark](api/bookmark.md)
- [Card](api/card.md)
- [Collection](api/collection.md)
-- [Content verification review*](api/ee/content-verification-review.md)
+- [Content verification review\*](api/ee/content-verification-review.md)
- [Dashboard](api/dashboard.md)
- [Database](api/database.md)
- [Dataset](api/dataset.md)
@@ -62,17 +61,17 @@ _* indicates endpoints used for features available on [paid plans](https://www.m
- [Public](api/public.md)
- [Pulse](api/pulse.md)
- [Revision](api/revision.md)
-- [Sandbox GTAP*](api/ee/sandbox-gtap.md)
-- [Sandbox table*](api/ee/sandbox-table.md)
-- [Sandbox user*](api/ee/sandbox-user.md)
+- [Sandbox GTAP\*](api/ee/sandbox-gtap.md)
+- [Sandbox table\*](api/ee/sandbox-table.md)
+- [Sandbox user\*](api/ee/sandbox-user.md)
- [Search](api/search.md)
- [Segment](api/segment.md)
-- [Serialization*](api/ee/serialization.md)
+- [Serialization\*](api/ee/serialization.md)
- [Session](api/session.md)
- [Setting](api/setting.md)
- [Setup](api/setup.md)
- [Slack](api/slack.md)
-- [SSO*](api/ee/sso.md)
+- [SSO\*](api/ee/sso.md)
- [SSO SAML](api/sso-saml.md)
- [Table](api/table.md)
- [Task](api/task.md)
diff --git a/docs/configuring-metabase/config-file.md b/docs/configuring-metabase/config-file.md
index 74878b79e91..0be4d494bc3 100644
--- a/docs/configuring-metabase/config-file.md
+++ b/docs/configuring-metabase/config-file.md
@@ -6,7 +6,7 @@ title: "Configuration file"
{% include plans-blockquote.html feature="Loading from a configuration file" self-hosted-only="true" %}
-On some paid, self-hosted plans, Metabase supports initialization on launch from a config file named `config.yml`. The config file should be located at:
+On self-hosted Pro and Enterprise plans, Metabase supports initialization on launch from a config file named `config.yml`. The config file should be located at:
- The current directory (the directory where the running Metabase JAR is located).
- The path specified by the `MB_CONFIG_FILE_PATH` [environment variable](./environment-variables.md).
@@ -222,7 +222,7 @@ But you can set any of the Admin settings with the config file. Check out the li
## Loading a new Metabase from a config file
-Since loading from a config file is a paid feature: for new installations, you'll need to supply Metabase with a token using the `MB_PREMIUM_EMBEDDING_TOKEN` environment variable.
+Since loading from a config file is a Pro/Enterprise feature: for new installations, you'll need to supply Metabase with a token using the `MB_PREMIUM_EMBEDDING_TOKEN` environment variable.
```
MB_PREMIUM_EMBEDDING_TOKEN="[your token]" java -jar metabase.jar
diff --git a/docs/configuring-metabase/fonts.md b/docs/configuring-metabase/fonts.md
index 6f749840d1a..ebe55e04225 100644
--- a/docs/configuring-metabase/fonts.md
+++ b/docs/configuring-metabase/fonts.md
@@ -9,7 +9,7 @@ redirect_from:
{% include plans-blockquote.html feature="Customizable font" %}
-On paid plans, you can customize the font Metabase uses (the default is [Lato](https://fonts.google.com/specimen/Lato)). You can choose from a curated set of Google Fonts that accommodate the regular, bold, and heavy font weights that Metabase relies on for its various UI elements.
+On Pro and Enterprise plans, you can customize the font Metabase uses (the default is [Lato](https://fonts.google.com/specimen/Lato)). You can choose from a curated set of Google Fonts that accommodate the regular, bold, and heavy font weights that Metabase relies on for its various UI elements.
## Included fonts
@@ -93,7 +93,6 @@ For latin text, we'd copy the relevant src URLs for each style, in this case:
- For 400: [https://fonts.gstatic.com/s/robotomono/v21/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2](https://fonts.gstatic.com/s/robotomono/v21/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2)
- For 700: [https://fonts.gstatic.com/s/robotomono/v21/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2](https://fonts.gstatic.com/s/robotomono/v21/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2)
-
And paste those URLS in the relevant input fields in **Admin settings** > **Settings** > **Appearance** > **Font** section where it says "Tell us where to find the file for each font weight. You don’t need to include all of them, but it’ll look better if you do."
## Hosting fonts on GitHub
diff --git a/docs/configuring-metabase/setting-up-metabase.md b/docs/configuring-metabase/setting-up-metabase.md
index c6aebc0dd23..c7ce7ab3171 100644
--- a/docs/configuring-metabase/setting-up-metabase.md
+++ b/docs/configuring-metabase/setting-up-metabase.md
@@ -58,7 +58,7 @@ For more on connecting to databases, see [Adding and managing databases](../data
## Activate your license
-If you're self-hosting Metabase on the [Pro](https://www.metabase.com/product/pro) or [Enterprise](https://www.metabase.com/product/enterprise) plan, Metabase will prompt you for your license. This step is just a convenience. You don't need to enter your license here; you can [activate your license](../paid-features/activating-the-enterprise-edition.md) at any time. Just know that all of your paid features won't work until you've activated your license.
+If you're self-hosting Metabase on the [Pro](https://www.metabase.com/product/pro) or [Enterprise](https://www.metabase.com/product/enterprise) plan, Metabase will prompt you for your license. This step is just a convenience. You don't need to enter your license here; you can [activate your license](../paid-features/activating-the-enterprise-edition.md) at any time. Just know that all of your Pro and Enterprise features won't work until you've activated your license.
If you're running Pro on [Metabase Cloud](https://www.metabase.com/cloud), we'll handle this step for you. Your Pro features should already be available.
diff --git a/docs/configuring-metabase/start.md b/docs/configuring-metabase/start.md
index 9f877592fd5..fb6752dcc29 100644
--- a/docs/configuring-metabase/start.md
+++ b/docs/configuring-metabase/start.md
@@ -26,7 +26,7 @@ Configure Metabase on launch via environment variables.
## [Configuration file](./config-file.md)
-On self-hosted paid plans, you can configure Metabase via a configuration file.
+On self-hosted Pro and Enterprise plans, you can configure Metabase via a configuration file.
## [Metabase logs configuration](./log-configuration.md)
diff --git a/docs/databases/connecting.md b/docs/databases/connecting.md
index 54d3763b6f0..b14671dc864 100644
--- a/docs/databases/connecting.md
+++ b/docs/databases/connecting.md
@@ -21,7 +21,7 @@ The connection settings differ database to database. For the list of connection
## Connecting to supported databases
-The databases listed below have official drivers maintained by the Metabase team. Customers on [paid plans](https://www.metabase.com/pricing) will get official support.
+The databases listed below have official drivers maintained by the Metabase team. Customers on [Pro and Enterprise](https://www.metabase.com/pricing) will get official support.
- [Amazon Athena](./connections/athena.md)
- [BigQuery](./connections/bigquery.md) (Google Cloud Platform)
diff --git a/docs/databases/encrypting-details-at-rest.md b/docs/databases/encrypting-details-at-rest.md
index 44a33e7bb88..0ce69fd0c8f 100644
--- a/docs/databases/encrypting-details-at-rest.md
+++ b/docs/databases/encrypting-details-at-rest.md
@@ -12,7 +12,7 @@ Metabase stores connection information for the various databases you add in the
1. Generate a secret key that is at least 16 characters (longer is even better!). We recommend using a secure random key generator, such as `openssl`.
> You cannot decrypt connection details without this key. If you lose (or change) the key, you'll have to reset all of the connection details that have been encrypted with that key in the Admin Panel.
-2. Set your secret key as the environment variable `MB_ENCRYPTION_SECRET_KEY`. On paid plans, you can set also set this using the [config file](../configuring-metabase/config-file.md).
+2. Set your secret key as the environment variable `MB_ENCRYPTION_SECRET_KEY`. On self-hosted [Pro and Enterprise plans](https://www.metabase.com/pricing/) plans, you can set also set this using the [config file](../configuring-metabase/config-file.md).
### Example commands for creating and adding a key
diff --git a/docs/embedding/interactive-embedding.md b/docs/embedding/interactive-embedding.md
index 761af3018f5..b622ab5eed9 100644
--- a/docs/embedding/interactive-embedding.md
+++ b/docs/embedding/interactive-embedding.md
@@ -25,7 +25,7 @@ Check out the [Interactive embedding quick start](https://www.metabase.com/learn
## Prerequisites for interactive embedding
-1. Make sure you have a [license token](../paid-features/activating-the-enterprise-edition.md) for a [paid plan](https://store.metabase.com/checkout/login-details).
+1. Make sure you have a [license token](../paid-features/activating-the-enterprise-edition.md) for a [Pro or Enterprise plan](https://store.metabase.com/checkout/login-details).
2. Organize people into Metabase [groups](../people-and-groups/start.md).
3. Set up [permissions](../permissions/introduction.md) for each group.
4. Set up [SSO](../people-and-groups/start.md#authentication) to automatically apply permissions and show people the right data upon sign-in. In general, **we recommend using [SSO with JWT](../people-and-groups/authenticating-with-jwt.md)**.
diff --git a/docs/installation-and-operation/running-metabase-on-docker.md b/docs/installation-and-operation/running-metabase-on-docker.md
index ed8ca2db7b2..aa68aba27ec 100644
--- a/docs/installation-and-operation/running-metabase-on-docker.md
+++ b/docs/installation-and-operation/running-metabase-on-docker.md
@@ -44,7 +44,7 @@ docker run -d -p 12345:3000 --name metabase metabase/metabase
## Pro or Enterprise quick start
-Use this quick start if you have a [license token](../paid-features/activating-the-enterprise-edition.md) for a [paid version](https://www.metabase.com/pricing) of Metabase, and you want to run Metabase locally. See below for instructions on [running Metabase in production](#production-installation).
+Use this quick start if you have a [license token](../paid-features/activating-the-enterprise-edition.md) for a [Pro or Enterprise version](https://www.metabase.com/pricing) of Metabase, and you want to run Metabase locally. See below for instructions on [running Metabase in production](#production-installation).
Assuming you have [Docker](https://www.docker.com/) installed and running, get the latest Docker image:
@@ -92,7 +92,6 @@ createdb metabaseappdb
No need to add any tables; Metabase will create those on startup. And let's assume that database is accessible via `my-database-host:5432` with username `name` and password `password`.
-
Here's an example Docker command that tells Metabase to use that database:
```
@@ -117,14 +116,14 @@ If you've already been running Metabase with the default application database (H
Here's an example `docker-compose.yml` file for running Metabase with a PostgreSQL database `metabaseappdb`:
```yml
-version: '3.9'
+version: "3.9"
services:
metabase:
image: metabase/metabase:latest
container_name: metabase
hostname: metabase
volumes:
- - /dev/urandom:/dev/random:ro
+ - /dev/urandom:/dev/random:ro
ports:
- 3000:3000
environment:
@@ -280,14 +279,14 @@ These files should be in the same directory as the `docker-compose.yml`. Put the
Notice the "\_FILE" on the environment variables that have a secret:
```yml
-version: '3.9'
+version: "3.9"
services:
metabase:
image: metabase/metabase:latest
container_name: metabase
hostname: metabase
volumes:
- - /dev/urandom:/dev/random:ro
+ - /dev/urandom:/dev/random:ro
ports:
- 3000:3000
environment:
@@ -324,10 +323,10 @@ networks:
metanet1:
driver: bridge
secrets:
- db_password:
- file: db_password.txt
- db_user:
- file: db_user.txt
+ db_password:
+ file: db_password.txt
+ db_user:
+ file: db_user.txt
```
We currently support the following [environment variables](../configuring-metabase/environment-variables.md) to be used as secrets:
diff --git a/docs/installation-and-operation/running-metabase-on-podman.md b/docs/installation-and-operation/running-metabase-on-podman.md
index 2f017f04746..7d83c316ad3 100644
--- a/docs/installation-and-operation/running-metabase-on-podman.md
+++ b/docs/installation-and-operation/running-metabase-on-podman.md
@@ -40,7 +40,7 @@ podman run -d -p 12345:3000 --name=metabase docker.io/metabase/metabase:latest
## Pro or Enterprise quick start
-Use this quick start if you have a [license token](../paid-features/activating-the-enterprise-edition.md) for a [paid version](https://www.metabase.com/pricing) of Metabase, and you want to run Metabase locally.
+Use this quick start if you have a [license token](../paid-features/activating-the-enterprise-edition.md) for a [Pro or Enterprise version](https://www.metabase.com/pricing) of Metabase, and you want to run Metabase locally.
Assuming you have [Podman](https://podman.io) installed and running, get the latest container image:
@@ -88,7 +88,6 @@ createdb metabaseappdb
No need to add any tables; Metabase will create those on startup. And let's assume that database is accessible via `my-database-host:5432` with username `name` and password `password`.
-
Here's an example Podman command that tells Metabase to use that database:
```
@@ -110,7 +109,6 @@ If you've already been running Metabase with the default application database (H
## Additional Podman maintenance and configuration
-
- [Running Metabase as a service](#running-metabase-as-a-service)
- [Customizing the Metabase Jetty server](#customizing-the-metabase-jetty-server)
- [Setting the Java Timezone](#setting-the-java-timezone)
@@ -139,12 +137,10 @@ sudo systemctl enable metabase
To verify that the system functions correctly, reboot the system. Upon completion of the system initialization process, the Metabase container should be operational as intended.
-
### Customizing the Metabase Jetty server
You can use any of the custom settings from [Customizing the Metabase Jetty Webserver](../configuring-metabase/customizing-jetty-webserver.md) by setting environment variables in your Podman run command.
-
### Setting the Java Timezone
It's best to set your Java timezone to match the timezone you'd like all your reports to come in. You can do this by simply specifying the `JAVA_TIMEZONE` environment variable which is picked up by the Metabase launch script. For example:
diff --git a/docs/installation-and-operation/running-the-metabase-jar-file.md b/docs/installation-and-operation/running-the-metabase-jar-file.md
index bb9ae6a7e5d..0dae6a0232f 100644
--- a/docs/installation-and-operation/running-the-metabase-jar-file.md
+++ b/docs/installation-and-operation/running-the-metabase-jar-file.md
@@ -27,7 +27,7 @@ java -jar metabase.jar
Metabase will log its progress in the terminal as it starts up. Wait until you see "Metabase Initialization Complete" and visit `http://localhost:3000/setup`.
-If you are using a paid version, be sure to [activate your license](../paid-features/activating-the-enterprise-edition.md).
+If you are using a Pro or Enterprise version, be sure to [activate your license](../paid-features/activating-the-enterprise-edition.md).
## Local installation
@@ -103,7 +103,7 @@ At this point you're ready to go! You can access your new Metabase server on por
You can use another port than 3000 by setting the `MB_JETTY_PORT` [environment variable](../configuring-metabase/environment-variables.md) before running the jar.
-If you are using a paid version of Metabase, be sure to [activate your license](../paid-features/activating-the-enterprise-edition.md).
+If you are using a Pro or Enterprise version of Metabase, be sure to [activate your license](../paid-features/activating-the-enterprise-edition.md).
## Production installation
diff --git a/docs/paid-features/activating-the-enterprise-edition.md b/docs/paid-features/activating-the-enterprise-edition.md
index f13811f908e..380b7b43739 100644
--- a/docs/paid-features/activating-the-enterprise-edition.md
+++ b/docs/paid-features/activating-the-enterprise-edition.md
@@ -6,13 +6,13 @@ redirect_from:
# Activating your Metabase commercial license
-The [paid Pro and Enterprise editions](https://www.metabase.com/pricing) of Metabase are distinct from the free [Open Source edition](../installation-and-operation/running-the-metabase-jar-file.md).
+The [paid Pro and Enterprise editions](https://www.metabase.com/pricing) of Metabase are distinct from the free [Open Source edition](../installation-and-operation/running-the-metabase-jar-file.md) and the [Starter version of Metabase Cloud](https://www.metabase.com/cloud/).
-To use your paid features you’ll need to first get a license. And if you want to self-host, you'll need a different JAR or Docker image that you can use to activate the advanced features with your license token.
+To use your Pro/Enterprise features, you’ll need to first get a license. And if you want to self-host, you'll need a different JAR or Docker image that you can use to activate the advanced features with your license token.
## If you're running on Metabase Cloud
-If you've signed up for or upgraded to a premium plan on Metabase Cloud, all of this will be taken care of for you.
+If you've signed up for or upgraded to a Pro or Enterprise plan on Metabase Cloud, all of this will be taken care of for you.
## Where to get a license
@@ -31,7 +31,7 @@ Run Metabase as you would normally, then go to **Settings** > **Admin settings**
## **Validating your token**
-To validate your token and maintain access to paid features, your Metabase needs to be able to access the Internet, specifically:
+To validate your token and maintain access to Pro/Enterprise features, your Metabase needs to be able to access the Internet, specifically:
```
https://token-check.metabase.com/api/[token-id]/v2/status
@@ -39,7 +39,7 @@ https://token-check.metabase.com/api/[token-id]/v2/status
(substituting `[token-id]` with your token ID).
-If your Metabase can't validate the token, it'll disable the paid features, but will continue to work normally as if you were running the Open Source edition.
+If your Metabase can't validate the token, it'll disable the Pro/Enterprise features, but will continue to work normally as if you were running the Open Source edition.
## Routing outbound Metabase traffic through a proxy
diff --git a/docs/paid-features/overview.md b/docs/paid-features/overview.md
index b1f195fda4e..bd0394b19d8 100644
--- a/docs/paid-features/overview.md
+++ b/docs/paid-features/overview.md
@@ -8,12 +8,12 @@ redirect_from:
Metabase's [Enterprise and Pro](https://www.metabase.com/pricing) plans provide additional features that help organizations scale Metabase and deliver self-service internal or embedded analytics.
-- **If you're on Metabase Cloud**, your paid features will activate automatically.
+- **If you're on Metabase Cloud**, your Pro/Enterprise features will activate automatically.
- **If you're self-hosting,** you'll need to [activate your license](./activating-the-enterprise-edition.md).
## Authentication
-Paid plans include more ways to authenticate people and manage groups.
+Pro and Enterprise plans include more ways to authenticate people and manage groups.
- [Authenticating with SAML](../people-and-groups/authenticating-with-saml.md)
- [Setting up SAML with Auth0](../people-and-groups/saml-auth0.md)
@@ -26,7 +26,7 @@ Paid plans include more ways to authenticate people and manage groups.
## Permissions
-Paid plans include more ways to manage permissions, including data sandboxing, which brings row and column-level permissions to Metabase.
+Pro and Enterprise plans include more ways to manage permissions, including data sandboxing, which brings row and column-level permissions to Metabase.
- [Data sandboxes](../permissions/data-sandboxes.md)
- [Blocked view data permissions](../permissions/data.md#blocked-view-data-permission)
@@ -77,7 +77,7 @@ Tools for keeping your Metabase organized, so people can find your most importan
## Advanced caching controls
-All Metabase editions include global caching controls. Paid plans includes additional caching options that let you control caching for individual questions.
+All Metabase editions include global caching controls. Pro and Enterprise plans includes additional caching options that let you control caching for individual questions.
- [Caching questions](../configuring-metabase/caching.md#question-caching-policy)
- [Caching dashboards](../configuring-metabase/caching.md#dashboard-caching-policy)
diff --git a/docs/paid-features/start.md b/docs/paid-features/start.md
index 6e8f03a767d..1a7565d3a45 100644
--- a/docs/paid-features/start.md
+++ b/docs/paid-features/start.md
@@ -4,17 +4,17 @@ title: Paid features
# Paid features
-Some [Metabase plans](https://www.metabase.com/pricing) offer additional features to help organizations manage lots of people asking lots of questions.
+[Metabase Pro and Enterprise plans](https://www.metabase.com/pricing) offer additional features to help organizations manage lots of people asking lots of questions.
- [Metabase Pro](https://www.metabase.com/product/pro)
- [Metabase Enterprise Edition](https://www.metabase.com/product/enterprise)
-Much of the documentation for these features is grouped with relevant feature clusters, so this section is meant to be more of an index of all the cool tools you get on these paid plans.
+Much of the documentation for these features is grouped with relevant feature clusters, so this section is meant to be more of an index of all the cool tools you get on these plans.
## [List of premium features](./overview.md)
-What you get when you're one of our premium plans.
+What you get when you're one of our Pro or Enterprise plans.
## [Activating the enterprise edition](./activating-the-enterprise-edition.md)
-If you're self-hosting the Enterprise Edition, you'll need to plug in your license to access your paid features.
+If you're self-hosting the Enterprise Edition, you'll need to plug in your license to access your Pro/Enterprise features.
diff --git a/docs/people-and-groups/google-and-ldap.md b/docs/people-and-groups/google-and-ldap.md
index 39d44d00731..2d46a91c2ff 100644
--- a/docs/people-and-groups/google-and-ldap.md
+++ b/docs/people-and-groups/google-and-ldap.md
@@ -8,7 +8,7 @@ redirect_from:
Enabling [Google Sign-In](https://developers.google.com/identity/sign-in/web/sign-in) or [LDAP](https://www.metabase.com/glossary/ldap) for single sign-on (SSO) lets your team log in with a click instead of using email and password. SSO can also be used to let people create Metabase accounts without asking an admin to add each person manually. You can find SSO options under **Settings** > **Admin settings** > **Authentication**.
-If you'd like to have people authenticate with [SAML][saml-docs] or [JWT][jwt-docs], Metabase's [paid plans](https://www.metabase.com/pricing) let you do just that. As time goes on we may add other auth providers. If you have a service you’d like to see work with Metabase, please let us know by [filing an issue](http://github.com/metabase/metabase/issues/new).
+If you'd like to have people authenticate with [SAML][saml-docs] or [JWT][jwt-docs], Metabase's [Pro and Enterprise](https://www.metabase.com/pricing) let you do just that. As time goes on we may add other auth providers. If you have a service you’d like to see work with Metabase, please let us know by [filing an issue](http://github.com/metabase/metabase/issues/new).
## Enabling Google Sign-In
@@ -135,12 +135,12 @@ User attributes can't be synced with regular Google Sign-In. You'll need to set
{% include plans-blockquote.html feature="Disabling password logins" %}
-On paid plans, you can require people to log in with SSO by disabling password authentication from **Admin settings** > **Authentication**.
+On Pro and Enterprise plans, you can require people to log in with SSO by disabling password authentication from **Admin settings** > **Authentication**.
## Troubleshooting login issues
- - [Can't log in](../troubleshooting-guide/cant-log-in.md).
- - [Troubleshooting LDAP](../troubleshooting-guide/ldap.md)
+- [Can't log in](../troubleshooting-guide/cant-log-in.md).
+- [Troubleshooting LDAP](../troubleshooting-guide/ldap.md)
## Further reading
diff --git a/docs/people-and-groups/managing.md b/docs/people-and-groups/managing.md
index 5fe896a4c5c..5ef7c776172 100644
--- a/docs/people-and-groups/managing.md
+++ b/docs/people-and-groups/managing.md
@@ -20,7 +20,7 @@ Click on the **gear** icon > **Admin settings** > **People**. You'll see a list
To add a new person, click **Invite someone** in the upper right corner. You’ll be prompted to enter their email, and optionally their first and last names–only the email is required.
-Click **Create** to activate an account. An account becomes active once you click **Create**, even if the person never signs into the account. The account remains active until you [deactivate the account](#deactivating-an-account). If you're on a paid Metabase plan, all active accounts will count toward your user account total. If one person has more than one account, each account will count toward the total (see [how billing works](https://www.metabase.com/pricing/how-billing-works)).
+Click **Create** to activate an account. An account becomes active once you click **Create**, even if the person never signs into the account. The account remains active until you [deactivate the account](#deactivating-an-account). If you're on a Pro or Enterprise Metabase plan, all active accounts will count toward your user account total. If one person has more than one account, each account will count toward the total (see [how billing works](https://www.metabase.com/pricing/how-billing-works)).
If you’ve already [configured Metabase to use email](../configuring-metabase/email.md), Metabase will send the person an email inviting them to log into Metabase. If you haven't yet setup email for your Metabase, Metabase will give you a temporary password that you’ll have to manually send to the person.
diff --git a/docs/people-and-groups/start.md b/docs/people-and-groups/start.md
index 3738975212d..121e13da960 100644
--- a/docs/people-and-groups/start.md
+++ b/docs/people-and-groups/start.md
@@ -37,7 +37,7 @@ Metabase offers several options for single sign-on (SSO) authentication.
### SSO for Metabase Pro and Enterprise plans
-With some paid plans, you have more options to help orchestrate lots of people and groups.
+With [Pro and Enterprise plans](https://www.metabase.com/pricing/), you have more options to help orchestrate lots of people and groups.
- [JWT][jwt]
- LDAP advanced features
diff --git a/docs/permissions/collections.md b/docs/permissions/collections.md
index 02c37871135..eb749900372 100644
--- a/docs/permissions/collections.md
+++ b/docs/permissions/collections.md
@@ -86,7 +86,7 @@ People in groups with Curate access to a collection can pin items in the collect
To pin an item, select the **pin icon** next to the item's name.
-Note that collections themselves can't be pinned. If you're running on a [paid plan](https://www.metabase.com/pricing), admins can designate [Offical Collections][offical-collections].
+Note that collections themselves can't be pinned. If you're running on a [Pro or Enterprise plan](https://www.metabase.com/pricing), admins can designate [Official Collections][offical-collections].
## Special collections
diff --git a/docs/permissions/introduction.md b/docs/permissions/introduction.md
index 54f645299ce..48b6a7c9b26 100644
--- a/docs/permissions/introduction.md
+++ b/docs/permissions/introduction.md
@@ -44,7 +44,7 @@ If instead you're wondering about what data Metabase the company can see, check
### Application permissions
-[Application permissions](application.md) (available on paid plans) dictate access to Metabase application-level features, including:
+[Application permissions](application.md) (available on [Pro and Enterprise plans](https://www.metabase.com/pricing/)) dictate access to Metabase application-level features, including:
- **Settings**: The Settings tab in the Admin panel.
- **Monitoring access**: The Tools and Troubleshooting tabs in the Admin panel.
diff --git a/docs/questions/sharing/answers.md b/docs/questions/sharing/answers.md
index 1ab2a7fda8e..5045c15e52c 100644
--- a/docs/questions/sharing/answers.md
+++ b/docs/questions/sharing/answers.md
@@ -56,7 +56,7 @@ Click the **info** icon to:
- Edit the [cache duration](../../configuring-metabase/caching.md#question-caching-policy)\*
- View [revision history](../../exploration-and-organization/history.md)
-\* Available on [paid plans](https://www.metabase.com/pricing/).
+\* Available on [Pro and Enterprise plans](https://www.metabase.com/pricing/).
## Bookmark a question
diff --git a/docs/questions/sharing/public-links.md b/docs/questions/sharing/public-links.md
index 1fbe404f59a..7592df3992b 100644
--- a/docs/questions/sharing/public-links.md
+++ b/docs/questions/sharing/public-links.md
@@ -107,9 +107,9 @@ To toggle appearance settings, add _hash_ parameters to the end of the public li
| font¹ | [font name](../../configuring-metabase/fonts.md) |
| hide_download_button² | true, false |
-¹ Available on [paid plans](https://www.metabase.com/pricing).
+¹ Available on [Pro and Enterprise plans](https://www.metabase.com/pricing).
-² Available on [paid plans](https://www.metabase.com/pricing) and hides the download button on questions only (not dashboards).
+² Available on [Pro and Enterprise plans](https://www.metabase.com/pricing) and hides the download button on questions only (not dashboards).
For example, to embed a dashboard with multiple appearance parameters:
diff --git a/docs/troubleshooting-guide/data-permissions.md b/docs/troubleshooting-guide/data-permissions.md
index 7ecacf972e2..97a03f25482 100644
--- a/docs/troubleshooting-guide/data-permissions.md
+++ b/docs/troubleshooting-guide/data-permissions.md
@@ -27,7 +27,7 @@ If a person has the wrong level of access to the data that's returned by a quest
1. Ensure scripts are loading by disabling browser extensions and refreshing the browser.
2. Go to **Admin** > **Permissions** and select the relevant group.
3. Find the database that you want to grant SQL access to.
-4. From the **View data** dropdown.elect **Can view**.
+4. From the **View data** dropdown.elect **Can view**.
5. From the **Create queries** dropdown, select **Query builder and native**.
6. [Check if the access problem is fixed](#checking-someones-access-to-a-table-or-schema).
@@ -37,8 +37,8 @@ For more information about the different types of database permissions, check ou
1. Go to **Admin** > **People** and check if the person is in [more than one group with conflicting permissions][group-permissions].
2. If the person is in multiple groups:
- - Remove the person from the group with wider permissions, or
- - Go to **Admin** > **Permissions** and change the **Data access** permission type.
+ - Remove the person from the group with wider permissions, or
+ - Go to **Admin** > **Permissions** and change the **Data access** permission type.
3. [Check if the access problem is fixed](#checking-someones-access-to-a-table-or-schema).
**Explanation**
@@ -62,22 +62,22 @@ Remember that everyone is a member of the **All Users** group. We recommend you
If you've granted a group View data access of "Can view" to a database or table, people can view saved questions and dashboards that draw on that database, as long as those questions and dashboards are stored in a collection that they have access to.
-The [**Blocked** data permission][block-data-permission] is available on [paid versions of Metabase][pricing]. If you block a group's access to a database, members of that group will not be able to see any data from this database, regardless of their collection permissions.
+The [**Blocked** data permission][block-data-permission] is available on [Pro and Enterprise versions of Metabase][pricing]. If you block a group's access to a database, members of that group will not be able to see any data from this database, regardless of their collection permissions.
## Getting a "permission denied" error message
If you get an error message that says something like "permission denied to \<your table\>", you'll need to check if the Metabase application has the correct permissions to query your database.
1. Go to the SQL editor and run a basic query against the table or schema in question:
- ```
- SELECT 1
- FROM <your table>;
- ```
+ ```
+ SELECT 1
+ FROM <your table>;
+ ```
2. Get the credentials that Metabase uses to connect to your database. If you're not sure what those credentials are, ask your database admin.
3. Using a different application (like your CLI or database IDE), connect to your database using the same credentials your Metabase uses to connect to that database, and run the query from step 1.
4. If you cannot access the table or schema in both step 1 and 3, ask your database admin to:
- - [Grant database privileges](../databases/users-roles-privileges.md) to the role that Metabase is using to connect, or
- - Provide a set of database credentials with the correct permissions.
+ - [Grant database privileges](../databases/users-roles-privileges.md) to the role that Metabase is using to connect, or
+ - Provide a set of database credentials with the correct permissions.
5. [Check if the access problem is fixed](#checking-someones-access-to-a-table-or-schema).
**Explanation**
diff --git a/docs/troubleshooting-guide/db-performance.md b/docs/troubleshooting-guide/db-performance.md
index 5b16da3e41e..b2f31877c51 100644
--- a/docs/troubleshooting-guide/db-performance.md
+++ b/docs/troubleshooting-guide/db-performance.md
@@ -28,7 +28,7 @@ To fix problems with your Metabase [application database](../installation-and-op
- Stop your script or application, and [clear any queued queries](#clearing-queued-queries).
- Recommended: add a timeout to your script, schedule the script or application to run during off-hours, or replicate your database (and point your tools there instead).
-\* Available on paid plans.
+\* Available on Pro and Enterprise plans.
## Resetting a database connection
diff --git a/docs/troubleshooting-guide/loading-from-h2.md b/docs/troubleshooting-guide/loading-from-h2.md
index 37f803ff2f7..949d2829122 100644
--- a/docs/troubleshooting-guide/loading-from-h2.md
+++ b/docs/troubleshooting-guide/loading-from-h2.md
@@ -47,7 +47,7 @@ Command failed with exception: Unsupported database file version or invalid file
java -jar metabase.jar load-from-h2 /path/to/metabase.db # do not include .mv.db
```
-If you're using a [paid version of Metabase][enterprise], you can use [serialization][serialization-docs] to snapshot your application database. Serialization is useful when you want to [preload questions and dashboards][serialization-learn] in a new Metabase instance.
+If you're using a [Pro or Enterprise version of Metabase][enterprise], you can use [serialization][serialization-docs] to snapshot your application database. Serialization is useful when you want to [preload questions and dashboards][serialization-learn] in a new Metabase instance.
## Are you trying to downgrade?
diff --git a/docs/troubleshooting-guide/my-dashboard-is-slow.md b/docs/troubleshooting-guide/my-dashboard-is-slow.md
index d35f05670f6..305dbadc15a 100644
--- a/docs/troubleshooting-guide/my-dashboard-is-slow.md
+++ b/docs/troubleshooting-guide/my-dashboard-is-slow.md
@@ -28,7 +28,7 @@ Aside from running faster, a small and focused dashboard is also easier for peop
2. Set up [caching](../configuring-metabase/caching.md) for the questions on your popular dashboard.
3. Run the dashboard during off-hours so that people can load the cached results in seconds instead of executing a fresh query to your database.
-\* Available on paid plans.
+\* Available on Pro and Enterprise plans.
**Explanation**
--
GitLab