---
title: "Accounts and sign-in"
description: "Create an account with Google, GitHub or email, and sign in."
canonical_url: "https://surrealdb.com/docs/operate/organisations/sign-in"
section: "Organisations"
surrealdb_version: "4.x"
last_modified: "2026-11-18T02:09:16Z"
---

> Full SurrealDB documentation index: https://surrealdb.com/docs/llms.txt

# Accounts and sign-in

Create an account with Google, GitHub or email, and sign in.

One account gets you into [SurrealDB Studio](https://studio.surrealdb.com), where you manage [organisations](/docs/operate/organisations.md) and [instances](/docs/operate/instances.md).

An account needs no payment details. The free instance type carries no charge, so you can deploy before you add a payment method.

To create an account or to sign in, open [studio.surrealdb.com](https://studio.surrealdb.com) and continue to the authentication page.

## Choose a sign-in method

Three methods are available. Use the same method every time. If you sign up with Google and later sign in by email on the same address, you create a second account. The first account is not recovered.

| Method | What happens | Suited to |
| --- | --- | --- |
| **Google** | You authorise SurrealDB on Google's own sign-in page | Teams already on Google Workspace |
| **GitHub** | You authorise SurrealDB on GitHub's own sign-in page | Developers already signed in to GitHub |
| **Email and password** | You set a password, then confirm the address from a verification link | Anyone who prefers not to link a third-party account |

> [!IMPORTANT]
> Google and GitHub sign-in uses OAuth2. The provider's own page collects your password, so SurrealDB never receives it. SurrealDB requests your email address and name only. After you authorise the connection, the provider returns a token that confirms your identity.

Two-factor authentication configured with Google or GitHub also applies to your SurrealDB account, because the provider verifies you before returning you to SurrealDB. For an account that signs in with an email address and password, add an authenticator app instead. See [Two-step verification](/docs/operate/organisations/security.md) for more.

## Create an account

With Google or GitHub:

1. Select **Sign up with Google** or **Sign up with GitHub**.
2. Choose your account in the provider's window.
3. Allow the requested permissions.

Studio signs you in as soon as the provider returns.

With email:

1. Select **Sign up with Email**.
2. Enter your email address.
3. Set a password.
4. Open the verification link sent to your inbox to confirm the address.

## Sign in

1. Open [studio.surrealdb.com](https://studio.surrealdb.com).
2. Select the method you registered with: **Continue with Google**, **Continue with GitHub**, or **Sign in with Email**.
3. Complete any two-factor step the provider asks for.

To reset a forgotten email password, select **Forgot password?** on the authentication page. Follow the instructions sent to your address.

An account created through Google or GitHub has no SurrealDB password to reset. Recover the provider account instead.

## Accounts for a team

Each person needs their own account. Invite colleagues to the organisation instead of sharing credentials. Separate accounts let each member hold a different role, and let you remove someone without changing a password the rest of the team uses. See [Members and roles](/docs/operate/organisations/members-and-roles.md).

For automation, use a token from [`surreal cloud`](/docs/reference/cli/guides/cloud/authentication.md) rather than an interactive account.

## Next steps

1. [Create an organisation](/docs/operate/organisations.md) to hold your instances and billing.
2. [Deploy an instance](/docs/operate/instances/create.md).
3. [Connect to it](/docs/operate/instances/connect.md) from SurrealDB Studio, the CLI, an SDK, or over HTTP.
