Once you have been invited to your organisation's Dash by an existing Admin user, you can register and log in using the following methods:
"Local" account
A local account is one with a username (your email address) and password that you set.
Sign in using Google
If you have been invited to a Dash account using an email address associated with a Google account, you can simply log in using the "Continue with Google" button.
If you register your Dash account in this way, you won't create a 'local' password - all further logins must be via the "Continue with Google" button.
Sign in using Microsoft
If you have been invited to a Dash account using an email address associated with a Microsoft account, you can simply log in using the "Continue with Microsoft" button.
If you register your Dash account in this way, you won't create a 'local' password - all further logins for this user must be via the "Continue with Microsoft" button.
If your company uses Microsoft Entra ID (formally Azure AD) then, the first time a user from your organisation attempts to sign in using their Microsoft credentials, they will be asked to click a button to request one of the Entra IA administrators to approve Dash as an application that can use that Entra ID instance for authentication.
What if I need to reset my password?
If you have a local account
On the sign in page (https://yoursubdomain.dash.app/login), click "Forgot password?" and follow the instructions. You'll need access to the email address you used to sign up with.
If you registered using Google or Microsoft
You will need to reset your Google or Microsoft password using those providers' own tools. Some quick links:
What if I accidentally log in with Google after registering with a local account?
No problem! Assuming you used the same email address, you'll be able to log in using either method from now on.
Can I restrict users to SSO-only in Dash?
Yes — but only if users set up their Dash account with SSO the first time they log in.
If a user chooses a local account (username and password) initially, they will be able to sign in with SSO whenever they want, but they'll also be able to still sign in with their local account.
To enforce SSO-only, ask employees to sign in with “Sign in with Microsoft” or “Sign in with Google” when they first set up their account.
If someone has already created a local account, we can help by deleting that account, re-adding them as an SSO user, and transferring their data across.