adds a coming soon section in dashboard

v2/emailpassword/custom-ui/init/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/emailpassword/pre-built-ui/setup/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/passwordless/custom-ui/init/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/passwordless/pre-built-ui/setup/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/thirdparty/custom-ui/init/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/thirdparty/pre-built-ui/setup/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/thirdpartyemailpassword/custom-ui/init/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/thirdpartyemailpassword/pre-built-ui/setup/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/thirdpartypasswordless/custom-ui/init/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/thirdpartypasswordless/pre-built-ui/setup/dashboard.mdx

@@ -140,7 +140,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -152,7 +152,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -168,6 +168,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.

v2/userdashboard/about.mdx

@@ -146,7 +146,7 @@ To update credentials you need to make a request to SuperTokens core.
 - Replace `<YOUR-API-KEY>` with your API key. If you are using a self hosted SuperTokens core there is no API key by default. In that case you can either skip or ignore the `api-key` header.
 - Replace `<YOUR_EMAIL>` and `<YOUR_NEW_PASSWORD>` with the appropriate values. You can use `newEmail` instead of `newPassword` if you want to update the email
 
-## Viewing users
+## Viewing users list
 
 If you have just created your app, you may not have any users to show on the dashboard.
 
@@ -158,7 +158,7 @@ Navigate to the your frontend app and create a user (via the sign up flow). On c
 
 </AppInfoForm>
 
-## User Management
+## User details page
 
 When you select a user you can view detailed information about the user such as email, phone number, user metadata etc.
 
@@ -174,6 +174,12 @@ You can edit user information and perform actions such as resetting a user's pas
 Some features such as user metadata and email verification have to be enabled in your backend before you can use them in the user management dashboard
 :::
 
+## Managing roles and permissions
+
+:::note
+Coming Soon
+:::
+
 ## Restricting access to dashboard users
 
 When using the dashboard recipe you can restrict access to certain features by providing a list of emails to be considered as "admins". When a dashboard user logs in with an email not present in this list, they will only be able to perform read operations and all write operations will result in the backend SDKs failing the request.