Merge upstream changes

.changeset/slimy-avocados-remain.md

@@ -0,0 +1,6 @@
+---
+'@nhost/dashboard': patch
+'@nhost/docs': patch
+---
+
+chore: change `Allowed Roles` to `Default Allowed Roles`

dashboard/src/features/projects/roles/settings/components/RoleSettings/RoleSettings.tsx

@@ -36,7 +36,7 @@ export interface RoleSettingsFormValues {
    */
   authUserDefaultRole: string;
   /**
-   * Allowed roles for the project.
+   * Default Allowed roles for the project.
    */
   authUserDefaultAllowedRoles: Role[];
 }
@@ -169,8 +169,8 @@ export default function RoleSettings() {
 
   return (
     <SettingsContainer
-      title="Allowed Roles"
-      description="Allowed roles are roles users get automatically when they sign up."
+      title="Default Allowed Roles"
+      description="Default Allowed Roles are roles users get automatically when they sign up."
       docsLink="https://docs.nhost.io/authentication/users#allowed-roles"
       rootClassName="gap-0"
       className={twMerge(

docs/docs/authentication/users.mdx

@@ -34,9 +34,9 @@ The default role is used when no role is specified in the request. By default, u
 
 You can change what the default role for new users should be at **Settings -> Roles and Permissions**.
 
-### Allowed Roles
+### Default Allowed Roles
 
-Allowed roles are roles the user is allowed to use when making a request. Usually, you would change the role from `user` (the default role) to some other role because you want to use a different role to resolve permissions for a particular request.
+Default Allowed roles are roles the user is allowed to use when making a request. Usually, you would change the role from `user` (the default role) to some other role because you want to use a different role to resolve permissions for a particular request.
 
 By default, users have two allowed roles: