diff --git a/src/content/docs/build/environments/environments.mdx b/src/content/docs/build/environments/environments.mdx
index 41db4a24b..06a866628 100644
--- a/src/content/docs/build/environments/environments.mdx
+++ b/src/content/docs/build/environments/environments.mdx
@@ -1,9 +1,12 @@
---
page_id: d95a8edd-f61a-4095-a80e-ffd67f90a438
-title: About environments
+title: Manage Kinde environments
description: Overview of Kinde environments including production and non-production environments, environment management, rate limiting considerations, and development workflow best practices.
sidebar:
order: 1
+ label: Manage environments
+tableOfContents:
+ maxHeadingLevel: 3
app_context:
- m: settings
s: environment_details
@@ -12,6 +15,11 @@ topics:
- environments
- development
- production
+ - staging
+ - testing
+ - environment management
+ - environment switching
+ - environment settings
sdk: []
languages: []
audience: developers
@@ -19,74 +27,101 @@ complexity: beginner
keywords:
- environments
- production environment
- - non-production
- - staging
- - testing
+ - non-production environment
+ - staging environment
+ - testing environment
- environment management
- - rate limiting
-updated: 2024-01-15
+ - create environment
+ - delete environment
+ - rename environment
+ - environment settings
+ - environment switcher
+ - switch environment
+ - dev environment
+updated: 2026-05-27
featured: false
deprecated: false
-ai_summary: Overview of Kinde environments including production and non-production environments, environment management, rate limiting considerations, and development workflow best practices.
+ai_summary: "Kinde supports multiple environments to match your software development workflow. Every Kinde business includes one production environment by default. You can create additional non-production environments — such as dev, test, or staging — on a paid plan. Use the environment switcher in the top-left of the dashboard to switch between environments or access environment settings. You can create, rename, delete (non-production only), and configure environment settings including analytics integrations. The production environment cannot be deleted and must go through the go-live checklist to be set to live. Currently, there is no built-in way to copy configuration between environments, but a separate guide covers how to manage this."
---
-Kinde allows you to run multiple environments to support your software development cycle. All plans come with one production environment and one non-production environment. Higher plans come with additional non-production environments, so you can add staging, testing, beta, etc. to meet your team’s needs.
+Kinde allows you to run multiple environments to support your software development cycle.
-
+You can see the environment you are working in at the top left of the home page when signed in. To make the production environment live, [follow the go-live checklist](/build/environments/production-to-live/).
-You can see the environment you are working in at the top left of the home page when signed in.
+## Manage environments
-## Take care using multiple environments
+### Environment switcher
-Unless you are a developer, we recommend you stay in the production environment for viewing and working with your Kinde account.
+
+
+1. Sign in to your Kinde dashboard.
+2. On the top left of the screen, you will see the environment you are currently in.
+3. Select the environment drop-down to:
+ - Switch to another environment
+ - View all your environments (and create additional ones)
+ - View and edit the current environment settings
-For developers who want to test new user configurations or make other changes, do this in a non-production (testing or staging) environment first, before replicating in the production environment.
+### Create a new environment
-## Rate limiting for live production environments
+
-Before you make your production environment live, [follow ](/build/environments/production-to-live/)[this checklist](/build/environments/production-to-live/).
+1. From the environment drop-down, select **All environments**.
+2. In the **Environments** page, select **Add environment**.
+3. Enter a name for the environment (e.g., Development).
+4. Enter a dev-friendly code for the environment (e.g., `dev`).
+5. Select **Save**.
-It is critical that all [third-party authentication](/authenticate/authentication-methods/set-up-user-authentication/) connections (such as social connections or enterprise connections) are set up with the third-party’s Client ID and Client secret. If you leave these fields blank during setup, Kinde’s credentials will be used as a proxy, and rate limits will apply.
+ You will see the new environment in the list.
-Note that you can leave these fields blank in your non-production environments. Non-production environments cannot be made live.
+
-## View and manage environments
+6. Select **Switch to this environment** on the environment card to start working in the new environment.
-Select the environment drop-down in the top left of the home screen. From here you can:
-- Switch to another environment
-- View all your environments (and create additional ones)
-- View environment settings
+### Rename an environment
-## Add an environment
+1. From the environment drop-down, select **All environments**.
+2. On the environment you want to rename, select the **three dots menu** (...).
+3. Select **Edit environment**.
+4. Update the environment name and select **Save**.
-You can only add non-production environments.
+### Delete a non-production environment
-1. Select the environment drop-down in the top left of the home screen, and select **All environments**.
-2. On the **Environments** page, select **Add environment**.
-3. Enter a name and code for the environment, then select **Save**.
+1. From the environment drop-down, select **All environments**.
+2. On the environment you want to delete, select the **three dots menu** (...).
+3. Select **Delete environment**.
+4. Confirm you want to delete the environment. This action is irreversible.
-## Switch between environments
+
-Select the environment drop-down in the top left of the home screen, and select the environment you want to switch to.
+### Update environment settings
-## Change the name of an environment
+1. From the environment drop-down, select **Environment settings**.
+2. Update the environment name as needed.
+3. Optionally, add third-party analytics tracking codes such as Google Analytics, Hotjar, and Contentsquare.
-1. Switch to the environment you want.
-2. Select the environment drop-down in the top left of the home screen and choose **Environment settings**.
-3. Change the environment name and select **Save**.
+ If you are editing the production environment, you can also update the environment status to **Live**. See the [go live checklist](/build/environments/production-to-live/) for more details.
-## Delete a non-production environment
+## Kinde environment FAQs
-You cannot delete the production environment.
+### Who should use multiple environments?
-1. Select the environment drop-down in the top left of the home screen, and select **All environments**.
-2. On the environment you want to delete select the three dots, then select **Delete environment**.
-3. Confirm you want to delete the environment. This action is irreversible.
+If you want to test new user configurations or make other changes, do so in a non-production environment (e.g., testing or staging) first, then replicate the changes in production.
+
+Unless you are a developer, we recommend you stay in the production environment for viewing and working with your Kinde account.
-## Move data between environments
+### Can I copy configuration between environments?
-There is currently no way to shift data or configuration settings between environments. For now, you need to replicate settings manually, and export/import data or use the [Kinde Management API](https://docs.kinde.com/kinde-apis/management/). It's on our roadmap to make this easier someday.
+No. You cannot copy configuration settings between environments using the Kinde dashboard. However, you can use the Kinde Management API to achieve this — [follow this guide](/developer-tools/guides/manage-kinde-configuration/).
\ No newline at end of file
diff --git a/src/content/docs/build/environments/production-to-live.mdx b/src/content/docs/build/environments/production-to-live.mdx
index ca6269940..2d1fa8831 100644
--- a/src/content/docs/build/environments/production-to-live.mdx
+++ b/src/content/docs/build/environments/production-to-live.mdx
@@ -1,9 +1,12 @@
---
page_id: 6018b610-bb9d-48b4-a226-f88f7fc68296
title: Prepare your production environment to go live
-description: Comprehensive checklist for preparing production environment to go live including authentication setup, domain configuration, security measures, and analytics integration.
+description: "Checklist for preparing your Kinde production environment before marking it as Live, including required setup, security controls, branding, and analytics."
sidebar:
order: 2
+ label: Go live checklist
+tableOfContents:
+ maxHeadingLevel: 3
relatedArticles:
- d95a8edd-f61a-4095-a80e-ffd67f90a438
- 692187c5-1b82-467a-b86f-85b9098ecaab
@@ -16,6 +19,7 @@ topics:
- environments
- production
- go-live
+ - security
sdk: []
languages: []
audience: developers
@@ -27,44 +31,144 @@ keywords:
- third-party authentication
- custom domain
- multi-factor authentication
- - Google analytics
-updated: 2024-01-15
+ - terms of use and privacy policy
+ - default roles
+ - twilio sms authentication
+ - custom email sender
+ - google analytics
+updated: 2026-05-27
featured: false
deprecated: false
-ai_summary: Comprehensive checklist for preparing production environment to go live including authentication setup, domain configuration, security measures, and analytics integration.
+ai_summary: "This guide helps you prepare a Kinde production environment before marking it as Live. It covers required setup for third-party authentication credentials and Twilio SMS configuration, then walks through recommended business readiness steps in priority order. These include adding terms and privacy policy URLs, enabling multi-factor authentication, setting default roles, connecting a custom domain, configuring a branded email sender, adding tracking scripts, and creating additional development environments. The page also clarifies that the Live switch is a status indicator only and does not publish or change app behavior."
---
-As you build your business on Kinde and configure connections and features, you will eventually want to set your production environment to be ‘live’. This indicates the status of the environment to anyone making changes.
+Use this checklist to prepare your Kinde production environment before you mark it as `Live`.
-Follow the checklist below before you switch your environment to show as 'Live'.
+
-