diff --git a/docs/additional-verification/email-verification/initial-setup.mdx b/docs/additional-verification/email-verification/initial-setup.mdx index 20dacdae65..b84b797ce7 100644 --- a/docs/additional-verification/email-verification/initial-setup.mdx +++ b/docs/additional-verification/email-verification/initial-setup.mdx @@ -724,10 +724,9 @@ This can change via a core's configuration (time in milliseconds): - - Go to the SuperTokens SaaS dashboard. - - Click "Edit Configuration" on the environment you want to change. - - Find the `email_verification_token_lifetime` property and change it. - - Click "Save". + - Go to the [SuperTokens SaaS dashboard](https://supertokens.com/dashboard) and select the relevant **Managed** deployment. + - Open **Configuration** and find the **Email Verification** configuration card. + - Change the `email_verification_token_lifetime` value. Configuration changes are saved automatically. diff --git a/docs/additional-verification/mfa/_blocks/paid-feature-callout.mdx b/docs/additional-verification/mfa/_blocks/paid-feature-callout.mdx index 0662fc16ba..96a38808a7 100644 --- a/docs/additional-verification/mfa/_blocks/paid-feature-callout.mdx +++ b/docs/additional-verification/mfa/_blocks/paid-feature-callout.mdx @@ -4,5 +4,5 @@ This is a paid feature. For self hosted users, [Sign up](https://supertokens.com/auth) to get a license key and follow the instructions sent to you by email. Using the `dev` license key is free. Charging only starts once you enable the feature in production using the provided production license key. -For managed service users, you can click on the "enable paid features" button on [the dashboard](https://supertokens.com/dashboard-saas), and follow the steps from there on. Once enabled, this feature is free on the provided development environment. +For managed service users, open the [SaaS Dashboard](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and enable this feature from **Features**. Changes are saved automatically. Once enabled, this feature is free on the provided development environment. ::: diff --git a/docs/authentication/email-password/password-hashing.mdx b/docs/authentication/email-password/password-hashing.mdx index 8ad233c032..c540b47fec 100644 --- a/docs/authentication/email-password/password-hashing.mdx +++ b/docs/authentication/email-password/password-hashing.mdx @@ -37,10 +37,9 @@ Instructions: - 1. Go to the SuperTokens SaaS dashboard. - 2. Click "Edit Configuration" on the environment you want to change. - 3. Find the `password_hashing_alg` property and change it. - 4. Click "Save". + 1. Go to the [SuperTokens SaaS dashboard](https://supertokens.com/dashboard) and select the relevant **Managed** deployment. + 2. Open **Configuration** and find the **Password Hashing Algorithm** setting. + 3. Change the algorithm. Configuration changes are saved automatically. diff --git a/docs/authentication/email-password/password-reset.mdx b/docs/authentication/email-password/password-reset.mdx index eff846bccf..90cd2219a4 100644 --- a/docs/authentication/email-password/password-reset.mdx +++ b/docs/authentication/email-password/password-reset.mdx @@ -521,7 +521,7 @@ email_verification_token_lifetime: 7200000 :::info -- For managed service, you can update these values by visiting the dashboard. +- For managed service, you can update these values in the **Configuration** page of the relevant deployment in the [SaaS Dashboard](https://supertokens.com/dashboard). - This requires that your SuperTokens core version >= `3.6.0` ::: diff --git a/docs/authentication/enterprise/manage-apps.mdx b/docs/authentication/enterprise/manage-apps.mdx index c289cd94c0..f98403112a 100644 --- a/docs/authentication/enterprise/manage-apps.mdx +++ b/docs/authentication/enterprise/manage-apps.mdx @@ -44,7 +44,7 @@ curl --location --request PUT '^{coreInfo.uri}/recipe/multitenancy/app/v2' \ - The above command creates (or updates) an app with the `appId` of `app1`. - It also creates a default tenant for this app with the tenant ID of `public` (that is, the default `tenantId`). -- You can set core configurations for this app (see the configuration.yaml / docker environment variable options for your core). The core configurations for a new app inherit from the configurations provided in the configuration.yaml / docker environment (or the edit configuration dashboard for managed service). +- You can set core configurations for this app (see the configuration.yaml / docker environment variable options for your core). The core configurations for a new app inherit from the configurations provided in the configuration.yaml / docker environment (or the **Configuration** page for the managed deployment). - By default, all the login methods enable for a new app (specifically, the `public` tenant of the new app), but you can pass in `firstFactors` input to specifically enable selected login methods. The built-in Factor IDs that you can use for `firstFactors` are: @@ -71,7 +71,7 @@ curl --location --request PUT '^{coreInfo.uri}/recipe/multitenancy/app' \ - The above command creates (or updates) an app with the `appId` of `app1`. - It also creates a default tenant for this app with the tenant ID of `public` (that is, the default `tenantId`). -- You can set core configurations for this app (see the configuration.yaml / docker environment variable options for your core). The core configurations for a new app inherit from the configurations provided in the configuration.yaml / docker environment (or the edit configuration dashboard for managed service). +- You can set core configurations for this app (see the configuration.yaml / docker environment variable options for your core). The core configurations for a new app inherit from the configurations provided in the configuration.yaml / docker environment (or the **Configuration** page for the managed deployment). - By default, all the login methods enable for a new app (specifically, the `public` tenant of the new app), but you can pass in `false` to any of the login methods specified above to disable them. :::important diff --git a/docs/authentication/m2m/client-credentials.mdx b/docs/authentication/m2m/client-credentials.mdx index c8f52a1cfd..6bd7df5667 100644 --- a/docs/authentication/m2m/client-credentials.mdx +++ b/docs/authentication/m2m/client-credentials.mdx @@ -55,12 +55,7 @@ If you have skipped that page, please follow the tutorial and return here once y ### 1. Enable the OAuth2 features from the Dashboard -You first have to enable the **OAuth2** features from the **SuperTokens.com Dashboard**. -1. Open the **SuperTokens.com Dashboard** -2. Click on the **Enabled Paid Features** button -3. Click on **Managed Service** -4. Check the **Unified Login / M2M** option -5. Click *Save* +You first have to enable **M2M Authentication** from the [**SuperTokens.com Dashboard**](https://supertokens.com/dashboard). Select the relevant **Managed** deployment, open **Features**, and enable **M2M Authentication**. Changes are saved automatically. You should be able to use the OAuth2 recipes in your applications. diff --git a/docs/authentication/passwordless/customize-the-magic-link.mdx b/docs/authentication/passwordless/customize-the-magic-link.mdx index 7199788dfe..ab75b47f7f 100644 --- a/docs/authentication/passwordless/customize-the-magic-link.mdx +++ b/docs/authentication/passwordless/customize-the-magic-link.mdx @@ -342,8 +342,8 @@ passwordless_code_lifetime: 60000 -- Navigate to your SuperTokens managed service dashboard, and click on the Edit Configuration button. -- In there, change the values of the following fields, and click on save. +- Open the [SaaS Dashboard](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and open **Configuration**. +- In the **Passwordless** configuration card, change the value. Configuration changes are saved automatically. ```yaml passwordless_code_lifetime: 60000 diff --git a/docs/authentication/passwordless/customize-the-otp.mdx b/docs/authentication/passwordless/customize-the-otp.mdx index 49e2580e58..f425ef5ba4 100644 --- a/docs/authentication/passwordless/customize-the-otp.mdx +++ b/docs/authentication/passwordless/customize-the-otp.mdx @@ -138,8 +138,8 @@ passwordless_max_code_input_attempts: 3 -- Navigate to your SuperTokens managed service dashboard, and click on the Edit Configuration button. -- In there, change the values of the following fields, and click on save. +- Open the [SaaS Dashboard](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and open **Configuration**. +- In the **Passwordless** configuration card, change the value. Configuration changes are saved automatically. ```yaml passwordless_max_code_input_attempts: 3 @@ -193,8 +193,8 @@ passwordless_code_lifetime: 60000 -- Navigate to your SuperTokens managed service dashboard, and click on the Edit Configuration button. -- In there, change the values of the following fields, and click on save. +- Open the [SaaS Dashboard](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and open **Configuration**. +- In the **Passwordless** configuration card, change the value. Configuration changes are saved automatically. ```yaml passwordless_code_lifetime: 60000 diff --git a/docs/authentication/unified-login/_blocks/paid-feature-callout.mdx b/docs/authentication/unified-login/_blocks/paid-feature-callout.mdx index 4c4ac00ff5..55296a7810 100644 --- a/docs/authentication/unified-login/_blocks/paid-feature-callout.mdx +++ b/docs/authentication/unified-login/_blocks/paid-feature-callout.mdx @@ -2,5 +2,5 @@ :::warning Paid Feature This is a paid feature. -You can click on the **Enable Paid Features** button on [the dashboard](https://supertokens.com/dashboard-saas), and follow the steps from there on. Once enabled, this feature is free on the provided development environment. +For managed service users, open the [SaaS Dashboard](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and enable this feature from **Features**. Changes are saved automatically. Once enabled, this feature is free on the provided development environment. ::: diff --git a/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-a-single-backend.mdx b/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-a-single-backend.mdx index 850e4144d8..64ada82b5f 100644 --- a/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-a-single-backend.mdx +++ b/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-a-single-backend.mdx @@ -56,11 +56,7 @@ If your frontend applications are on the same **domain**, but on different **sub ### 1. Enable the Unified Login feature -Go to the [**SuperTokens.com SaaS Dashboard**](https://supertokens.com) and follow these instructions: -1. Click on the **Enabled Paid Features** button -2. Click on **Managed Service** -3. Check the **Unified Login / M2M** option -4. Click *Save* +Go to the [**SuperTokens.com SaaS Dashboard**](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and open **Features**. Enable **Unified Login**. Changes are saved automatically. ### 2. Create the OAuth2 Clients diff --git a/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-separate-backends.mdx b/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-separate-backends.mdx index dae91379d9..d0f2b01ca9 100644 --- a/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-separate-backends.mdx +++ b/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-separate-backends.mdx @@ -58,11 +58,7 @@ Note that, if the *frontends* and *backends* are in different *sub domains*, you ### 1. Enable the Unified Login feature -Go to the [**SuperTokens.com SaaS Dashboard**](https://supertokens.com) and follow these instructions: -1. Click on the **Enabled Paid Features** button -2. Click on **Managed Service** -3. Check the **Unified Login / M2M** option -4. Click *Save* +Go to the [**SuperTokens.com SaaS Dashboard**](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and open **Features**. Enable **Unified Login**. Changes are saved automatically. ### 2. Create the OAuth2 Clients diff --git a/docs/authentication/unified-login/quickstart-guides/reuse-website-login.mdx b/docs/authentication/unified-login/quickstart-guides/reuse-website-login.mdx index be4bfab0bf..cd1f7ca09f 100644 --- a/docs/authentication/unified-login/quickstart-guides/reuse-website-login.mdx +++ b/docs/authentication/unified-login/quickstart-guides/reuse-website-login.mdx @@ -50,11 +50,7 @@ If you have skipped that page, please follow the tutorial and return here once y ### 1. Enable the Unified Login feature -Go to the [**SuperTokens.com SaaS Dashboard**](https://supertokens.com) and follow these instructions: -1. Click on the **Enabled Paid Features** button -2. Click on **Managed Service** -3. Check the **Unified Login / M2M** option -4. Click *Save* +Go to the [**SuperTokens.com SaaS Dashboard**](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and open **Features**. Enable **Unified Login**. Changes are saved automatically. ### 2. Create the OAuth2 Clients diff --git a/docs/migration/legacy/account-creation/user-creation.mdx b/docs/migration/legacy/account-creation/user-creation.mdx index b5b75b1d5b..c639d95243 100644 --- a/docs/migration/legacy/account-creation/user-creation.mdx +++ b/docs/migration/legacy/account-creation/user-creation.mdx @@ -56,7 +56,7 @@ Importing users from Firebases requires an update to your SuperTokens core confi - ** For Managed Service ** -- Edit the core configuration in the SuperTokens Managed Service Dashboard. +- Edit the core configuration on the **Configuration** page of the relevant deployment in the SuperTokens SaaS Dashboard. - Set the `firebase_password_hashing_signer_key` field in the config to the `base64_signer_key` retrieved from your firebase hashing parameters. diff --git a/docs/migration/rownd/sdk-integration-guide.mdx b/docs/migration/rownd/sdk-integration-guide.mdx index 14c7379abd..646d684cf3 100644 --- a/docs/migration/rownd/sdk-integration-guide.mdx +++ b/docs/migration/rownd/sdk-integration-guide.mdx @@ -23,8 +23,8 @@ By the end, your backend exposes Rownd-compatible plugin routes, your frontend o ## Before you start -These instructions assume that you already have created an account in [the SuperTokens dashboard](https://supertokens.com/dashboard) and have deployed a SuperTokens Core service. -After you have done that, enable the *Account Linking* feature in the created environment and copy the core connection information. +These instructions assume that you have already created an account in [the SuperTokens SaaS Dashboard](https://supertokens.com/dashboard) and have deployed a SuperTokens Core service. +After you have done that, select the relevant **Managed** deployment, enable **Account Linking** from **Features**, and copy the core connection information from **Overview**. :::info no-title diff --git a/docs/post-authentication/account-linking/_blocks/paid-feature-callout.mdx b/docs/post-authentication/account-linking/_blocks/paid-feature-callout.mdx index 4200e524b1..ab021fe07f 100644 --- a/docs/post-authentication/account-linking/_blocks/paid-feature-callout.mdx +++ b/docs/post-authentication/account-linking/_blocks/paid-feature-callout.mdx @@ -5,6 +5,6 @@ This is a paid feature. For self hosted users, [Sign up](https://supertokens.com/auth) to get a license key and follow the instructions sent by email. Using the `dev` license key is free. Charging only starts once you enable the feature in production using the provided production license key. -For managed service users, you can click on the "enable paid features" button on [the dashboard](https://supertokens.com/dashboard-saas), and follow the steps from there on. Once enabled, this feature is free on the provided development environment. +For managed service users, open the [SaaS Dashboard](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and enable this feature from **Features**. Changes are saved automatically. Once enabled, this feature is free on the provided development environment. ::: diff --git a/docs/post-authentication/dashboard/initial-setup.mdx b/docs/post-authentication/dashboard/initial-setup.mdx index 8ef9991f58..a75afbe045 100644 --- a/docs/post-authentication/dashboard/initial-setup.mdx +++ b/docs/post-authentication/dashboard/initial-setup.mdx @@ -200,7 +200,7 @@ You can create 3 dashboard users* for free. If you need to create additional users: - For self hosted users, please [sign up](https://supertokens.com/auth) to generate a license key and follow the instructions sent to you by email. -- For managed service users, you can click on the "enable paid features" button on [the dashboard](https://supertokens.com/dashboard-saas), and follow the steps from there on. +- For managed service users, open the [SaaS Dashboard](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and enable **Additional Dashboard Users** from **Features**. *: A dashboard user is a user that can log into and view the user management dashboard. These users are independent to the users of your application ::: @@ -322,4 +322,3 @@ init( - diff --git a/docs/post-authentication/dashboard/tenant-management.mdx b/docs/post-authentication/dashboard/tenant-management.mdx index 9909571831..8894639e7c 100644 --- a/docs/post-authentication/dashboard/tenant-management.mdx +++ b/docs/post-authentication/dashboard/tenant-management.mdx @@ -86,7 +86,7 @@ This section shows the current configuration values in core for the tenant. You :::caution -Some configuration values may not be editable since they inherit from the App. If using SuperTokens managed hosting, you can modify them in the SaaS Dashboard. Else, if you are self-hosting the SuperTokens core, edit them via Docker environment variables or the `configuration.yaml` file. +Some configuration values may not be editable since they inherit from the App. If using SuperTokens managed hosting, you can modify deployment-level values on the **Configuration** page in the SaaS Dashboard. Else, if you are self-hosting the SuperTokens core, edit them via Docker environment variables or the `configuration.yaml` file. ::: @@ -155,4 +155,3 @@ On continuing, you are further asked for the SAML configuration. You have an opt Adding ThirdParty suffix is not compulsory, however if you wish to add multiple SAML providers for a tenant, you need to add unique suffixes for each of them. ::: - diff --git a/docs/post-authentication/session-management/security.mdx b/docs/post-authentication/session-management/security.mdx index 99c0a2e87e..292615bea1 100644 --- a/docs/post-authentication/session-management/security.mdx +++ b/docs/post-authentication/session-management/security.mdx @@ -363,7 +363,7 @@ access_token_dynamic_signing_key_update_interval: 168 - It must have a ``number`` value with, the default value set to ``168`` :::info -For managed service, update this value by visiting the dashboard. +For managed service, update this value in the **Session Management** configuration card in the relevant deployment's **Configuration** page. ::: ### Use static keys diff --git a/docs/quickstart/next-steps.mdx b/docs/quickstart/next-steps.mdx index 0e3e873102..5f7df74ef6 100644 --- a/docs/quickstart/next-steps.mdx +++ b/docs/quickstart/next-steps.mdx @@ -37,16 +37,14 @@ Select the account that you want to use and wait for the action to complete. Integration with SuperTokens SDKs -After you have signed up, you can skip over the initial wizard that generates an example application. -You already have created one by going though the quickstart guide. -Once you are on the main dashboard page, select a region that is closest to where your services are hosted. -Click **Deploy** and wait for the action to complete. +After you have signed up, select **Managed** and create a deployment. +Choose a region that is closest to where your services are hosted, enter a deployment name, and click **Deploy Core**. Our internal service will deploy a separate environment based on your selection. -After this process is complete, the UI will render the new list of deployments. +After this process is complete, open the new deployment from the list. :::info @@ -60,11 +58,10 @@ In order to use SuperTokens in production, you will have to create a separate de SuperTokens managed service dashboard connectionURI and API key -Select the newly created deployment in order to access its details. -Copy the `Connection URI` and `API Key` values from this page and paste them in your backend code. +Open the newly created deployment and stay on its **Overview** page. In the **Connection Information** section, copy the `Connection URI` and an `API Key` and paste them in your backend code. You can use **Generate Key** to create an additional API key. diff --git a/docs/references/cdi/introduction.mdx b/docs/references/cdi/introduction.mdx index b26d0f5aff..cfcef3ccfb 100644 --- a/docs/references/cdi/introduction.mdx +++ b/docs/references/cdi/introduction.mdx @@ -53,11 +53,10 @@ To know which version you should see: The API uses JWT tokens for authentication. In order for the core service to accept a request you need to set the `api-key` header with the value of your token. -If you are using the managed service, the token can be accessed from [the dashboard](https://supertokens.com/dashboard-saas). +If you are using the managed service, the token can be accessed from the **Connection Information** section on the deployment's **Overview** page in [the SaaS Dashboard](https://supertokens.com/dashboard). In the context of a self-hosted instance, keys are not created by default. You have to explicitly [generate them](/docs/platform-configuration/supertokens-core/api-keys). - diff --git a/docs/references/updating-supertokens.mdx b/docs/references/updating-supertokens.mdx index dd102496ce..cc78702cdb 100644 --- a/docs/references/updating-supertokens.mdx +++ b/docs/references/updating-supertokens.mdx @@ -31,8 +31,7 @@ See the migration sections in the [SuperTokens-core changelog](https://github.co ### Managed core -Access the the [SaaS dashboard](https://supertokens.com/dashboard) and click on the **Upgrade** button. -You can find the action in the top right corner of the environment card. +Open the [SaaS Dashboard](https://supertokens.com/dashboard), select the relevant **Managed** deployment, and click **Upgrade Core** in the deployment header. --- diff --git a/src/components/Callouts/PaidFeatureCallouts.tsx b/src/components/Callouts/PaidFeatureCallouts.tsx index 195e4ce889..8329fdcb02 100644 --- a/src/components/Callouts/PaidFeatureCallouts.tsx +++ b/src/components/Callouts/PaidFeatureCallouts.tsx @@ -19,12 +19,12 @@ export function MFAPaidFeatureCallout() { only start charging you once you enable the feature in production using the provided production license key.

- For managed service users, you can click on the "enable paid features" button on{" "} - - our dashboard + For managed service users, open our{" "} + + SaaS Dashboard - , and follow the steps from there on. Once enabled, this feature is free on the provided development - environment. + , select the relevant Managed deployment, and enable the feature from Features. Changes are saved + automatically. Once enabled, this feature is free on the provided development environment.

@@ -75,12 +75,12 @@ export function AccountLinkingFeatureCallout() { only start charging you once you enable the feature in production using the provided production license key.

- For managed service users, you can click on the "enable paid features" button on{" "} - - our dashboard + For managed service users, open our{" "} + + SaaS Dashboard - , and follow the steps from there on. Once enabled, this feature is free on the provided development - environment. + , select the relevant Managed deployment, and enable the feature from Features. Changes are saved + automatically. Once enabled, this feature is free on the provided development environment.

diff --git a/src/components/PaidFeatureCallout.tsx b/src/components/PaidFeatureCallout.tsx index 19482eb41d..2855935dc2 100644 --- a/src/components/PaidFeatureCallout.tsx +++ b/src/components/PaidFeatureCallout.tsx @@ -56,7 +56,7 @@ export function PaidFeatureCallout(): JSX.Element { Login into the{" "} - + SaaS dashboard . @@ -66,7 +66,7 @@ export function PaidFeatureCallout(): JSX.Element { - Select the Managed tab and click on the Core that you are working with. + Select the Managed tab and open the deployment that you are working with. @@ -80,8 +80,8 @@ export function PaidFeatureCallout(): JSX.Element { - Click Edit and check the features you want to enable. When you're done, click the{" "} - Save button to submit the changes. + Open Features and toggle the features you want to enable. Changes are saved + automatically. @@ -95,7 +95,7 @@ export function PaidFeatureCallout(): JSX.Element { Login into the{" "} - + SaaS dashboard . @@ -105,14 +105,14 @@ export function PaidFeatureCallout(): JSX.Element { - Select the Self-Hosted tab and create a new license key. + Select the Self-hosted tab and create a new license key. - Check the features you want to use, fill in the rest of the fields and submit the form. + Open the license key and toggle the features you want to use. Changes are saved automatically. diff --git a/static/img/quickstart-next-steps-0.png b/static/img/quickstart-next-steps-0.png index ec23c5a166..a48094c4c5 100644 Binary files a/static/img/quickstart-next-steps-0.png and b/static/img/quickstart-next-steps-0.png differ diff --git a/static/img/quickstart-next-steps-1.png b/static/img/quickstart-next-steps-1.png index ddd4dc78f9..c8edff8c99 100644 Binary files a/static/img/quickstart-next-steps-1.png and b/static/img/quickstart-next-steps-1.png differ diff --git a/static/img/quickstart-next-steps-copy-creds.png b/static/img/quickstart-next-steps-copy-creds.png new file mode 100644 index 0000000000..c8edff8c99 Binary files /dev/null and b/static/img/quickstart-next-steps-copy-creds.png differ diff --git a/static/img/quickstart-next-steps-create-deployment.png b/static/img/quickstart-next-steps-create-deployment.png new file mode 100644 index 0000000000..a48094c4c5 Binary files /dev/null and b/static/img/quickstart-next-steps-create-deployment.png differ