Skip to content

fix: update the Kinde environments page #739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tamalchowdhury wants to merge 5 commits into
base: main
Choose a base branch
from
Open

fix: update the Kinde environments page #739

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6073d77
update the kinde environments page
tamalchowdhury May 24, 2026
62e58ff
update the environment page
tamalchowdhury May 26, 2026
a00bcde
initial update the go-live checklist page
tamalchowdhury May 27, 2026
66d97a2
update the go-live checklist
tamalchowdhury May 27, 2026
b7e91d5
coderabbit fix done
tamalchowdhury May 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
119 changes: 77 additions & 42 deletions src/content/docs/build/environments/environments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand All @@ -12,81 +15,113 @@ topics:
- environments
- development
- production
- staging
- testing
- environment management
- environment switching
- environment settings
sdk: []
languages: []
audience: developers
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.

<Aside>
Kinde environments at a glance:

You must use the default production environment (the one you got when you first signed up to Kinde) as your production environment. This is important for when you are [ready to go live](/build/environments/production-to-live/). You cannot delete the production environment or add additional production environments.
- All Kinde businesses come with one production environment
- You can create additional non-production environments (e.g., dev, test, staging, etc.)
- You will need a paid plan to create more than one non-production environment
- You cannot delete the production environment

</Aside>
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.
![kinde environment switcher](https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/2f35b1fe-faa5-4d54-7abb-1330aba28700/socialsharingimage)

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
<Aside type="upgrade">
You will need a [paid plan](https://kinde.com/pricing/) to create more than one non-production environment.
</Aside>

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.
<Aside type="warning">
You can only add non-production environments to Kinde.
</Aside>

## 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
<Aside>
You cannot delete the production environment.
</Aside>

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/).
154 changes: 129 additions & 25 deletions src/content/docs/build/environments/production-to-live.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand All @@ -16,6 +19,7 @@ topics:
- environments
- production
- go-live
- security
sdk: []
languages: []
audience: developers
Expand All @@ -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'.
![kinde production environment to live](https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/128c203f-79bc-4cce-8d62-55dfbe95e900/socialsharingimage)

<Aside title="The live button is not actually live">
Completing these steps helps reduce launch risk and gives your team a clear signal that the environment is production-ready.

The 'Live' switch is for indicating the environment is live. It does not actually change or do anything in relation to your app. Your app can be live on Kinde without the switch being on.
<Aside title="The Live switch does not publish your app">

The `Live` switch indicates that the environment is live. It does not change your app behavior. Your app can be live on Kinde without this switch being on.

</Aside>

## Required steps to go live

### Set up third-party app credentials

Enter a `Client ID` and `Client secret` in all your third-party authentication connections (such as social connections or enterprise connections). Here are the general steps to update your credentials:

1. Create or register an app with your third-party provider and get the app keys.
2. In Kinde, go to **Settings > Environment > Authentication**.
3. Select **Configure** for the connection you want to update (e.g., Google, Facebook, etc.).
4. Enter the `Client ID` and `Client secret` values.
5. Select **Save**.

Check out the specific connection page for steps for each provider in the [third-party authentication](/authenticate/authentication-methods/set-up-user-authentication/) section.

<Aside type="warning">
If you leave these fields blank at setup, Kinde’s credentials are used and rate limits will apply.
</Aside>

## Go-live checklist
### Add Twilio details

If you are using phone or SMS authentication, configure your Twilio details. Kinde provides 10 SMS messages per month for free to test this feature. To use the full feature set, enter your Twilio credentials:

1. Go to **Settings > Environment > Messaging > SMS**.
2. Select the **Default country** that you want to show on the authentication screen when users sign in.
3. Enter the Twilio details from your Twilio account in the relevant fields.
4. Select **Save**.

Learn more about [phone or SMS authentication](/authenticate/authentication-methods/phone-authentication/).

## Recommended steps

### Add terms and policy URLs

Add your terms and policy URLs so users can access and agree to them during sign-up.

1. Go to **Settings > Business > Details**.

You can also find this menu item under the bottom left corner of the screen by selecting your avatar.
2. Scroll down to the **Terms of use and privacy** section.
3. Enter the relevant URL(s) for your policies. You can add the **Terms of use URL**, the **Privacy policy URL**, or both.
4. Select **Save**.

Learn more about [adding policies, terms, and explicit acceptance](/manage-your-account/business-information/policies-terms/).

### Set up multi-factor authentication

Set up multi-factor authentication (MFA) to add an extra layer of security for user sign-in.

1. Go to **Settings > Environment > Multi-factor auth**.
2. Toggle the switch to **Yes**, **Optional**, or **No**. Selecting **No** disables the environment-level MFA requirement.
3. Select the authentication methods you want to use (for example, SMS or Email).
4. Select **Save**.

Learn more about [multi-factor authentication](/authenticate/multi-factor-auth/enable-multi-factor-authentication/).

### Set up default roles

Set up default roles so new users get the right access level when they sign up.

1. Go to **Settings > User management > Roles**.
2. Add your roles (for example, User or Admin).

Learn more about [default roles](/manage-users/roles-and-permissions/default-user-roles/).

### Connect your custom domain

Connect your custom domain to provide a branded sign-in experience.

1. Go to **Settings > Environment > Custom domain**.
2. Select **Add custom domain**.
3. In the dialog, enter your custom domain.
4. Select **Save**.

Learn more about [using a custom domain](/build/domains/pointing-your-domain/) and [customizing sign-in screens](/design/brand/global-brand-defaults/).

### Configure custom email sender details

Configure a custom email sender to give your users a branded email experience.

1. Go to **Settings > Environment > Messaging > Email Sender**.
2. Enter a **Sender name**.
3. Select **Save**.

To control the full email experience, learn how to [configure a custom SMTP provider with Kinde](/get-started/connect/customize-email-sender/).

### Add tracking scripts

Add tracking scripts like [Google Analytics](/manage-users/view-activity/track-user-sign-in-with-google-analytics/), [Hotjar](/manage-users/view-activity/hotjar/), or [Contentsquare](/manage-users/view-activity/contentsquare/) to track user activity and behavior.

1. Go to **Settings > Environment > Environment details**.
2. Scroll down to the **Third-party analytics** section.
3. Add your tracking ID(s).
4. Select **Save**.

### Add a development environment

Add additional Kinde environments to support a safer development workflow.

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**.

Before you go live, make sure you’ve done the following:
Learn more about [creating and managing environments](/build/environments/environments/).

- (Required) Enter a `Client ID` and `Client secret` in all your [third-party authentication](/authenticate/authentication-methods/set-up-user-authentication/) connections (such as social connections or enterprise connections). If you left these fields blank at setup, Kinde’s credentials are used and rate limits will apply.
- (Required) Add Twilio details if you have [phone or SMS authentication](/authenticate/authentication-methods/phone-authentication/) switched on.
- Add a [development environment](/build/environments/environments/) to continue building your product on Kinde without affecting the live production instance.
- Add [policies and terms](/manage-your-account/business-information/policies-terms/) so that users can access and agree to these on sign up.
- Configure [custom email details](/get-started/connect/customize-email-sender/) so that authentication emails sent to your users come from your business, and not Kinde.
- Connect [your own domain](/build/domains/pointing-your-domain/) and customize the [sign in screens](/design/brand/global-brand-defaults/) to provide a seamless and branded experience for users.
- Set up [multi-factor authentication](/authenticate/multi-factor-auth/enable-multi-factor-authentication/) to add extra layers of security for user sign in.
- Connect [Google analytics](/manage-users/view-activity/track-user-sign-in-with-google-analytics/) to track sign ups through Kinde.
- Set up [default roles](/manage-users/roles-and-permissions/default-user-roles/) for assigning to new users when they sign up.
## Switch production environment to appear live

## Switch an environment to appear live
When you are ready, turn on the `Live` indicator.

When you are ready, turn the 'Live' indicator switch on.
1. Switch to your production environment.
2. Go to **Settings > Environment > Environment details**.
3. Scroll to the **Environment status** section and toggle the switch to **Live**.
4. Select **Save**.

1. Open your production environment.
2. Go to **Settings > Environment > Details.**
3. Scroll to the **Environment status** section and toggle the switch to **Live**.
4. Select **Save**. If there are any issues, an error message will appear. Where there are no errors, your Kinde environment should now show as 'Live.
If there are any issues, an error message will appear. If there are no errors, your Kinde production environment will now show as `Live`.

![Status of production environment in Kinde](https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/ac1aa617-bcb6-4a7f-02d3-b51aa7bcc600/public)
Loading