Merge pull request #956 from nhost/changeset-release/main

chore: update versions

.github/workflows/changesets.yaml

@@ -5,7 +5,6 @@ on:
     branches: [main]
     paths-ignore:
       - 'docs/**'
-      - 'templates/**'
       - 'examples/**'
       - 'assets/**'
       - '**.md'

.github/workflows/tests.yaml

@@ -5,7 +5,6 @@ on:
     branches: [main]
     paths-ignore:
       - 'docs/**'
-      - 'templates/**'
       - 'assets/**'
       - '**.md'
       - 'LICENSE'
@@ -14,7 +13,6 @@ on:
     types: [opened, synchronize]
     paths-ignore:
       - 'docs/**'
-      - 'templates/**'
       - 'assets/**'
       - '**.md'
       - 'LICENSE'

README.md

@@ -87,12 +87,12 @@ await nhost.graphql.request(`{
 Nhost is frontend agnostic, which means Nhost works with all frontend frameworks.
 
 <div align="center">
-  <a href="https://github.com/nhost/nhost/tree/main/templates/web/nextjs-apollo"><img src="assets/nextjs.svg"/></a>
-  <a href="https://github.com/nhost/nhost/tree/main/examples/nuxt-apollo"><img src="assets/nuxtjs.svg"/></a>
-  <a href="https://github.com/nhost/nhost/tree/main/templates/web/react-apollo"><img src="assets/react.svg"/></a>
-  <img src="assets/react-native.svg"/>
-  <a href="https://github.com/nhost/nhost/tree/main/packages/nhost-js"><img src="assets/svelte.svg"/></a>
-  <a href="https://github.com/nhost/nhost/tree/main/packages/nhost-js"><img src="assets/vuejs.svg"/></a>
+  <a href="https://docs.nhost.io/platform/quickstarts/nextjs"><img src="assets/nextjs.svg"/></a>
+  <a href="https://docs.nhost.io/reference/javascript"><img src="assets/nuxtjs.svg"/></a>
+  <a href="https://docs.nhost.io/platform/quickstarts/react"><img src="assets/react.svg"/></a>
+  <a href="https://docs.nhost.io/reference/javascript"><img src="assets/react-native.svg"/></a>
+  <a href="https://docs.nhost.io/reference/javascript"><img src="assets/svelte.svg"/></a>
+  <a href="https://docs.nhost.io/platform/quickstarts/vue"><img src="assets/vuejs.svg"/></a>
 </div>
 
 # Resources
@@ -147,6 +147,13 @@ Here are some ways of contributing to making Nhost better:
             <sub><b>Johan Eliasson</b></sub>
         </a>
     </td>
+    <td align="center">
+        <a href="https://github.com/nunopato">
+            <img src="https://avatars.githubusercontent.com/u/1523504?v=4" width="100;" alt="nunopato"/>
+            <br />
+            <sub><b>Nuno Pato</b></sub>
+        </a>
+    </td>
     <td align="center">
         <a href="https://github.com/gdangelo">
             <img src="https://avatars.githubusercontent.com/u/4352286?v=4" width="100;" alt="gdangelo"/>
@@ -155,10 +162,10 @@ Here are some ways of contributing to making Nhost better:
         </a>
     </td>
     <td align="center">
-        <a href="https://github.com/nunopato">
-            <img src="https://avatars.githubusercontent.com/u/1523504?v=4" width="100;" alt="nunopato"/>
+        <a href="https://github.com/szilarddoro">
+            <img src="https://avatars.githubusercontent.com/u/310881?v=4" width="100;" alt="szilarddoro"/>
             <br />
-            <sub><b>Nuno Pato</b></sub>
+            <sub><b>Szilárd Dóró</b></sub>
         </a>
     </td>
     <td align="center">
@@ -167,15 +174,15 @@ Here are some ways of contributing to making Nhost better:
             <br />
             <sub><b>Guido Curcio</b></sub>
         </a>
-    </td>
+    </td></tr>
+<tr>
     <td align="center">
         <a href="https://github.com/subatuba21">
             <img src="https://avatars.githubusercontent.com/u/34824571?v=4" width="100;" alt="subatuba21"/>
             <br />
             <sub><b>Subha Das</b></sub>
         </a>
-    </td></tr>
-<tr>
+    </td>
     <td align="center">
         <a href="https://github.com/sebagudelo">
             <img src="https://avatars.githubusercontent.com/u/43288271?v=4" width="100;" alt="sebagudelo"/>
@@ -198,10 +205,10 @@ Here are some ways of contributing to making Nhost better:
         </a>
     </td>
     <td align="center">
-        <a href="https://github.com/szilarddoro">
-            <img src="https://avatars.githubusercontent.com/u/310881?v=4" width="100;" alt="szilarddoro"/>
+        <a href="https://github.com/GavanWilhite">
+            <img src="https://avatars.githubusercontent.com/u/2085119?v=4" width="100;" alt="GavanWilhite"/>
             <br />
-            <sub><b>Szilárd Dóró</b></sub>
+            <sub><b>Gavan Wilhite</b></sub>
         </a>
     </td>
     <td align="center">
@@ -210,15 +217,15 @@ Here are some ways of contributing to making Nhost better:
             <br />
             <sub><b>Vadim Smirnov</b></sub>
         </a>
-    </td>
+    </td></tr>
+<tr>
     <td align="center">
         <a href="https://github.com/macmac49">
             <img src="https://avatars.githubusercontent.com/u/831190?v=4" width="100;" alt="macmac49"/>
             <br />
             <sub><b>Macmac49</b></sub>
         </a>
-    </td></tr>
-<tr>
+    </td>
     <td align="center">
         <a href="https://github.com/subhendukundu">
             <img src="https://avatars.githubusercontent.com/u/20059141?v=4" width="100;" alt="subhendukundu"/>
@@ -253,13 +260,6 @@ Here are some ways of contributing to making Nhost better:
             <br />
             <sub><b>Filip Hájek</b></sub>
         </a>
-    </td>
-    <td align="center">
-        <a href="https://github.com/GavanWilhite">
-            <img src="https://avatars.githubusercontent.com/u/2085119?v=4" width="100;" alt="GavanWilhite"/>
-            <br />
-            <sub><b>Gavan Wilhite</b></sub>
-        </a>
     </td></tr>
 <tr>
     <td align="center">
@@ -276,6 +276,13 @@ Here are some ways of contributing to making Nhost better:
             <sub><b>Jerry Jäppinen</b></sub>
         </a>
     </td>
+    <td align="center">
+        <a href="https://github.com/mdp18">
+            <img src="https://avatars.githubusercontent.com/u/11698527?v=4" width="100;" alt="mdp18"/>
+            <br />
+            <sub><b>Max</b></sub>
+        </a>
+    </td>
     <td align="center">
         <a href="https://github.com/mustafa-hanif">
             <img src="https://avatars.githubusercontent.com/u/30019262?v=4" width="100;" alt="mustafa-hanif"/>
@@ -296,6 +303,14 @@ Here are some ways of contributing to making Nhost better:
             <br />
             <sub><b>Savin Vadim</b></sub>
         </a>
+    </td></tr>
+<tr>
+    <td align="center">
+        <a href="https://github.com/Svarto">
+            <img src="https://avatars.githubusercontent.com/u/24279217?v=4" width="100;" alt="Svarto"/>
+            <br />
+            <sub><b>Svarto</b></sub>
+        </a>
     </td>
     <td align="center">
         <a href="https://github.com/muttenzer">
@@ -303,8 +318,7 @@ Here are some ways of contributing to making Nhost better:
             <br />
             <sub><b>Muttenzer</b></sub>
         </a>
-    </td></tr>
-<tr>
+    </td>
     <td align="center">
         <a href="https://github.com/ahmic">
             <img src="https://avatars.githubusercontent.com/u/13452362?v=4" width="100;" alt="ahmic"/>
@@ -332,6 +346,14 @@ Here are some ways of contributing to making Nhost better:
             <br />
             <sub><b>Colin Broderick</b></sub>
         </a>
+    </td></tr>
+<tr>
+    <td align="center">
+        <a href="https://github.com/dminkovsky">
+            <img src="https://avatars.githubusercontent.com/u/218725?v=4" width="100;" alt="dminkovsky"/>
+            <br />
+            <sub><b>Dmitry Minkovsky</b></sub>
+        </a>
     </td>
     <td align="center">
         <a href="https://github.com/dohomi">
@@ -346,8 +368,7 @@ Here are some ways of contributing to making Nhost better:
             <br />
             <sub><b>Gaurav Agrawal</b></sub>
         </a>
-    </td></tr>
-<tr>
+    </td>
     <td align="center">
         <a href="https://github.com/alveshelio">
             <img src="https://avatars.githubusercontent.com/u/8176422?v=4" width="100;" alt="alveshelio"/>
@@ -362,6 +383,14 @@ Here are some ways of contributing to making Nhost better:
             <sub><b>Hoang Do</b></sub>
         </a>
     </td>
+    <td align="center">
+        <a href="https://github.com/eltociear">
+            <img src="https://avatars.githubusercontent.com/u/22633385?v=4" width="100;" alt="eltociear"/>
+            <br />
+            <sub><b>Ikko Ashimine</b></sub>
+        </a>
+    </td></tr>
+<tr>
     <td align="center">
         <a href="https://github.com/jladuval">
             <img src="https://avatars.githubusercontent.com/u/1935359?v=4" width="100;" alt="jladuval"/>
@@ -383,21 +412,28 @@ Here are some ways of contributing to making Nhost better:
             <sub><b>Leo Thorp</b></sub>
         </a>
     </td>
+    <td align="center">
+        <a href="https://github.com/LucasBois1">
+            <img src="https://avatars.githubusercontent.com/u/44686060?v=4" width="100;" alt="LucasBois1"/>
+            <br />
+            <sub><b>Lucas Bois</b></sub>
+        </a>
+    </td>
     <td align="center">
         <a href="https://github.com/MarcelloTheArcane">
             <img src="https://avatars.githubusercontent.com/u/21159570?v=4" width="100;" alt="MarcelloTheArcane"/>
             <br />
             <sub><b>Max Reynolds</b></sub>
         </a>
-    </td></tr>
-<tr>
+    </td>
     <td align="center">
         <a href="https://github.com/nachoaldamav">
             <img src="https://avatars.githubusercontent.com/u/22749943?v=4" width="100;" alt="nachoaldamav"/>
             <br />
             <sub><b>Nacho Aldama</b></sub>
         </a>
-    </td>
+    </td></tr>
+<tr>
     <td align="center">
         <a href="https://github.com/ghoshnirmalya">
             <img src="https://avatars.githubusercontent.com/u/6391763?v=4" width="100;" alt="ghoshnirmalya"/>

docs/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @nhost/docs
 
+## 0.0.3
+
+### Patch Changes
+
+- eb46f7d8: Use port 1337 if no port is specified when using "localhost" as `subdomain`.
+
+## 0.0.2
+
+### Patch Changes
+
+- 747aa969: fix: added twitch and discord as provider
+
 ## 0.0.1
 
 ### Patch Changes

docs/docs/platform/authentication/email-templates.md

@@ -12,11 +12,11 @@ The following email templates are available:
 - **signin-passwordless** - Magic Link
 - **password-reset** - Reset password
 
-Changing email templates is only available for apps on the [Pro and Enterprise plan](https://nhost.io/pricing).
+Changing email templates is only available for projects on the [Pro and Enterprise plan](https://nhost.io/pricing).
 
 ## Update Email Templates
 
-Your app must be connected to a GitHub repository using the [GitHub Integration](/platform/github-integration) to be able to change the email templates.
+Your project must be connected to a GitHub repository using the [GitHub Integration](/platform/github-integration) to be able to change the email templates.
 
 Email templates are automatically deployed during a deployment, just like database migrations, Hasura metadata, and Serverless Functions.
 
@@ -29,7 +29,7 @@ The email templates should be provided as body.html and subject.txt files in thi
 **Example:** Email templates for `en` (English) and `es` (Spanish):
 
 ```txt
-my-nhost-app/
+my-nhost-project/
 └── nhost/
     ├── config.yaml
     ├── emails/
@@ -70,7 +70,7 @@ As you see, the format is:
 nhost/emails/{two-letter-language-code}/{email-template}/[subject.txt, body.html]
 ```
 
-Default templates for English (`en`) and French (`fr`) are automatically generated when the app is initialized with the [CLI](/platform/cli).
+Default templates for English (`en`) and French (`fr`) are automatically generated when the project is initialized with the [CLI](/platform/cli).
 
 ## Languages
 

docs/docs/platform/authentication/index.md

@@ -7,7 +7,7 @@ image: /img/og/platform/authentication.png
 
 Nhost Authentication is a ready-to-use authentication service that is integrated with the [GraphQL API](/platform/graphql) and its permission system from Hasura.
 
-Nhost Authentication lets you authenticate users to your app using different sign-in methods:
+Nhost Authentication lets you authenticate users using different sign-in methods:
 
 - [Email and Password](/platform/authentication/sign-in-with-email-and-password)
 - [Magic Link](/platform/authentication/sign-in-with-magic-link)

docs/docs/platform/authentication/sign-in-methods/1-email-password.mdx

@@ -7,7 +7,7 @@ image: /img/og/platform/sign-in-with-email-and-password.png
 
 Follow this guide to sign in users with email and password.
 
-The email and password sign-in method is enabled by default for all Nhost apps.
+The email and password sign-in method is enabled by default for all Nhost projects.
 
 ## Sign Up
 
@@ -22,7 +22,7 @@ await nhost.auth.signUp({
 })
 ```
 
-If you've turned on email verification in your app's **Authentication Settings**, a user will be sent a verification email upon signup. The user must click the verification link in the email before they can sign in.
+If you've turned on email verification in your project's **Authentication Settings**, a user will be sent a verification email upon signup. The user must click the verification link in the email before they can sign in.
 
 ## Sign In
 
@@ -39,6 +39,6 @@ await nhost.auth.signIn({
 
 ## Verified Emails
 
-You can decide if only verified emails should be able to sign in or not. Modify the **Only allow login for verified emails.** setting in the **Authentication Settings** section under **Users** in your Nhost app.
+You can decide if only verified emails should be able to sign in or not. Modify the **Only allow users with verified emails to sign in.** setting in the **Authentication Settings** section under **Users** in your Nhost project.
 
-An email-verification email is automatically sent to the user during sign-up if your app only allows to sign in users with verified emails. You can also manually send the verification email to the user using [`nhost.auth.sendVerificationEmail()`](/reference/javascript/auth/send-verification-email).
+An email-verification email is automatically sent to the user during sign-up if your project only allows to sign in users with verified emails. You can also manually send the verification email to the user using [`nhost.auth.sendVerificationEmail()`](/reference/javascript/auth/send-verification-email).

docs/docs/platform/authentication/sign-in-methods/2-magic-link.mdx

@@ -7,7 +7,7 @@ image: /img/og/platform/sign-in-with-magic-link.png
 
 Follow this guide to sign in users with Magic Link, also called passwordless email.
 
-The Magic Link sign-in method enables you to sign in users to your app using an email address, without requiring a password.
+The Magic Link sign-in method enables you to sign in users using an email address, without requiring a password.
 
 ## Setup
 
@@ -20,9 +20,9 @@ Enable the Magic Link sign-in method in the Nhost dashboard under **Users** -> *
 To sign in users with Magic Link is a two-step process:
 
 1. Send a Magic Link to the user's email address.
-2. The user clicks the Magic Link in their email to sign in to your app.
+2. The user clicks the Magic Link in their email to sign in.
 
-Use the [Nhost JavaScript client](/reference/javascript) to sign up users with Magic Link in your app:
+Use the [Nhost JavaScript client](/reference/javascript) to sign in users with Magic Link:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/4-apple.mdx

@@ -5,7 +5,7 @@ slug: /platform/authentication/sign-in-with-apple
 image: /img/og/platform/sign-in-with-apple.png
 ---
 
-Follow this guide to sign in users with Apple with your Nhost App.
+Follow this guide to sign in users with Apple.
 
 <p align="center">
   <img
@@ -89,7 +89,7 @@ Follow this guide to sign in users with Apple with your Nhost App.
 
 ## Sign In Users
 
-Use the [Nhost JavaScript client](/reference/javascript) to sign in users in your app:
+Use the [Nhost JavaScript client](/reference/javascript) to sign in users:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/4-discord.mdx

@@ -5,7 +5,7 @@ slug: /platform/authentication/sign-in-with-discord
 image: /img/og/platform/sign-in-with-discord.png
 ---
 
-Follow this guide to sign in users with Discord with your Nhost App.
+Follow this guide to sign in users with Discord.
 
 <p align="center">
   <img
@@ -36,7 +36,7 @@ Follow this guide to sign in users with Discord with your Nhost App.
 
 ## Sign In Users
 
-Use the [Nhost JavaScript client](/reference/javascript) to sign in users in your app:
+Use the [Nhost JavaScript client](/reference/javascript) to sign in users:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/4-facebook.mdx

@@ -5,7 +5,7 @@ slug: /platform/authentication/sign-in-with-facebook
 image: /img/og/platform/sign-in-with-facebook.png
 ---
 
-Follow this guide to sign in users with Facebook with your Nhost App.
+Follow this guide to sign in users with Facebook.
 
 <p align="center">
   <img
@@ -59,7 +59,7 @@ To make sure we can fetch all user data (email, profile picture and name). For t
 
 ## Sign In Users
 
-Use the [Nhost JavaScript client](/reference/javascript) to sign in users in your app:
+Use the [Nhost JavaScript client](/reference/javascript) to sign in users:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/4-github.mdx

@@ -5,7 +5,7 @@ slug: /platform/authentication/sign-in-with-github
 image: /img/og/platform/sign-in-with-github.png
 ---
 
-Follow this guide to sign in users with GitHub with your Nhost App.
+Follow this guide to sign in users with GitHub.
 
 <p align="center">
   <img
@@ -44,7 +44,7 @@ Follow this guide to sign in users with GitHub with your Nhost App.
 
 ## Sign In Users
 
-Use the [Nhost JavaScript client](/reference/javascript) to sign in users in your app:
+Use the [Nhost JavaScript client](/reference/javascript) to sign in users:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/4-google.mdx

@@ -5,7 +5,7 @@ slug: /platform/authentication/sign-in-with-google
 image: /img/og/platform/sign-in-with-google.png
 ---
 
-Follow this guide to sign in users with Google with your Nhost App.
+Follow this guide to sign in users with Google.
 
 <p align="center">
   <img
@@ -68,7 +68,7 @@ Follow this guide to sign in users with Google with your Nhost App.
 
 ## Sign In Users
 
-Use the Nhost JavaScript client to sign in users in your app:
+Use the Nhost JavaScript client to sign in users:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/4-linkedin.mdx

@@ -5,7 +5,7 @@ slug: /platform/authentication/sign-in-with-linkedin
 image: /img/og/platform/sign-in-with-linkedin.png
 ---
 
-Follow this guide to sign in users with LinkedIn with your Nhost App.
+Follow this guide to sign in users with LinkedIn.
 
 <p align="center">
   <img
@@ -51,7 +51,7 @@ Follow this guide to sign in users with LinkedIn with your Nhost App.
 
 ## Sign In Users
 
-Use the [Nhost JavaScript client](/reference/javascript) to sign in users in your app:
+Use the [Nhost JavaScript client](/reference/javascript) to sign in users:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/4-spotify.mdx

@@ -5,7 +5,7 @@ slug: /platform/authentication/sign-in-with-spotify
 image: /img/og/platform/sign-in-with-spotify.png
 ---
 
-Follow this guide to sign in users with Spotify with your Nhost App.
+Follow this guide to sign in users with Spotify.
 
 <p align="center">
   <img
@@ -44,7 +44,7 @@ Follow this guide to sign in users with Spotify with your Nhost App.
 
 ## Sign In Users
 
-Use the [Nhost JavaScript client](/reference/javascript) to sign in users in your app:
+Use the [Nhost JavaScript client](/reference/javascript) to sign in users:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/4-twitch.mdx

@@ -5,7 +5,7 @@ slug: /platform/authentication/sign-in-with-twitch
 image: /img/og/platform/sign-in-with-twitch.png
 ---
 
-Follow this guide to sign in users with Twitch with your Nhost App.
+Follow this guide to sign in users with Twitch.
 
 <p align="center">
   <img
@@ -38,7 +38,7 @@ Follow this guide to sign in users with Twitch with your Nhost App.
 
 ## Sign In Users
 
-Use the [Nhost JavaScript client](/reference/javascript) to sign in users in your app:
+Use the [Nhost JavaScript client](/reference/javascript) to sign in users:
 
 ```js
 nhost.auth.signIn({

docs/docs/platform/authentication/sign-in-methods/index.md

@@ -17,13 +17,13 @@ Nhost Authentication support the following sign-in methods:
 
 ## Enabling Social Sign-In Provider
 
-To start with social sign-in, select your app in Nhost Console and go to **Users** → **Authentication Settings**.
+To start with social sign-in, select your project in Nhost Dashboard and go to **Users** → **Authentication Settings**.
 
 You need to set the Client ID and Client Secret for each provider that you want to enable.
 
 ## Implementing sign-in experience
 
-Use the [Nhost JavaScript SDK](/reference/javascript) and the `signIn()` method to implement social sign-in in your app,
+Use the [Nhost JavaScript SDK](/reference/javascript) and the `signIn()` method to implement social sign-in for your project.
 
 Here's an example of how to implement sign-in with GitHub:
 
@@ -33,8 +33,7 @@ nhost.auth.signIn({
 })
 ```
 
-Users are redirected to your Nhost app's **client URL** by default. By default, your Nhost app's client URL is set to `http://localhost:3000`. You can change the value of your client URL in the Nhost console by going to **Users** → **Authentication Settings** → **Client URL**.
-
+Users are redirected to your Nhost project's **client URL** by default. By default, your Nhost project's client URL is set to `http://localhost:3000`. You can change the value of your client URL in the Nhost console by going to **Users** → **Authentication Settings** → **Client URL**.
 
 Here is an example of how to redirect to another host or path:
 
@@ -51,7 +50,7 @@ nhost.auth.signIn({
 
 Scopes are a mechanism in OAuth to allow or limit an application's access to a user's account.
 
-By default, Nhost sets the scope to get the name, email, and avatar url for each user. Editing scope is not currently supported.
+By default, Nhost sets the scope to get the name, email, and avatar URL for each user. Editing scope is not currently supported.
 
 ## Provider OAuth Tokens
 

docs/docs/platform/authentication/users.mdx

@@ -39,7 +39,7 @@ query {
 
 Users should be created using the sign-up or sign-in flows as described under [sign-in methods](/platform/authentication/sign-in-methods).
 
-- **Never** create users directly via GraphQL or database.
+- **Never** create users directly via GraphQL or database, unless you [import users](#import-users) from an external system.
 - **Never** modify the `auth.users` table.
 - **Never** modify the GraphQL root queries or fields for any of the tables in the `auth` schema.
 
@@ -136,3 +136,31 @@ await nhost.auth.signUp({
   }
 })
 ```
+
+## Import Users
+
+If you have users in a different system, you can import them into Nhost. When importing users you should insert the users directly into the database instead of using the authentication endpoints (`/signup/email-password`).
+
+It's possible to insert users via GraphQL or SQL.
+
+### GraphQL
+
+Make a GraphQL request to insert a user like this:
+
+```graphql
+mutation insertUser($user: users_insert_input!) {
+  insertUser(object: $user) {
+    id
+  }
+}
+```
+
+### SQL
+
+Connect directly to the database and insert a user like this:
+
+```sql
+INSERT INTO auth.users (id, email, display_name, password_hash, ..) VALUES ('<user-id>', '<email>', '<display-name>', '<password-hash>', ..);
+```
+
+User passwords are hashed using [bcrypt](https://en.wikipedia.org/wiki/Bcrypt) in Nhost.

docs/docs/platform/cli.mdx

@@ -7,9 +7,9 @@ image: /img/og/platform/cli.png
 import Tabs from '@theme/Tabs'
 import TabItem from '@theme/TabItem'
 
-Nhost CLI, or `nhost`, is a command-line interface that lets you run and manage Nhost apps locally on Mac, Linux and Windows (WSL2).
+Nhost CLI, or `nhost`, is a command-line interface that lets you run and manage Nhost projects locally on Mac, Linux and Windows (WSL2).
 
-This means you get a full-featured Nhost app running locally on your machine:
+This means you get a full-featured Nhost project running locally on your machine:
 
 - Postgres Database
 - Hasura GraphQL API
@@ -55,41 +55,41 @@ Start by authenticating yourself to Nhost Cloud:
 nhost login
 ```
 
-Once signed in, you can list all your Nhost apps using:
+Once signed in, you can list all your Nhost projects using:
 
 ```
 nhost list
 ```
 
-Let's start by initializing a remote Nhost app locally with the following command:
+Let's start by initializing a remote Nhost project locally with the following command:
 
 ```
 nhost init --remote
 ```
 
-Pick a Nhost app to use then change the directory once the app initialization is completed:
+Pick a Nhost project to use then change the directory once the project initialization is completed:
 
 ```
 cd my_test_app
 ```
 
-Then start the Nhost app locally:
+Then start the Nhost project locally:
 
 ```
 nhost up
 ```
 
-Hasura Console starts automatically and your Nhost app is running locally with the backend URL: `http://localhost:1337`.
+Hasura Console starts automatically and your Nhost project is running locally.
 
 ## Subdomain and Region
 
-Use `localhost:1337` as the `subdomain`, and skip `region` when using the CLI and the [JavaScript SDK](/reference/javascript):
+Use `localhost` as the `subdomain`, and skip `region` when using the CLI and the [JavaScript SDK](/reference/javascript):
 
 ```
 import { NhostClient } from '@nhost/nhost-js'
 
 const nhost = new NhostClient({
-  subdomain: 'localhost:1337',
+  subdomain: 'localhost',
 })
 ```
 
@@ -97,12 +97,22 @@ const nhost = new NhostClient({
 
 During local development with the CLI, all transactional emails from Authentication are sent to a local Mailhog instance, instead of to the recipient's email address. You'll see an address where after starting [`nhost up`](/reference/cli/up) where all emails are sent to.
 
-For the example below, all emails are accessable at `http://localhost:8839`.
+For the example below, all emails are accessible at `http://localhost:8025`.
 
 ```bash
 $ nhost up
-✔ Your app is running at http://localhost:1337 (Ctrl+C to stop)
-ℹ Emails will be sent to http://localhost:8839
+URLs:
+- Postgres:         postgres://postgres:postgres@localhost:5432/postgres
+- GraphQL:          http://localhost:1337/v1/graphql
+- Auth:             http://localhost:1337/v1/auth
+- Storage:          http://localhost:1337/v1/storage
+- Functions:        http://localhost:1337/v1/functions
+
+- Hasura console:  http://localhost:9695
+- Mailhog:         http://localhost:8025
+
+- subdomain:       localhost
+- region:          (empty)
 ```
 
 ## What's next?

docs/docs/platform/database/index.mdx

@@ -7,7 +7,7 @@ image: /img/og/platform/database.png
 import Tabs from '@theme/Tabs'
 import TabItem from '@theme/TabItem'
 
-Every Nhost app comes with its own [Postgres database](https://postgres.org/). Postgres is the world's most advanced open-source relational database and it's the most [popular SQL database for developers](https://insights.stackoverflow.com/survey/2021#section-most-loved-dreaded-and-wanted-databases).
+Every Nhost project comes with its own [Postgres database](https://postgres.org/). Postgres is the world's most advanced open-source relational database and it's the most [popular SQL database for developers](https://insights.stackoverflow.com/survey/2021#section-most-loved-dreaded-and-wanted-databases).
 
 :::info
 
@@ -34,7 +34,7 @@ Hasura Console is where you manage your database. This is where you create and m
 
 The two schemas `auth` and `storage` are reserved for Nhost Auth and Nhost Storage to work. You're allowed to modify **permissions** and **add relationships**. However, never modify any tables or remove relationships that were added by Nhost inside the `auth` and `storage` schemas.
 
-Generally, you should use the `public` schema when creating and managing your tables for your app. It's also ok to add custom schemas for more advanced usage.
+Generally, you should use the `public` schema when creating and managing your tables for your project. It's also ok to add custom schemas for more advanced usage.
 
 ## Create Table
 

docs/docs/platform/environment-variables.md

@@ -6,11 +6,11 @@ image: /img/og/platform/environment-variables.png
 
 Environment Variables are key-value pairs configured outside your source code. They are used to store environment-specific values such as API keys.
 
-You can manage your app's environment variables in Nhost Console under **Variables**. When you define a new variable, you can set one value for **production** and one for **development**.
+You can manage your project's Environment Variables in Nhost Dashboard under **Variables**. When you define a new variable, you can set one value for **production** and one for **development**.
 
 ![Environment Variables](/img/platform/environment-variables/environment-variables.png)
 
-When an environment variable is changed, you must deploy your app again using the [GitHub integration](/platform/github-integration) for the changes to take effect.
+When an Environment Variable is changed, you must deploy your project again using the [GitHub integration](/platform/github-integration) for the changes to take effect.
 
 Environment Variables are available in:
 
@@ -19,7 +19,7 @@ Environment Variables are available in:
 
 ## System Environment Variables
 
-System environment variables are automatically available in production and during development. The following system environment variables are available:
+System Environment Variables are automatically available in production and during development. The following system Environment Variables are available:
 
 - `NHOST_ADMIN_SECRET`
 - `NHOST_WEBHOOK_SECRET`
@@ -38,7 +38,7 @@ NHOST_BACKEND_URL=https://xxxxxxx.nhost.run
 
 ## Development Environment Variables
 
-When developing locally using the [CLI](/platform/cli), environment variables set in `.env.development` are available in your local environment. There are two ways to manage them:
+When developing locally using the [CLI](/platform/cli), Environment Variables set in `.env.development` are available in your local environment. There are two ways to manage them:
 
 1. Edit the `.env.development` file manually.
-2. Add development environment variables in the Nhost Console and use `nhost env pull` to sync them. This way, your team members will also have access to the same variables.
+2. Add development Environment Variables in the Nhost Dashboard and use `nhost env pull` to sync them. This way, your team members will also have access to the same Environment Variables.

docs/docs/platform/github-integration.mdx

@@ -4,9 +4,9 @@ sidebar_position: 10
 image: /img/og/platform/github-integration.png
 ---
 
-The GitHub integration allows you to automatically deploy your Nhost app when on push and merge to a GitHub repository that is connected to your Nhost app.
+The GitHub integration allows you to automatically deploy your Nhost project when on push and merge to a GitHub repository that is connected to your Nhost project.
 
-When a GitHub repository is connected to a Nhost app, Nhost automatically deploys changes when you push code to the repo.
+When a GitHub repository is connected to a Nhost project, Nhost automatically deploys changes when you push code to the repo.
 
 The following things are deployed:
 
@@ -20,11 +20,11 @@ Settings in `nhost/config.yaml` are **not** deployed. That means you need to man
 
 ## Connecting a GitHub repository
 
-1. From your Nhost app, click **Connect to Github**.
+1. From your Nhost project, click **Connect to Github**.
 
 ![Connect to GitHub](/img/architecture/cli/connect-repo-step-1.png)
 
-2. **Install the Nhost app** on your Github account.
+2. **Install the Nhost project** on your Github account.
 
 ![Install the Nhost GitHub App](/img/architecture/cli/connect-repo-step-2.png)
 
@@ -36,9 +36,9 @@ Settings in `nhost/config.yaml` are **not** deployed. That means you need to man
 
 Nhost only deploys your **deployment branch**. By default, your deployment branch matches the default branch set on GitHub (usually `main`).
 
-You can change the deployment branch by clicking **Edit** next to the repository in your Nhost app's dashboard.
+You can change the deployment branch by clicking **Edit** next to the repository in your Nhost project's Overview.
 
-You can have multiple Nhost apps connected to the same GitHub repository and use different deployment branches (e.g., `main` and `staging`).
+You can have multiple Nhost projects connected to the same GitHub repository and use different deployment branches (e.g., `main` and `staging`).
 
 <center>
   <img src="/img/platform/github-integration/deployment-branch.png" alt="drawing" width="50%" />
@@ -46,7 +46,7 @@ You can have multiple Nhost apps connected to the same GitHub repository and use
 
 ## Base Directory
 
-If your Nhost app is not at the root of your git repository, you can set a custom base directory. The base directory is where the `nhost` and `functions` directories are located. In other words, the base directory is the **parent directory** of the `nhost` and `functions` directories.
+If your Nhost project is not at the root of your git repository (typically when using a monorepo), you can set a custom base directory. The base directory is where the `nhost` directory is located. In other words, the base directory is the **parent directory** of the `nhost` folder.
 
 <center>
   <img src="/img/platform/github-integration/base-directory.png" alt="drawing" width="50%" />
@@ -54,4 +54,4 @@ If your Nhost app is not at the root of your git repository, you can set a custo
 
 ## Next Steps
 
-- Learn how to [use the CLI to deploy your Nhost app](/platform/overview/get-started-with-nhost-cli).
+- Learn how to [use the CLI to deploy your Nhost project](/platform/overview/get-started-with-nhost-cli).

docs/docs/platform/graphql/index.md

@@ -6,7 +6,7 @@ image: /img/og/platform/graphql.png
 
 A GraphQL API is automatically and instantly available based on the tables and columns in your [database](/platform/database).
 
-The GraphQL API has instant support for inserting, selecting, updating, and deleting data, which usually account for 80% of all operations you need in your app.
+The GraphQL API has instant support for inserting, selecting, updating, and deleting data, which usually account for 80% of all API operations you need.
 
 It's the [Hasura GraphQL engine](https://github.com/hasura/graphql-engine) that powers the GraphQL API which means that all documentation about [queries](https://hasura.io/docs/latest/graphql/core/databases/postgres/queries/index/), [mutations](https://hasura.io/docs/latest/graphql/core/databases/postgres/mutations/index/), and [subscriptions](https://hasura.io/docs/latest/graphql/core/databases/postgres/subscriptions/index/) from Hasura's documentation is applicable.
 
@@ -40,7 +40,7 @@ When building more complex frontend applications, we recommend using a more adva
 A GraphQL query is used to fetch data from the database.
 
 :::tip
-The [Queries documentation from Hasura](https://hasura.io/docs/latest/graphql/core/databases/postgres/queries/index/) is applicable since Nhost uses Hasura's GraphQL Engine for your app.
+The [Queries documentation from Hasura](https://hasura.io/docs/latest/graphql/core/databases/postgres/queries/index/) is applicable since we're using Hasura's GraphQL Engine for your project.
 :::
 
 **Example:** A GraphQL query to select `title`, `body`, and `isCompleted` for every row in the `todos` table.
@@ -131,7 +131,7 @@ query GetTodosWithLatestComments {
 A GraphQL mutation is used to insert, upsert, update, or delete data.
 
 :::tip
-The [Mutations documentation from Hasura](https://hasura.io/docs/latest/graphql/core/databases/postgres/mutations/index/) is applicable since Nhost uses Hasura's GraphQL Engine for your app.
+The [Mutations documentation from Hasura](https://hasura.io/docs/latest/graphql/core/databases/postgres/mutations/index/) is applicable since we're using Hasura's GraphQL Engine for your project.
 :::
 
 ### Insert Data

docs/docs/platform/graphql/permissions.md

@@ -32,7 +32,7 @@ The rule above make it so users can only select posts where the value of `user_i
 
 `x-hasura-user-id` is a permission variable that is used to create permission rules in Hasura. The permission variable comes from the [access token](platform/authentication#access-tokens) that signed-in users have.
 
-The `x-hasura-user-id` permission variable is always available for all signed-in users. You can add [custom permission variables](#custom-permission-variables) to create more complex permission rules unique to your app.
+The `x-hasura-user-id` permission variable is always available for all signed-in users. You can add [custom permission variables](#custom-permission-variables) to create more complex permission rules unique to your project.
 
 ## Custom Permission Variables
 

docs/docs/platform/overview/get-started-with-nhost-cli.mdx

@@ -99,11 +99,11 @@ nhost logout
 
 ## Set up your project
 
-### 1. Create a new Nhost app
+### 1. Create a new Nhost project
 
-import CreateApp from '@site/src/components/create-nhost-app.mdx';
+import CreateProject from '@site/src/components/create-nhost-project.mdx'
 
-<CreateApp />
+<CreateProject />
 
 ### 2. Create a new GitHub Repository
 
@@ -119,61 +119,43 @@ either public or private.
 
 ### 3. Connect Nhost project to Github
 
-Finally, connect your Github repository to your Nhost project. Doing so will
-enable Nhost to deploy new versions of your project when you push automatically
-commits to your connected Git repository.
+Finally, connect your GitHub repository to your Nhost project. Doing so will
+enable Nhost to deploy new versions of your project when you push new commits to your connected Git repository.
 
-1. From your project workspace, click **Connect to Github**.
+1. From your project workspace, click **Connect to GitHub**.
 
 ![Connect to GitHub](/img/architecture/cli/connect-repo-step-1.png)
 
-2. **Install the Nhost app** on your Github account.
+2. **Install the Nhost app** on your GitHub account.
 
 ![Connect to GitHub](/img/architecture/cli/connect-repo-step-2.png)
 
-3. **Connect** your Github repository.
+3. **Connect** your GitHub repository.
 
 ![Connect to GitHub](/img/architecture/cli/connect-repo-step-3.png)
 
 ## Develop locally
 
-## 1. Initialize your Nhost app
+## 1. Initialize your Nhost project
 
 **Nhost CLI** brings the functionality of your Nhost production environment
 directly to your local machine.
 
 It provides Docker containers to run the backend services that match your
-production application in a local environment. That way, you can make changes
+production environment in a local environment. That way, you can make changes
 and test your code locally before deploying those changes to production.
 
-You can either initialize a blank Nhost app locally to start from scratch by
-running the following command:
+Initialize your Nhost project locally with the following command:
 
 ```bash
-nhost init -n my-nhost-app
+nhost init --remote
 ```
 
-And then link it to a remote app from your Nhost workspace in `app.nhost.io` by
-running the `link` command and selecting the corresponding app from the prompt:
+It will prompt you to choose what Nhost project you want to initialize.
 
-```bash
-nhost link
-```
+![Select Nhost Project](/img/architecture/cli/cli-select-app.png)
 
-Or you can directly initialize a local Nhost app from one of your existing
-production apps by specifying the `--remote` flag:
-
-```bash
-nhost init --remote -n my-nhost-app
-```
-
-It will also prompt you to choose the remote app you'd like to use to initialize
-your local Nhost development environment.
-
-![Select app](/img/architecture/cli/cli-select-app.png)
-
-The `init` command creates the Nhost app inside your current working directory
-within a `nhost/` folder.
+Your file system will be populated with the following files and folders:
 
 ```
 my-nhost-app/
@@ -200,11 +182,11 @@ git push -u origin main
 
 ## 2. Start a local development environment
 
-To start a local development environment for your Nhost app, run the following
+To start a local development environment for your Nhost project, run the following
 command:
 
 ```bash
-nhost dev
+nhost up
 ```
 
 :::caution
@@ -213,11 +195,10 @@ Make sure [Docker](https://www.docker.com/get-started) is up and running. It’s
 
 Running this command will start up all the backend services provided by Nhost.
 
-It also runs a webserver to serve the Hasura console for the GraphQL engine so
-you can manage the database and try out the API.
+It also runs a webserver to serve the Hasura Console for the GraphQL Engine so
+you can manage the database and test the GraphQL API.
 
-The Hasura console should open automatically at
-[http://localhost:1337](http://localhost:1337/).
+The Hasura Console opens automatically at [http://localhost:9695](http://localhost:9695/).
 
 ![Hasura Console](/img/architecture/cli/hasura-console.png)
 
@@ -226,7 +207,7 @@ The Hasura console should open automatically at
 There are three things the Nhost CLI and the GitHub integration track and apply
 to production:
 
-- Database migrations
+- Database Migrations
 - Hasura Metadata
 - Serverless Functions
 
@@ -239,7 +220,7 @@ Settings in `nhost/config.yaml` are not being applied to production. They only w
 Database changes are tracked and managed through migrations.
 
 :::tip
-It's important that you use the Hasura console to make database changes. Indeed, with the Hasura console, DB migration files are generated incrementally to track changes automatically for you.
+You must use the Hasura Console to make database changes. With the Hasura Console, database migration files are automatically generated incrementally to track database changes for you.
 :::
 
 To demonstrate how to make database changes, let's create a new table called
@@ -250,14 +231,15 @@ To demonstrate how to make database changes, let's create a new table called
 - `authorId` (type UUID),
 - `createdAt` (type Timestamp and default `now()`)
 
-In the Hasura console, head over to the **data** tab section and click on the
+In the Hasura Console, go to the **DATA** tab section and click on the
 PostgreSQL database (from the left side navigation) that Nhost provides us.
 
-Click on the **public** schema and the **Create Table** button.
+Click on the **public** schema and then the **Create Table** button.
 
 ![Create Table](/img/architecture/cli/create-table-step-1.png)
 
-Then, enter the values for creating the `messages` table as mentioned above.
+Enter the values for creating the `messages` table as mentioned above.
+
 Also, specify the `id` column as the primary key of the table, and link the
 `authorId` column to the `users.id` column using a foreign key to link the
 `users` and `messages` tables together.
@@ -280,7 +262,7 @@ drwxr-xr-x  3 user  staff   96 Apr 27 17:06 ..
 drwxr-xr-x  4 user  staff  128 Apr 27 17:06 1651071963431_create_table_public_messages
 ```
 
-However, note that this database migration has only been applied locally. In
+Note that this database migration has only been applied locally. In
 other words, the `messages` table does not (yet) exists in production.
 
 To apply the local changes to production, check out the
@@ -338,12 +320,12 @@ insert_permissions:
     role: user
 ```
 
-### Serverless functions
+### Serverless Functions
 
-Now let's create a serverless function before we push all changes to GitHub so
+Now let's create a Serverless Function before we push all changes to GitHub so
 Nhost can deploy them to production.
 
-For this guide, let's create a simple serverless function that will return the
+For this guide, let's create a Serverless Function that will return the
 current date-time when called.
 
 First, make sure to install `express`, which is required for serverless

docs/docs/platform/quickstarts/nextjs.mdx

@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem'
 
 ## Introduction
 
-This quickstart guide provides the steps you need to build a simple Next.js app
+This quickstart provides the steps you need to build a Next.js app
 powered by Nhost for the backend. It includes:
 
 - Database: [PostgreSQL](https://www.postgresql.org/)
@@ -19,7 +19,7 @@ powered by Nhost for the backend. It includes:
 - Authentication: [Hasura Auth](https://github.com/nhost/hasura-auth/)
 - Storage: [Hasura Storage](https://hub.docker.com/r/nhost/hasura-storage)
 
-By the end of this guide, you'll have a full-stack app that allows users to log
+By the end of this guide, you'll have a full-stack app that allows users to sign
 in to access a protected dashboard and update their profile information.
 
 ## Prerequisites
@@ -33,12 +33,12 @@ You'll need **Node.js** version 12 or later: [install it from here](https://node
 
 ### Create a new Nhost app
 
-import CreateApp from '@site/src/components/create-nhost-app.mdx'
+import CreateApp from '@site/src/components/create-nhost-project.mdx'
 
 <CreateApp />
 
 :::info
-You can also connect your Nhost app to a GitHub repository. When you do this, any updates you push to your code will automatically be deployed. [Learn more](https://docs.nhost.io/platform/github-integration).
+You can also connect your Nhost project to a GitHub repository. When you do this, any updates you push to your code will automatically be deployed. [Learn more](https://docs.nhost.io/platform/github-integration).
 :::
 
 ## Initialize the app
@@ -153,13 +153,13 @@ function MyApp({ Component, pageProps }) {
 Finally, store the environment variables for `subdomain` and `region` in `.env.development`:
 
 ```yaml title=".env.development"
-NEXT_PUBLIC_NHOST_SUBDOMAIN=YOUR_NHOST_APP_SUBDOMAIN
-NEXT_PUBLIC_NHOST_REGION=YOUR_NHOST_APP_REGION
+NEXT_PUBLIC_NHOST_SUBDOMAIN=[subdomain]
+NEXT_PUBLIC_NHOST_REGION=[region]
 ```
 
-You find your Nhost app's subdomain and region in [the app dashboard](https://app.nhost.io):
+You find your Nhost project's `subdomain` and `region` in the [project overview](https://app.nhost.io):
 
-![Nhost App Dashboard](/img/quickstarts/app-dashboard.png)
+![Project Overview](/img/quickstarts/app-dashboard.png)
 
 :::caution
 Don't forget to restart your Next.js server after saving your `.env.development`

docs/docs/platform/quickstarts/react.mdx

@@ -31,14 +31,14 @@ You'll need **Node.js** version 14 or later: [install it from here](https://node
 
 ## Project setup
 
-### Create a new Nhost app
+### Create a new Nhost project
 
-import CreateApp from '@site/src/components/create-nhost-app.mdx'
+import CreateProject from '@site/src/components/create-nhost-project.mdx'
 
-<CreateApp />
+<CreateProject />
 
 :::info
-You can also connect your Nhost app to a GitHub repository. When you do this, any updates you push to your code will automatically be deployed. [Learn more](https://docs.nhost.io/platform/github-integration).
+You can also connect your Nhost project to a GitHub repository. When you do this, any updates you push to your code will automatically be deployed. [Learn more](https://docs.nhost.io/platform/github-integration).
 :::
 
 ## Initialize the app
@@ -147,13 +147,13 @@ Finally, make sure to create an environment variable named
 `REACT_APP_NHOST_SUBDOMAIN` and `REACT_APP_NHOST_REGION` to store your Nhost domain details:
 
 ```yaml title=".env.local"
-REACT_APP_NHOST_SUBDOMAIN=YOUR_NHOST_APP_SUBDOMAIN
-REACT_APP_NHOST_REGION=YOUR_NHOST_APP_REGION
+REACT_APP_NHOST_SUBDOMAIN=[subdomain]
+REACT_APP_NHOST_REGION=[region]
 ```
 
-You find your Nhost app's subdomain and region in [the app dashboard](https://app.nhost.io):
+You find your Nhost project's `subdomain` and `region` in the [project overview](https://app.nhost.io):
 
-![Nhost App Dashboard](/img/quickstarts/app-dashboard.png)
+![Project Overview](/img/quickstarts/app-dashboard.png)
 
 :::caution
 Don't forget to restart your React server after saving your `.env.local`

docs/docs/platform/quickstarts/redwoodjs.mdx

@@ -44,27 +44,16 @@ If your system versions do not meet both requirements, the RedwoodJS installatio
 
 ### Create a new Nhost app
 
-First things first, we need to create a new Nhost project.
+import CreateApp from '@site/src/components/create-nhost-project.mdx'
 
-So, log in to your Nhost dashboard and click the **Create your first app**
-button.
-
-![nhost-first-app](/img/quickstarts/create-app-step-1.png)
-
-Next, give your new Nhost app a name, select a geographic region for your Nhost
-services and click **Create App**.
-
-![nhost-first-app](/img/quickstarts/create-app-step-2.png)
-
-After a few seconds, you should get a PostgreSQL database, a GraphQL API with
-Hasura, file storage, and authentication set up.
+<CreateApp />
 
 Finally, update your client login URL from your Nhost dashboard as the local RedwoodJS server starts on port `8910` instead of the usual `3000` port you may be used to with a regular React app.
 
 ![nhost-first-app](/img/quickstarts/create-app-step-3.png)
 
 :::info
-You can also connect your Nhost app to a GitHub repository. When you do this, any updates you push to your code will automatically be deployed. [Learn more](https://docs.nhost.io/platform/github-integration).
+You can also connect your Nhost project to a GitHub repository. When you do this, any updates you push to your code will automatically be deployed. [Learn more](https://docs.nhost.io/platform/github-integration).
 :::
 
 ## Initialize the app
@@ -179,13 +168,13 @@ That prop avoids having an additional request to fetch the current user.
 Next, store the environment variables for `subdomain` and `region` in `.env`:
 
 ```yaml title=".env"
-NHOST_SUBDOMAIN=YOUR_NHOST_APP_SUBDOMAIN
-NHOST_REGION=YOUR_NHOST_APP_REGION
+NHOST_SUBDOMAIN=[subdomain]
+NHOST_REGION=[region]
 ```
 
-You find your Nhost app's subdomain and region in [the app dashboard](https://app.nhost.io):
+You find your Nhost project's `subdomain` and `region` in the [project overview](https://app.nhost.io):
 
-![Nhost App Dashboard](/img/quickstarts/app-dashboard.png)
+![Project Overview](/img/quickstarts/app-dashboard.png)
 
 Finally, we need to customize the GraphQL Endpoint for our RedwoodJS app. Indeed, by default, RedwoodJS provides a built-in GraphQL server under the `api` side. However, as we already have our own GraphQL server through Nhost and Hasura, we do not need it.
 

docs/docs/platform/quickstarts/vue.mdx

@@ -39,12 +39,12 @@ You'll need **Node.js** version 14 or later: [install it from here](https://node
 
 ### Create a new Nhost app
 
-import CreateApp from '@site/src/components/create-nhost-app.mdx'
+import CreateApp from '@site/src/components/create-nhost-project.mdx'
 
 <CreateApp />
 
 :::info
-You can also connect your Nhost app to a GitHub repository. When you do this, any updates you push to your code will automatically be deployed. [Learn more](https://docs.nhost.io/platform/github-integration).
+You can also connect your Nhost project to a GitHub repository. When you do this, any updates you push to your code will automatically be deployed. [Learn more](https://docs.nhost.io/platform/github-integration).
 :::
 
 ## Initialize the app
@@ -174,13 +174,13 @@ app.mount('#app')
 Finally, store the environment variables for `subdomain` and `region` in `.env`:
 
 ```yaml title=".env.development"
-VITE_NHOST_SUBDOMAIN=YOUR_NHOST_APP_SUBDOMAIN
-VITE_NHOST_REGION=YOUR_NHOST_APP_REGION
+VITE_NHOST_SUBDOMAIN=[subdomain]
+VITE_NHOST_REGION=[region]
 ```
 
-You find your Nhost app's subdomain and region in [the app dashboard](https://app.nhost.io):
+You find your Nhost project's `subdomain` and `region` in the [project overview](https://app.nhost.io):
 
-![Nhost App Dashboard](/img/quickstarts/app-dashboard.png)
+![Project Overview](/img/quickstarts/app-dashboard.png)
 
 ## Build the app
 

docs/docs/platform/serverless-functions.mdx

@@ -15,7 +15,7 @@ Serverless functions can be used to handle [event triggers](/platform/database/e
 
 ## Creating a Serverless Function
 
-Every `.js` (JavaScript) and `.ts` (TypeScript) file in the `functions/` folder of your Nhost app is its own serverless function.
+Every `.js` (JavaScript) and `.ts` (TypeScript) file in the `functions/` folder of your Nhost project is its own serverless function.
 
 <Tabs groupId="language">
   <TabItem value="ts" label="TypeScript" default>
@@ -30,7 +30,7 @@ export default (req: Request, res: Response) => {
 
 :::info
 
-You **MUST** install `express` locally in the base directory of your Nhost app.
+You **MUST** install `express` locally in the base directory of your Nhost project.
 
 ```bash
 npm install -d express @types/express
@@ -51,7 +51,7 @@ export default (req, res) => {
 
 :::info
 
-You **MUST** install `express` locally in the base directory of your Nhost app.
+You **MUST** install `express` locally in the base directory of your Nhost project.
 
 ```bash
 npm install -d express
@@ -76,12 +76,12 @@ HTTP endpoints are automatically generated based on the file structure inside `f
 
 Here's an example of four serverless functions with their files and their HTTP endpoints:
 
-| File                        | HTTP Endpoint                                                 |
-| --------------------------- | ------------------------------------------------------------- |
-| `functions/index.js`        | `https://[app-subdomain].nhost.run/v1/functions/`             |
-| `functions/users/index.ts`  | `https://[app-subdomain].nhost.run/v1/functions/users`        |
-| `functions/users/active.ts` | `https://[app-subdomain].nhost.run/v1/functions/users/active` |
-| `functions/my-company.js`   | `https://[app-subdomain].nhost.run/v1/functions/my-company`   |
+| File                        | HTTP Endpoint                                                     |
+| --------------------------- | ----------------------------------------------------------------- |
+| `functions/index.js`        | `https://[project-subdomain].nhost.run/v1/functions/`             |
+| `functions/users/index.ts`  | `https://[project-subdomain].nhost.run/v1/functions/users`        |
+| `functions/users/active.ts` | `https://[project-subdomain].nhost.run/v1/functions/users/active` |
+| `functions/my-company.js`   | `https://[project-subdomain].nhost.run/v1/functions/my-company`   |
 
 ---
 
@@ -103,4 +103,4 @@ All serverless functions in production are running Node.js version 14.x.
 
 ## Regions
 
-Serverless Functions are always deployed to the same region as your app.
+Serverless Functions are always deployed to the same region as your project.

docs/docs/platform/storage.mdx

@@ -20,7 +20,7 @@ File metadata is stored in your database in the `files` table in the `storage` s
 - Create GraphQL relationships between files and your database tables.
 
 :::warning
-Don't modify the database schema, nor GraphQL root fields in any of the tables in the `storage` schema. 
+Don't modify the database schema, nor GraphQL root fields in any of the tables in the `storage` schema.
 :::
 
 :::tip
@@ -28,8 +28,8 @@ You're allowed to add and modify the following:
 
 - GraphQL Relationships
 - Permissions
-:::
 
+:::
 
 ### Upload File
 
@@ -159,16 +159,11 @@ Permissions to upload, download, and delete files are managed through Hasura's p
 
 ### Upload
 
-To upload a file, a user must have the **`insert` permission** to the `storage.files` table. The following columns must be allowed to insert:
-
-- `id`
-- `bucket_id`
-- `name`
-- `mime_type`
+To upload a file, a user must have the **`insert` permission** to the `storage.files` table. The `id` column must be granted.
 
 ### Download
 
-To download a file, a user must have the **`select` permission** to the `storage.files` table. Only the `id` column is required, but we recommend allowing to select all columns. 
+To download a file, a user must have the **`select` permission** to the `storage.files` table. **All** columns must be granted.
 
 ### Delete
 
@@ -200,31 +195,35 @@ Let's say you want to build a CRM system and you want to store files for custome
 Start with, you would have two tables:
 
 1. `customers` - Customer data.
-2. `customer_files` - What file belongs to what customer.
+2. `customer_files` - What file belongs to what customer
 
-```text 
+```text
 - customers
   - id
   - name
   - address
+
 customer_files
   - id
   - customer_id (Foreign Key to `customers.id`)
   - file_id (Foreign Key to `storage.files.id`)
 ```
 
-You would also create [Hasura Relationships](https://hasura.io/docs/latest/graphql/core/databases/postgres/schema/table-relationships/index/) (GraphQL relationships) between between `customers` and `customer_files` and between `customer_files` and `storage.files`.
+You would also create a [Hasura Relationship](https://hasura.io/docs/latest/graphql/core/databases/postgres/schema/table-relationships/index/) (GraphQL relationship) between between `customers` and `customer_files` and between `customer_files` and `storage.files`.
 
 With the two tables and GraphQL relationships in place, you can query customers and the customer's files like this:
 
 ```graphql
 query {
-  customers { # customers table
+  customers {
+    # customers table
     id
     name
-    customer_files { # customer_files tabel
+    customer_files {
+      # customer_files table
       id
-      file { # storage.files table
+      file {
+        # storage.files table
         id
         name
         size
@@ -239,6 +238,6 @@ The file upload process would be as follows:
 
 1. Upload a file.
 2. Get the returned file id.
-3. Insert the file `id` and the customer's `id` into the `customer_files` table.
+3. Insert (GraphQL Mutation) the file `id` and the customer's `id` into the `customer_files` table.
 
-This would allow you to upload and download files belonging to specific customers in your CRM system.
+This would allow you to upload and download files belonging to specific customers in your CRM system.

docs/docs/reference/cli/init.mdx

@@ -3,15 +3,15 @@ title: 'init'
 sidebar_position: 1
 ---
 
-Intialize a local Nhost app in the current working directory.
+Initialize a local Nhost project in the current working directory.
 
 ```
 nhost init
 ```
 
-If you already have a Nhost app in Nhost Cloud you can use that app as a starting point by appending `--remote` to the command.
+If you already have a Nhost project in Nhost Cloud you can use that project as a starting point by appending `--remote` to the command.
 
-This will pull the database migrations and Hasura metadata from the Nhost Cloud app locally for you to use as a starting point.
+This will pull the database migrations and Hasura metadata from the Nhost Cloud project locally for you to use as a starting point.
 
 ```
 nhost init --remote

docs/docs/reference/cli/link.mdx

@@ -3,7 +3,7 @@ title: 'link'
 sidebar_position: 4
 ---
 
-Link the local Nhost app in your working directory to an app in Nhost Cloud.
+Link the local Nhost project in your working directory to a project in Nhost Cloud.
 
 ```bash
 nhost link

docs/docs/reference/cli/list.mdx

@@ -3,7 +3,7 @@ title: 'list'
 sidebar_position: 7
 ---
 
-List all your Nhost apps in Nhost Cloud.
+List all your Nhost projects in Nhost Cloud.
 
 ```bash
 nhost list

docs/docs/reference/cli/up.mdx

@@ -3,7 +3,7 @@ title: 'up'
 sidebar_position: 2
 ---
 
-Launch the development environment for your app. Once the environment is up, the command will:
+Launch the development environment for your project. Once the environment is up, the command will:
 
 - Apply database migrations.
 - Apply the Hasura metadata.

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/01-sign-up.mdx

@@ -4,7 +4,7 @@ title: signUp()
 sidebar_label: signUp()
 slug: /reference/javascript/auth/sign-up
 description: Use `nhost.auth.signUp` to sign up a user using email and password. If you want to sign up a user using passwordless email (Magic Link), SMS, or an OAuth provider, use the `signIn` function instead.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L103
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L107
 ---
 
 # `signUp()`
@@ -22,12 +22,6 @@ nhost.auth.signUp({
 
 ---
 
-**<span className="parameter-name">\_\_namedParameters</span>** <span className="optional-status">required</span> [`SignUpEmailPasswordParams`](/reference/docgen/javascript/auth/types/sign-up-email-password-params)
-
-| Property                                                                                                 | Type            | Required | Notes |
-| :------------------------------------------------------------------------------------------------------- | :-------------- | :------: | :---- |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>password</span> | `string`        |    ✔️    |       |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>email</span>    | `string`        |    ✔️    |       |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>options</span>  | `SignUpOptions` |          |       |
+**<span className="parameter-name">params</span>** <span className="optional-status">required</span> [`SignUpParams`](/reference/docgen/javascript/auth/types/sign-up-params)
 
 ---

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/02-sign-in.mdx

@@ -4,7 +4,7 @@ title: signIn()
 sidebar_label: signIn()
 slug: /reference/javascript/auth/sign-in
 description: Use `nhost.auth.signIn` to sign in a user using email and password, passwordless (email or sms) or an external provider. `signIn` can be used to sign in a user in various ways depending on the parameters.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L146
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L156
 ---
 
 # `signIn()`
@@ -53,8 +53,8 @@ nhost.auth.signIn({ email: 'joe@example.com' })
 
 ```ts
 // [step 1/2] Passwordless sign in using SMS
-nhost.auth.signIn({ phoneNumber: '001122334455' })
+nhost.auth.signIn({ phoneNumber: '+11233213123' })
 
 // [step 2/2] Finish passwordless sign in using SMS (OTP)
-nhost.auth.signIn({ phoneNumber: '001122334455', otp: '123456' })
+nhost.auth.signIn({ phoneNumber: '+11233213123', otp: '123456' })
 ```

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/03-sign-out.mdx

@@ -4,7 +4,7 @@ title: signOut()
 sidebar_label: signOut()
 slug: /reference/javascript/auth/sign-out
 description: Use `nhost.auth.signOut` to sign out the user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L231
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L252
 ---
 
 # `signOut()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/04-reset-password.mdx

@@ -4,7 +4,7 @@ title: resetPassword()
 sidebar_label: resetPassword()
 slug: /reference/javascript/auth/reset-password
 description: Use `nhost.auth.resetPassword` to reset the password for a user. This will send a reset-password link in an email to the user. When the user clicks the reset-password link the user is automatically signed-in. Once signed-in, the user can change their password using `nhost.auth.changePassword()`.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L247
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L268
 ---
 
 # `resetPassword()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/05-change-password.mdx

@@ -3,13 +3,13 @@
 title: changePassword()
 sidebar_label: changePassword()
 slug: /reference/javascript/auth/change-password
-description: Use `nhost.auth.changePassword` to change the password for the user. The old password is not needed.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L263
+description: Use `nhost.auth.changePassword` to change the password for the signed-in user. The old password is not needed. In case the user is not signed-in, a password reset ticket needs to be provided.
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L284
 ---
 
 # `changePassword()`
 
-Use `nhost.auth.changePassword` to change the password for the user. The old password is not needed.
+Use `nhost.auth.changePassword` to change the password for the signed-in user. The old password is not needed. In case the user is not signed-in, a password reset ticket needs to be provided.
 
 ```ts
 nhost.auth.changePassword({ newPassword: 'new-secret-password' })
@@ -24,5 +24,6 @@ nhost.auth.changePassword({ newPassword: 'new-secret-password' })
 | Property                                                                                                    | Type     | Required | Notes |
 | :---------------------------------------------------------------------------------------------------------- | :------- | :------: | :---- |
 | <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>newPassword</span> | `string` |    ✔️    |       |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>ticket</span>      | `string` |          |       |
 
 ---

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/06-send-verification-email.mdx

@@ -4,7 +4,7 @@ title: sendVerificationEmail()
 sidebar_label: sendVerificationEmail()
 slug: /reference/javascript/auth/send-verification-email
 description: Use `nhost.auth.sendVerificationEmail` to send a verification email to the specified email. The email contains a verification-email link. When the user clicks the verification-email link their email is verified.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L279
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L303
 ---
 
 # `sendVerificationEmail()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/07-change-email.mdx

@@ -4,7 +4,7 @@ title: changeEmail()
 sidebar_label: changeEmail()
 slug: /reference/javascript/auth/change-email
 description: Use `nhost.auth.changeEmail` to change a user's email. This will send a confirm-email-change link in an email to the new email. Once the user clicks on the confirm-email-change link the email will be change to the new email.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L298
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L322
 ---
 
 # `changeEmail()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/08-deanonymize.mdx

@@ -4,7 +4,7 @@ title: deanonymize()
 sidebar_label: deanonymize()
 slug: /reference/javascript/auth/deanonymize
 description: Use `nhost.auth.deanonymize` to deanonymize a user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L314
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L338
 ---
 
 # `deanonymize()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/09-add-security-key.mdx

@@ -0,0 +1,22 @@
+---
+# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
+title: addSecurityKey()
+sidebar_label: addSecurityKey()
+slug: /reference/javascript/auth/add-security-key
+description: Use `nhost.auth.addSecurityKey to add a security key to the user, using the WebAuthn API.
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L376
+---
+
+# `addSecurityKey()`
+
+Use `nhost.auth.addSecurityKey to add a security key to the user, using the WebAuthn API.
+
+## Parameters
+
+---
+
+**<span className="parameter-name">nickname</span>** <span className="optional-status">optional</span> `string`
+
+optional human-readable nickname for the security key
+
+---

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/10-on-token-changed.mdx

@@ -4,7 +4,7 @@ title: onTokenChanged()
 sidebar_label: onTokenChanged()
 slug: /reference/javascript/auth/on-token-changed
 description: Use `nhost.auth.onTokenChanged` to add a custom function that runs every time the access or refresh token is changed.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L357
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L394
 ---
 
 # `onTokenChanged()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/11-on-auth-state-changed.mdx

@@ -4,7 +4,7 @@ title: onAuthStateChanged()
 sidebar_label: onAuthStateChanged()
 slug: /reference/javascript/auth/on-auth-state-changed
 description: Use `nhost.auth.onAuthStateChanged` to add a custom function that runs every time the authentication status of the user changes. E.g. add a custom function that runs every time the authentication status changes from signed-in to signed-out.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L392
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L429
 ---
 
 # `onAuthStateChanged()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/12-is-authenticated.mdx

@@ -4,7 +4,7 @@ title: isAuthenticated()
 sidebar_label: isAuthenticated()
 slug: /reference/javascript/auth/is-authenticated
 description: Use `nhost.auth.isAuthenticated` to check if the user is authenticated or not.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L434
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L471
 ---
 
 # `isAuthenticated()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/13-is-authenticated-async.mdx

@@ -4,7 +4,7 @@ title: isAuthenticatedAsync()
 sidebar_label: isAuthenticatedAsync()
 slug: /reference/javascript/auth/is-authenticated-async
 description: Use `nhost.auth.isAuthenticatedAsync` to wait (await) for any internal authentication network requests to finish and then return the authentication status.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L452
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L489
 ---
 
 # `isAuthenticatedAsync()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/14-get-authentication-status.mdx

@@ -4,7 +4,7 @@ title: getAuthenticationStatus()
 sidebar_label: getAuthenticationStatus()
 slug: /reference/javascript/auth/get-authentication-status
 description: Use `nhost.auth.getAuthenticationStatus` to get the authentication status of the user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L478
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L515
 ---
 
 # `getAuthenticationStatus()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/15-get-access-token.mdx

@@ -4,7 +4,7 @@ title: getAccessToken()
 sidebar_label: getAccessToken()
 slug: /reference/javascript/auth/get-access-token
 description: Use `nhost.auth.getAccessToken` to get the access token of the user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L508
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L545
 ---
 
 # `getAccessToken()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/16-get-decoded-access-token.mdx

@@ -4,7 +4,7 @@ title: getDecodedAccessToken()
 sidebar_label: getDecodedAccessToken()
 slug: /reference/javascript/auth/get-decoded-access-token
 description: Use `nhost.auth.getDecodedAccessToken` to get the decoded access token of the user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L523
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L560
 ---
 
 # `getDecodedAccessToken()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/17-get-hasura-claims.mdx

@@ -4,7 +4,7 @@ title: getHasuraClaims()
 sidebar_label: getHasuraClaims()
 slug: /reference/javascript/auth/get-hasura-claims
 description: Use `nhost.auth.getHasuraClaims` to get the Hasura claims of the user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L540
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L577
 ---
 
 # `getHasuraClaims()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/18-get-hasura-claim.mdx

@@ -4,7 +4,7 @@ title: getHasuraClaim()
 sidebar_label: getHasuraClaim()
 slug: /reference/javascript/auth/get-hasura-claim
 description: Use `nhost.auth.getHasuraClaim` to get the value of a specific Hasura claim of the user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L558
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L595
 ---
 
 # `getHasuraClaim()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/19-refresh-session.mdx

@@ -4,7 +4,7 @@ title: refreshSession()
 sidebar_label: refreshSession()
 slug: /reference/javascript/auth/refresh-session
 description: Use `nhost.auth.refreshSession` to refresh the session with either the current internal refresh token or an external refresh token.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L581
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L618
 ---
 
 # `refreshSession()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/20-get-session.mdx

@@ -4,7 +4,7 @@ title: getSession()
 sidebar_label: getSession()
 slug: /reference/javascript/auth/get-session
 description: Use `nhost.auth.getSession()` to get the session of the user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L625
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L659
 ---
 
 # `getSession()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/content/21-get-user.mdx

@@ -4,7 +4,7 @@ title: getUser()
 sidebar_label: getUser()
 slug: /reference/javascript/auth/get-user
 description: Use `nhost.auth.getUser()` to get the signed-in user.
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L640
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L674
 ---
 
 # `getUser()`

docs/docs/reference/docgen/javascript/auth/content/hasura-auth-client/index.mdx

@@ -4,7 +4,7 @@ title: HasuraAuthClient
 sidebar_label: Auth
 description: No description provided.
 slug: /reference/javascript/auth
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L60
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/hasura-auth-client.ts#L64
 ---
 
 # `HasuraAuthClient`

docs/docs/reference/docgen/javascript/auth/types/api-change-email-response.mdx

@@ -1,18 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiChangeEmailResponse
-sidebar_label: ApiChangeEmailResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L181
----
-
-# `ApiChangeEmailResponse`
-
-## Parameters
-
----
-
-**<span className="parameter-name">error</span>** <span className="optional-status">required</span> `null` | `ErrorPayload`
-
----

docs/docs/reference/docgen/javascript/auth/types/api-change-password-response.mdx

@@ -1,18 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiChangePasswordResponse
-sidebar_label: ApiChangePasswordResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L173
----
-
-# `ApiChangePasswordResponse`
-
-## Parameters
-
----
-
-**<span className="parameter-name">error</span>** <span className="optional-status">required</span> `null` | `ErrorPayload`
-
----

docs/docs/reference/docgen/javascript/auth/types/api-deanonymize-response.mdx

@@ -1,18 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiDeanonymizeResponse
-sidebar_label: ApiDeanonymizeResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L185
----
-
-# `ApiDeanonymizeResponse`
-
-## Parameters
-
----
-
-**<span className="parameter-name">error</span>** <span className="optional-status">required</span> `null` | `ErrorPayload`
-
----

docs/docs/reference/docgen/javascript/auth/types/api-refresh-token-response.mdx

@@ -1,16 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiRefreshTokenResponse
-sidebar_label: ApiRefreshTokenResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L161
----
-
-# `ApiRefreshTokenResponse`
-
-```ts
-type ApiRefreshTokenResponse =
-  | { session: null; error: ErrorPayload }
-  | { session: Session; error: null }
-```

docs/docs/reference/docgen/javascript/auth/types/api-reset-password-response.mdx

@@ -1,18 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiResetPasswordResponse
-sidebar_label: ApiResetPasswordResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L169
----
-
-# `ApiResetPasswordResponse`
-
-## Parameters
-
----
-
-**<span className="parameter-name">error</span>** <span className="optional-status">required</span> `null` | `ErrorPayload`
-
----

docs/docs/reference/docgen/javascript/auth/types/api-send-verification-email-response.mdx

@@ -1,18 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiSendVerificationEmailResponse
-sidebar_label: ApiSendVerificationEmailResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L177
----
-
-# `ApiSendVerificationEmailResponse`
-
-## Parameters
-
----
-
-**<span className="parameter-name">error</span>** <span className="optional-status">required</span> `null` | `ErrorPayload`
-
----

docs/docs/reference/docgen/javascript/auth/types/api-sign-in-data.mdx

@@ -1,29 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiSignInData
-sidebar_label: ApiSignInData
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L150
----
-
-# `ApiSignInData`
-
-## Parameters
-
----
-
-**<span className="parameter-name">session</span>** <span className="optional-status">required</span> [`Session`](/reference/docgen/javascript/auth/types/session)
-
-| Property                                                                                                 | Type                                                             | Required | Notes |
-| :------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------- | :------: | :---- |
-| <span className="parameter-name"><span className="light-grey">session.</span>user</span>                 | `null` \| [`User`](/reference/docgen/javascript/auth/types/user) |    ✔️    |       |
-| <span className="parameter-name"><span className="light-grey">session.</span>refreshToken</span>         | `string`                                                         |    ✔️    |       |
-| <span className="parameter-name"><span className="light-grey">session.</span>accessTokenExpiresIn</span> | `number`                                                         |    ✔️    |       |
-| <span className="parameter-name"><span className="light-grey">session.</span>accessToken</span>          | `string`                                                         |    ✔️    |       |
-
----
-
-**<span className="parameter-name">mfa</span>** <span className="optional-status">required</span> `null` | [`Mfa`](/reference/docgen/javascript/auth/types/mfa)
-
----

docs/docs/reference/docgen/javascript/auth/types/api-sign-in-response.mdx

@@ -1,16 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiSignInResponse
-sidebar_label: ApiSignInResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L154
----
-
-# `ApiSignInResponse`
-
-```ts
-type ApiSignInResponse =
-  | { data: ApiSignInData; error: null }
-  | { data: null; error: ErrorPayload }
-```

docs/docs/reference/docgen/javascript/auth/types/api-sign-out-response.mdx

@@ -1,18 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiSignOutResponse
-sidebar_label: ApiSignOutResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L165
----
-
-# `ApiSignOutResponse`
-
-## Parameters
-
----
-
-**<span className="parameter-name">error</span>** <span className="optional-status">required</span> `null` | `ErrorPayload`
-
----

docs/docs/reference/docgen/javascript/auth/types/api-sign-up-email-password-response.mdx

@@ -1,16 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: ApiSignUpEmailPasswordResponse
-sidebar_label: ApiSignUpEmailPasswordResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L146
----
-
-# `ApiSignUpEmailPasswordResponse`
-
-```ts
-type ApiSignUpEmailPasswordResponse =
-  | { session: null; error: ErrorPayload }
-  | { session: Session; error: null }
-```

docs/docs/reference/docgen/javascript/auth/types/auth-change-event.mdx

@@ -4,7 +4,7 @@ title: AuthChangeEvent
 sidebar_label: AuthChangeEvent
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L134
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L118
 ---
 
 # `AuthChangeEvent`

docs/docs/reference/docgen/javascript/auth/types/auth-changed-function.mdx

@@ -4,7 +4,7 @@ title: AuthChangedFunction
 sidebar_label: AuthChangedFunction
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L136
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L120
 ---
 
 # `AuthChangedFunction`
@@ -12,6 +12,6 @@ custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-j
 ```ts
 type AuthChangedFunction = () => (
   event: AuthChangeEvent,
-  session: Session | null
+  session: NhostSession | null
 ) => void
 ```

docs/docs/reference/docgen/javascript/auth/types/change-email-params.mdx

@@ -4,7 +4,7 @@ title: ChangeEmailParams
 sidebar_label: ChangeEmailParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L105
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L99
 ---
 
 # `ChangeEmailParams`

docs/docs/reference/docgen/javascript/auth/types/change-password-params.mdx

@@ -4,7 +4,7 @@ title: ChangePasswordParams
 sidebar_label: ChangePasswordParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L96
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L89
 ---
 
 # `ChangePasswordParams`
@@ -16,3 +16,7 @@ custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-j
 **<span className="parameter-name">newPassword</span>** <span className="optional-status">required</span> `string`
 
 ---
+
+**<span className="parameter-name">ticket</span>** <span className="optional-status">optional</span> `string`
+
+---

docs/docs/reference/docgen/javascript/auth/types/common-sign-up-params.mdx

@@ -1,18 +1,18 @@
 ---
 # ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: Headers
-sidebar_label: Headers
+title: CommonSignUpParams
+sidebar_label: CommonSignUpParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L139
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L25
 ---
 
-# `Headers`
+# `CommonSignUpParams`
 
 ## Parameters
 
 ---
 
-**<span className="parameter-name">Authorization</span>** <span className="optional-status">optional</span> `string`
+**<span className="parameter-name">options</span>** <span className="optional-status">optional</span> `SignUpOptions`
 
 ---

docs/docs/reference/docgen/javascript/auth/types/deanonymize-params.mdx

@@ -4,14 +4,14 @@ title: DeanonymizeParams
 sidebar_label: DeanonymizeParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L110
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L104
 ---
 
 # `DeanonymizeParams`
 
 ```ts
 type DeanonymizeParams =
-  | ({ signInMethod: 'email-password' } & SignUpParams)
+  | ({ signInMethod: 'email-password' } & SignUpEmailPasswordParams)
   | ({
       signInMethod: 'passwordless'
       connection: 'email'

docs/docs/reference/docgen/javascript/auth/types/nhost-auth-constructor-params.mdx

@@ -4,7 +4,7 @@ title: NhostAuthConstructorParams
 sidebar_label: NhostAuthConstructorParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L15
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L17
 ---
 
 # `NhostAuthConstructorParams`

docs/docs/reference/docgen/javascript/auth/types/on-token-changed-function.mdx

@@ -4,11 +4,11 @@ title: OnTokenChangedFunction
 sidebar_label: OnTokenChangedFunction
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L138
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L122
 ---
 
 # `OnTokenChangedFunction`
 
 ```ts
-type OnTokenChangedFunction = () => (session: Session | null) => void
+type OnTokenChangedFunction = () => (session: NhostSession | null) => void
 ```

docs/docs/reference/docgen/javascript/auth/types/provider.mdx

@@ -4,7 +4,7 @@ title: Provider
 sidebar_label: Provider
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/core/src/types.ts#L140
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/core/src/types.ts#L153
 ---
 
 # `Provider`
@@ -22,4 +22,7 @@ type Provider =
   | 'strava'
   | 'gitlab'
   | 'bitbucket'
+  | 'discord'
+  | 'twitch'
+  | 'workos'
 ```

docs/docs/reference/docgen/javascript/auth/types/reset-password-params.mdx

@@ -4,7 +4,7 @@ title: ResetPasswordParams
 sidebar_label: ResetPasswordParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L91
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L84
 ---
 
 # `ResetPasswordParams`

docs/docs/reference/docgen/javascript/auth/types/send-verification-email-params.mdx

@@ -4,7 +4,7 @@ title: SendVerificationEmailParams
 sidebar_label: SendVerificationEmailParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L100
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L94
 ---
 
 # `SendVerificationEmailParams`

docs/docs/reference/docgen/javascript/auth/types/session.mdx

@@ -1,30 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: Session
-sidebar_label: Session
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L23
----
-
-# `Session`
-
-## Parameters
-
----
-
-**<span className="parameter-name">accessToken</span>** <span className="optional-status">required</span> `string`
-
----
-
-**<span className="parameter-name">accessTokenExpiresIn</span>** <span className="optional-status">required</span> `number`
-
----
-
-**<span className="parameter-name">refreshToken</span>** <span className="optional-status">required</span> `string`
-
----
-
-**<span className="parameter-name">user</span>** <span className="optional-status">required</span> `null` | [`User`](/reference/docgen/javascript/auth/types/user)
-
----

docs/docs/reference/docgen/javascript/auth/types/sign-in-email-password-otp-params.mdx

@@ -4,7 +4,7 @@ title: SignInEmailPasswordOtpParams
 sidebar_label: SignInEmailPasswordOtpParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L59
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L46
 ---
 
 # `SignInEmailPasswordOtpParams`

docs/docs/reference/docgen/javascript/auth/types/sign-in-email-password-params.mdx

@@ -4,7 +4,7 @@ title: SignInEmailPasswordParams
 sidebar_label: SignInEmailPasswordParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L54
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L41
 ---
 
 # `SignInEmailPasswordParams`

docs/docs/reference/docgen/javascript/auth/types/sign-in-params.mdx

@@ -4,7 +4,7 @@ title: SignInParams
 sidebar_label: SignInParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L83
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L75
 ---
 
 # `SignInParams`
@@ -14,6 +14,7 @@ type SignInParams =
   | SignInEmailPasswordParams
   | SignInEmailPasswordOtpParams
   | SignInPasswordlessEmailParams
+  | SignInPasswordlessSecurityKeyParams
   | SignInPasswordlessSmsOtpParams
   | SignInPasswordlessSmsParams
   | SignInWithProviderOptions

docs/docs/reference/docgen/javascript/auth/types/sign-in-passwordless-email-params.mdx

@@ -4,7 +4,7 @@ title: SignInPasswordlessEmailParams
 sidebar_label: SignInPasswordlessEmailParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L64
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L51
 ---
 
 # `SignInPasswordlessEmailParams`

docs/docs/reference/docgen/javascript/auth/types/sign-in-passwordless-security-key-params.mdx

@@ -0,0 +1,22 @@
+---
+# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
+title: SignInPasswordlessSecurityKeyParams
+sidebar_label: SignInPasswordlessSecurityKeyParams
+description: No description provided.
+displayed_sidebar: referenceSidebar
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L56
+---
+
+# `SignInPasswordlessSecurityKeyParams`
+
+## Parameters
+
+---
+
+**<span className="parameter-name">email</span>** <span className="optional-status">required</span> `string`
+
+---
+
+**<span className="parameter-name">securityKey</span>** <span className="optional-status">required</span> `"true"`
+
+---

docs/docs/reference/docgen/javascript/auth/types/sign-in-passwordless-sms-otp-params.mdx

@@ -4,7 +4,7 @@ title: SignInPasswordlessSmsOtpParams
 sidebar_label: SignInPasswordlessSmsOtpParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L74
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L66
 ---
 
 # `SignInPasswordlessSmsOtpParams`

docs/docs/reference/docgen/javascript/auth/types/sign-in-passwordless-sms-params.mdx

@@ -4,7 +4,7 @@ title: SignInPasswordlessSmsParams
 sidebar_label: SignInPasswordlessSmsParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L69
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L61
 ---
 
 # `SignInPasswordlessSmsParams`

docs/docs/reference/docgen/javascript/auth/types/sign-in-reponse.mdx

@@ -1,34 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: SignInReponse
-sidebar_label: SignInReponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L123
----
-
-# `SignInReponse`
-
-## Parameters
-
----
-
-**<span className="parameter-name">session</span>** <span className="optional-status">required</span> `null` | [`Session`](/reference/docgen/javascript/auth/types/session)
-
----
-
-**<span className="parameter-name">error</span>** <span className="optional-status">required</span> `null` | `ErrorPayload`
-
----
-
-**<span className="parameter-name">mfa</span>** <span className="optional-status">optional</span> `{ enabled: boolean, ticket: string }`
-
----
-
-**<span className="parameter-name">providerUrl</span>** <span className="optional-status">optional</span> `string`
-
----
-
-**<span className="parameter-name">provider</span>** <span className="optional-status">optional</span> `string`
-
----

docs/docs/reference/docgen/javascript/auth/types/sign-in-response.mdx

@@ -1,34 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: SignInResponse
-sidebar_label: SignInResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L45
----
-
-# `SignInResponse`
-
-## Parameters
-
----
-
-**<span className="parameter-name">session</span>** <span className="optional-status">required</span> `null` | [`Session`](/reference/docgen/javascript/auth/types/session)
-
----
-
-**<span className="parameter-name">mfa</span>** <span className="optional-status">required</span> `null` | `{ ticket: string }`
-
----
-
-**<span className="parameter-name">error</span>** <span className="optional-status">required</span> `null` | `ErrorPayload`
-
----
-
-**<span className="parameter-name">providerUrl</span>** <span className="optional-status">optional</span> `string`
-
----
-
-**<span className="parameter-name">provider</span>** <span className="optional-status">optional</span> `string`
-
----

docs/docs/reference/docgen/javascript/auth/types/sign-in-with-provider-options.mdx

@@ -4,19 +4,13 @@ title: SignInWithProviderOptions
 sidebar_label: SignInWithProviderOptions
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L78
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L71
 ---
 
 # `SignInWithProviderOptions`
 
-## Parameters
-
----
-
-**<span className="parameter-name">provider</span>** <span className="optional-status">required</span> [`Provider`](/reference/docgen/javascript/auth/types/provider)
-
----
-
-**<span className="parameter-name">options</span>** <span className="optional-status">optional</span> `ProviderOptions`
-
----
+```ts
+type SignInWithProviderOptions =
+  | { provider: Exclude<Provider, 'workos'>; options: CommonProviderOptions }
+  | { provider: 'workos'; options: WorkOsOptions }
+```

docs/docs/reference/docgen/javascript/auth/types/sign-up-email-password-params.mdx

@@ -4,7 +4,7 @@ title: SignUpEmailPasswordParams
 sidebar_label: SignUpEmailPasswordParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L31
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L29
 ---
 
 # `SignUpEmailPasswordParams`
@@ -13,7 +13,7 @@ custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-j
 
 ---
 
-**<span className="parameter-name">password</span>** <span className="optional-status">required</span> `string`
+**<span className="parameter-name">options</span>** <span className="optional-status">optional</span> `SignUpOptions`
 
 ---
 
@@ -21,6 +21,6 @@ custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-j
 
 ---
 
-**<span className="parameter-name">options</span>** <span className="optional-status">optional</span> `SignUpOptions`
+**<span className="parameter-name">password</span>** <span className="optional-status">required</span> `string`
 
 ---

docs/docs/reference/docgen/javascript/auth/types/sign-up-params.mdx

@@ -4,7 +4,11 @@ title: SignUpParams
 sidebar_label: SignUpParams
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L37
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L40
 ---
 
 # `SignUpParams`
+
+```ts
+type SignUpParams = SignUpEmailPasswordParams | SignUpSecurityKeyParams
+```

docs/docs/reference/docgen/javascript/auth/types/sign-up-response.mdx

@@ -1,16 +0,0 @@
----
-# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
-title: SignUpResponse
-sidebar_label: SignUpResponse
-description: No description provided.
-displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L39
----
-
-# `SignUpResponse`
-
-```ts
-type SignUpResponse =
-  | { session: null; error: ErrorPayload }
-  | { session: Session | null; error: null }
-```

docs/docs/reference/docgen/javascript/auth/types/sign-up-security-key-params.mdx

@@ -0,0 +1,26 @@
+---
+# ⚠️ AUTO-GENERATED CONTENT. DO NOT EDIT THIS FILE DIRECTLY! ⚠️
+title: SignUpSecurityKeyParams
+sidebar_label: SignUpSecurityKeyParams
+description: No description provided.
+displayed_sidebar: referenceSidebar
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/hasura-auth-js/src/utils/types.ts#L34
+---
+
+# `SignUpSecurityKeyParams`
+
+## Parameters
+
+---
+
+**<span className="parameter-name">email</span>** <span className="optional-status">required</span> `string`
+
+---
+
+**<span className="parameter-name">options</span>** <span className="optional-status">optional</span> `SignUpSecurityKeyOptions`
+
+---
+
+**<span className="parameter-name">securityKey</span>** <span className="optional-status">required</span> `"true"`
+
+---

docs/docs/reference/docgen/javascript/auth/types/user.mdx

@@ -4,7 +4,7 @@ title: User
 sidebar_label: User
 description: User information
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/core/src/types.ts#L93
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/core/src/types.ts#L106
 ---
 
 # `User`

docs/docs/reference/docgen/javascript/nhost-js/content/create-client.mdx

@@ -15,18 +15,18 @@ custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/nhost-js/src/
 
 **<span className="parameter-name">config</span>** <span className="optional-status">required</span> [`NhostClientConstructorParams`](/reference/docgen/javascript/nhost-js/types/nhost-client-constructor-params)
 
-| Property                                                                                               | Type                | Required | Notes                                                                                                                         |
-| :----------------------------------------------------------------------------------------------------- | :------------------ | :------: | :---------------------------------------------------------------------------------------------------------------------------- |
-| <span className="parameter-name"><span className="light-grey">config.</span>refreshIntervalTime</span> | `number`            |          | Time interval until token refreshes, in seconds                                                                               |
-| <span className="parameter-name"><span className="light-grey">config.</span>clientStorageType</span>   | `ClientStorageType` |          | Define a way to get information about the refresh token and its exipration date.                                              |
-| <span className="parameter-name"><span className="light-grey">config.</span>clientStorage</span>       | `ClientStorage`     |          | Object where the refresh token will be persisted and read locally.                                                            |
-| <span className="parameter-name"><span className="light-grey">config.</span>autoRefreshToken</span>    | `boolean`           |          | When set to true, will automatically refresh token before it expires                                                          |
-| <span className="parameter-name"><span className="light-grey">config.</span>autoSignIn</span>          | `boolean`           |          | When set to true, will parse the url on startup to check if it contains a refresh token to start the session with             |
-| <span className="parameter-name"><span className="light-grey">config.</span>devTools</span>            | `boolean`           |          | Activate devTools e.g. the ability to connect to the xstate inspector                                                         |
-| <span className="parameter-name"><span className="light-grey">config.</span>start</span>               | `boolean`           |          |                                                                                                                               |
-| <span className="parameter-name"><span className="light-grey">config.</span>backendUrl</span>          | `string`            |          | Nhost backend URL Should only be used when self-hosting                                                                       |
-| <span className="parameter-name"><span className="light-grey">config.</span>adminSecret</span>         | `string`            |          | When set, the admin secret is sent as a header, `x-hasura-admin-secret`, for all requests to GraphQL, Storage, and Functions. |
-| <span className="parameter-name"><span className="light-grey">config.</span>subdomain</span>           | `string`            |          | App subdomain (e.g, ieingiwnginwnfnegqwvdqwdwq) Should be used when using the Nhost platform Use "localhost" in development   |
-| <span className="parameter-name"><span className="light-grey">config.</span>region</span>              | `string`            |          | App region (e.g., eu-central-1) Not required in development (when `subdomain` is "localhost")                                 |
+| Property                                                                                               | Type                | Required | Notes                                                                                                                                    |
+| :----------------------------------------------------------------------------------------------------- | :------------------ | :------: | :--------------------------------------------------------------------------------------------------------------------------------------- |
+| <span className="parameter-name"><span className="light-grey">config.</span>refreshIntervalTime</span> | `number`            |          | Time interval until token refreshes, in seconds                                                                                          |
+| <span className="parameter-name"><span className="light-grey">config.</span>clientStorageType</span>   | `ClientStorageType` |          | Define a way to get information about the refresh token and its exipration date.                                                         |
+| <span className="parameter-name"><span className="light-grey">config.</span>clientStorage</span>       | `ClientStorage`     |          | Object where the refresh token will be persisted and read locally.                                                                       |
+| <span className="parameter-name"><span className="light-grey">config.</span>autoRefreshToken</span>    | `boolean`           |          | When set to true, will automatically refresh token before it expires                                                                     |
+| <span className="parameter-name"><span className="light-grey">config.</span>autoSignIn</span>          | `boolean`           |          | When set to true, will parse the url on startup to check if it contains a refresh token to start the session with                        |
+| <span className="parameter-name"><span className="light-grey">config.</span>devTools</span>            | `boolean`           |          | Activate devTools e.g. the ability to connect to the xstate inspector                                                                    |
+| <span className="parameter-name"><span className="light-grey">config.</span>start</span>               | `boolean`           |          |                                                                                                                                          |
+| <span className="parameter-name"><span className="light-grey">config.</span>backendUrl</span>          | `string`            |          | Nhost backend URL Should only be used when self-hosting                                                                                  |
+| <span className="parameter-name"><span className="light-grey">config.</span>adminSecret</span>         | `string`            |          | When set, the admin secret is sent as a header, `x-hasura-admin-secret`, for all requests to GraphQL, Storage, and Serverless Functions. |
+| <span className="parameter-name"><span className="light-grey">config.</span>subdomain</span>           | `string`            |          | Project subdomain (e.g. `ieingiwnginwnfnegqwvdqwdwq`) Use `localhost` during local development                                           |
+| <span className="parameter-name"><span className="light-grey">config.</span>region</span>              | `string`            |          | Project region (e.g. `eu-central-1`) Project region is not required during local development (when `subdomain` is `localhost`)           |
 
 ---

docs/docs/reference/docgen/javascript/nhost-js/content/nhost-client/index.mdx

@@ -21,18 +21,18 @@ const nhost = new NhostClient({ subdomain, region })
 
 **<span className="parameter-name">\_\_namedParameters</span>** <span className="optional-status">required</span> [`NhostClientConstructorParams`](/reference/docgen/javascript/nhost-js/types/nhost-client-constructor-params)
 
-| Property                                                                                                            | Type                | Required | Notes                                                                                                                         |
-| :------------------------------------------------------------------------------------------------------------------ | :------------------ | :------: | :---------------------------------------------------------------------------------------------------------------------------- |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>region</span>              | `string`            |          | App region (e.g., eu-central-1) Not required in development (when `subdomain` is "localhost")                                 |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>subdomain</span>           | `string`            |          | App subdomain (e.g, ieingiwnginwnfnegqwvdqwdwq) Should be used when using the Nhost platform Use "localhost" in development   |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>adminSecret</span>         | `string`            |          | When set, the admin secret is sent as a header, `x-hasura-admin-secret`, for all requests to GraphQL, Storage, and Functions. |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>backendUrl</span>          | `string`            |          | Nhost backend URL Should only be used when self-hosting                                                                       |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>start</span>               | `boolean`           |          |                                                                                                                               |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>devTools</span>            | `boolean`           |          | Activate devTools e.g. the ability to connect to the xstate inspector                                                         |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>autoSignIn</span>          | `boolean`           |          | When set to true, will parse the url on startup to check if it contains a refresh token to start the session with             |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>autoRefreshToken</span>    | `boolean`           |          | When set to true, will automatically refresh token before it expires                                                          |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>clientStorage</span>       | `ClientStorage`     |          | Object where the refresh token will be persisted and read locally.                                                            |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>clientStorageType</span>   | `ClientStorageType` |          | Define a way to get information about the refresh token and its exipration date.                                              |
-| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>refreshIntervalTime</span> | `number`            |          | Time interval until token refreshes, in seconds                                                                               |
+| Property                                                                                                            | Type                | Required | Notes                                                                                                                                    |
+| :------------------------------------------------------------------------------------------------------------------ | :------------------ | :------: | :--------------------------------------------------------------------------------------------------------------------------------------- |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>region</span>              | `string`            |          | Project region (e.g. `eu-central-1`) Project region is not required during local development (when `subdomain` is `localhost`)           |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>subdomain</span>           | `string`            |          | Project subdomain (e.g. `ieingiwnginwnfnegqwvdqwdwq`) Use `localhost` during local development                                           |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>adminSecret</span>         | `string`            |          | When set, the admin secret is sent as a header, `x-hasura-admin-secret`, for all requests to GraphQL, Storage, and Serverless Functions. |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>backendUrl</span>          | `string`            |          | Nhost backend URL Should only be used when self-hosting                                                                                  |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>start</span>               | `boolean`           |          |                                                                                                                                          |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>devTools</span>            | `boolean`           |          | Activate devTools e.g. the ability to connect to the xstate inspector                                                                    |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>autoSignIn</span>          | `boolean`           |          | When set to true, will parse the url on startup to check if it contains a refresh token to start the session with                        |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>autoRefreshToken</span>    | `boolean`           |          | When set to true, will automatically refresh token before it expires                                                                     |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>clientStorage</span>       | `ClientStorage`     |          | Object where the refresh token will be persisted and read locally.                                                                       |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>clientStorageType</span>   | `ClientStorageType` |          | Define a way to get information about the refresh token and its exipration date.                                                         |
+| <span className="parameter-name"><span className="light-grey">\_\_namedParameters.</span>refreshIntervalTime</span> | `number`            |          | Time interval until token refreshes, in seconds                                                                                          |
 
 ---

docs/docs/reference/docgen/javascript/nhost-js/content/nhost-graphql-client/content/01-request.mdx

@@ -3,13 +3,13 @@
 title: request()
 sidebar_label: request()
 slug: /reference/javascript/nhost-js/graphql/request
-description: Use `nhost.graphql.request` to send a GraphQL request. For more serious GraphQL usage in your app we recommend using a GraphQL client such as Apollo Client (https://www.apollographql.com/docs/react).
+description: Use `nhost.graphql.request` to send a GraphQL request. For more serious GraphQL usage we recommend using a GraphQL client such as Apollo Client (https://www.apollographql.com/docs/react).
 custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/nhost-js/src/clients/graphql.ts#L55
 ---
 
 # `request()`
 
-Use `nhost.graphql.request` to send a GraphQL request. For more serious GraphQL usage in your app we recommend using a GraphQL client such as Apollo Client (https://www.apollographql.com/docs/react).
+Use `nhost.graphql.request` to send a GraphQL request. For more serious GraphQL usage we recommend using a GraphQL client such as Apollo Client (https://www.apollographql.com/docs/react).
 
 ```ts
 const CUSTOMERS = gql`

docs/docs/reference/docgen/javascript/nhost-js/types/backend-or-subdomain.mdx

@@ -4,7 +4,7 @@ title: BackendOrSubdomain
 sidebar_label: BackendOrSubdomain
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/nhost-js/src/utils/types.ts#L40
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/nhost-js/src/utils/types.ts#L39
 ---
 
 # `BackendOrSubdomain`

docs/docs/reference/docgen/javascript/nhost-js/types/function-call-response.mdx

@@ -4,7 +4,7 @@ title: FunctionCallResponse
 sidebar_label: FunctionCallResponse
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/nhost-js/src/utils/types.ts#L57
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/nhost-js/src/utils/types.ts#L56
 ---
 
 # `FunctionCallResponse`

docs/docs/reference/docgen/javascript/nhost-js/types/graphql-request-response.mdx

@@ -4,7 +4,7 @@ title: GraphqlRequestResponse
 sidebar_label: GraphqlRequestResponse
 description: No description provided.
 displayed_sidebar: referenceSidebar
-custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/nhost-js/src/utils/types.ts#L47
+custom_edit_url: https://github.com/nhost/nhost/edit/main/packages/nhost-js/src/utils/types.ts#L46
 ---
 
 # `GraphqlRequestResponse`