diff --git a/_docs/latest/developers-guide/e2e-tests.md b/_docs/latest/developers-guide/e2e-tests.md
index a2c61214cd..aff410c041 100644
--- a/_docs/latest/developers-guide/e2e-tests.md
+++ b/_docs/latest/developers-guide/e2e-tests.md
@@ -266,15 +266,17 @@ Prior to running Cypress against Metabase® Enterprise Edition™, set `MB_EDITI
**Enterprise instance will start without a premium token!**
-If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests. We achieve this by prefixing environment variables with `CYPRESS_`.
-You should provide two tokens that correspond to the `EE/PRO` self-hosted (all features enabled) and `STARTER` Cloud (no features enabled) Metabase plans. For more information, please see [Metabase pricing page](/pricing/). (note: only a few tests require the no features token)
+If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests.
+You should provide 4 tokens:
-- `CYPRESS_ALL_FEATURES_TOKEN`
-- `CYPRESS_NO_FEATURES_TOKEN`
+- MB_ALL_FEATURES_TOKEN: all feature enabled, including new feature not released yet to customers
+- MB_STARTER_CLOUD_TOKEN: only 'hosting' feature enabled to simulate the starter plan on cloud
+- MB_PRO_CLOUD_TOKEN: PRO features enabled + 'hosting' to simulate the pro plan on cloud
+- MB_PRO_SELF_HOSTED_TOKEN: PRO features but no 'hosting' to simulate the pro self-hosted plan
-```
-MB_EDITION=ee ENTERPRISE_TOKEN=xxxxxx yarn test-cypress
-```
+You can configure these via ENVs or via the `cypress.env.json` file (see `cypress.env.json.example` for an example).
+
+For more information, please see [Metabase pricing page](/pricing/).
If you navigate to the `/admin/settings/license` page, the license input field should display the active token. Be careful when sharing screenshots!
diff --git a/_docs/v0.55/developers-guide/e2e-tests.md b/_docs/v0.55/developers-guide/e2e-tests.md
index 4e294acaf6..714050b06d 100644
--- a/_docs/v0.55/developers-guide/e2e-tests.md
+++ b/_docs/v0.55/developers-guide/e2e-tests.md
@@ -264,15 +264,17 @@ Prior to running Cypress against Metabase® Enterprise Edition™, set `MB_EDITI
**Enterprise instance will start without a premium token!**
-If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests. We achieve this by prefixing environment variables with `CYPRESS_`.
-You should provide two tokens that correspond to the `EE/PRO` self-hosted (all features enabled) and `STARTER` Cloud (no features enabled) Metabase plans. For more information, please see [Metabase pricing page](/pricing/). (note: only a few tests require the no features token)
+If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests.
+You should provide 4 tokens:
-- `CYPRESS_ALL_FEATURES_TOKEN`
-- `CYPRESS_NO_FEATURES_TOKEN`
+- MB_ALL_FEATURES_TOKEN: all feature enabled, including new feature not released yet to customers
+- MB_STARTER_CLOUD_TOKEN: only 'hosting' feature enabled to simulate the starter plan on cloud
+- MB_PRO_CLOUD_TOKEN: PRO features enabled + 'hosting' to simulate the pro plan on cloud
+- MB_PRO_SELF_HOSTED_TOKEN: PRO features but no 'hosting' to simulate the pro self-hosted plan
-```
-MB_EDITION=ee ENTERPRISE_TOKEN=xxxxxx yarn test-cypress
-```
+You can configure these via ENVs or via the `cypress.env.json` file (see `cypress.env.json.example` for an example).
+
+For more information, please see [Metabase pricing page](/pricing/).
If you navigate to the `/admin/settings/license` page, the license input field should display the active token. Be careful when sharing screenshots!
diff --git a/_site/docs/latest/developers-guide/e2e-tests.html b/_site/docs/latest/developers-guide/e2e-tests.html
index 1e3e043c18..cd0327b08b 100644
--- a/_site/docs/latest/developers-guide/e2e-tests.html
+++ b/_site/docs/latest/developers-guide/e2e-tests.html
@@ -5043,16 +5043,19 @@ Enterprise instance will start without a premium token!
-If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests. We achieve this by prefixing environment variables with CYPRESS_.
-You should provide two tokens that correspond to the EE/PRO self-hosted (all features enabled) and STARTER Cloud (no features enabled) Metabase plans. For more information, please see Metabase pricing page. (note: only a few tests require the no features token)
+If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests.
+You should provide 4 tokens:
- CYPRESS_ALL_FEATURES_TOKENCYPRESS_NO_FEATURES_TOKEN- MB_ALL_FEATURES_TOKEN: all feature enabled, including new feature not released yet to customers
+ - MB_STARTER_CLOUD_TOKEN: only ‘hosting’ feature enabled to simulate the starter plan on cloud
+ - MB_PRO_CLOUD_TOKEN: PRO features enabled + ‘hosting’ to simulate the pro plan on cloud
+ - MB_PRO_SELF_HOSTED_TOKEN: PRO features but no ‘hosting’ to simulate the pro self-hosted plan
-MB_EDITION=ee ENTERPRISE_TOKEN=xxxxxx yarn test-cypress
-
You can configure these via ENVs or via the cypress.env.json file (see cypress.env.json.example for an example).
+
+For more information, please see Metabase pricing page.
If you navigate to the /admin/settings/license page, the license input field should display the active token. Be careful when sharing screenshots!
diff --git a/_site/docs/v0.55/developers-guide/e2e-tests.html b/_site/docs/v0.55/developers-guide/e2e-tests.html
index dcc4992da7..9f2bb74038 100644
--- a/_site/docs/v0.55/developers-guide/e2e-tests.html
+++ b/_site/docs/v0.55/developers-guide/e2e-tests.html
@@ -5045,16 +5045,19 @@ Enterprise instance will start without a premium token!
-If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests. We achieve this by prefixing environment variables with CYPRESS_.
-You should provide two tokens that correspond to the EE/PRO self-hosted (all features enabled) and STARTER Cloud (no features enabled) Metabase plans. For more information, please see Metabase pricing page. (note: only a few tests require the no features token)
+If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests.
+You should provide 4 tokens:
- CYPRESS_ALL_FEATURES_TOKENCYPRESS_NO_FEATURES_TOKEN- MB_ALL_FEATURES_TOKEN: all feature enabled, including new feature not released yet to customers
+ - MB_STARTER_CLOUD_TOKEN: only ‘hosting’ feature enabled to simulate the starter plan on cloud
+ - MB_PRO_CLOUD_TOKEN: PRO features enabled + ‘hosting’ to simulate the pro plan on cloud
+ - MB_PRO_SELF_HOSTED_TOKEN: PRO features but no ‘hosting’ to simulate the pro self-hosted plan
-MB_EDITION=ee ENTERPRISE_TOKEN=xxxxxx yarn test-cypress
-
You can configure these via ENVs or via the cypress.env.json file (see cypress.env.json.example for an example).
+
+For more information, please see Metabase pricing page.
If you navigate to the /admin/settings/license page, the license input field should display the active token. Be careful when sharing screenshots!