Skip to main content
e6data is passwordless - you never create or remember a password. You verify your email with a 6-digit code, or sign in through your company’s identity provider if Single Sign-On (SSO) is configured.

Sign up (new organization)

Use this if you’re the first person from your company and want to create a new organization:
  1. Go to the e6data login page.
  2. Enter your work email and select Continue.
  3. Enter the 6-digit verification code sent to your inbox.
  4. Because you’re a new user, complete the short setup form: First name, Last name, and Company name (this becomes your organization’s name, 2–100 characters).
  5. Select Continue. You land on the Workspaces page, signed in, as the Admin of the new organization.
Some deployments restrict who can create a new organization. If sign-up isn’t available for your email, ask to be invited instead - see Accept invites.

Log in (existing user)

  1. Go to the login page, enter your email, and select Continue.
  2. If your organization uses SSO, you’re redirected to your company login automatically (see below).
  3. Otherwise, enter the 6-digit code emailed to you.
  4. You’re signed in and taken to the Workspaces page.
If your code doesn’t arrive, select Resend code. Codes are short-lived - request a fresh one if a few minutes have passed.

Log in with SSO

If your organization has connected an identity provider (Okta, Microsoft Entra ID, Google, and so on), you sign in through your company:
  1. Enter your work email and select Continue.
  2. e6data recognizes your email domain and either redirects you to your company login or shows a Sign in with SSO button - select it.
  3. Approve the sign-in at your company’s login page.
  4. You’re returned to e6data, signed in.
The first SSO sign-in creates your account automatically with Viewer access until an admin assigns a different role. SSO sign-in does not fall back to a one-time code. See SSO overview.

Log out

Select Log out from your account menu. This ends your e6data session and signs you out of the identity provider where possible.

Troubleshooting

See also

Last modified on September 29, 2026