Skip to main content

Manage sign-in methods

Control which sign-in methods are available to your users.

Updated over 2 weeks ago

Admins can control which sign-in methods are available to your Dash users. Turning a method off removes it from the login page immediately.

This allows you to set an account-level default for your users to authenticate when accessing your Dash (for example, you can enforce your users to use SSO via Google or Microsoft).

Available sign-in methods

You can enable or disable the following options:

  • Email & password
    Users sign in using an email address and a password stored in Dash.

  • Google
    Users sign in with their Google account.

  • Microsoft
    Users sign in with their Microsoft account.

👉 At least one sign-in method must remain enabled.

What happens when you disable a sign-in method?

Disabling a method does not delete user accounts. It only affects how users authenticate next time they log in.

👉 All existing user data, such as collections and asset uploader information will be retained.

What if a user tries to log in using a method that is no longer enabled?

In this situation, they’ll be prompted to use one of the now-allowed sign-in options instead.

What happens next depends on which method they originally used:


A user signed up with "Email & password", but it's now disabled

A user (i.e. name@company.com) created their Dash account using their email and a password, however "Email & password" is disabled. This is what would happen next:

  • On their next login, they will only have the option to choose Google or Microsoft

  • As long as they have an account with the same email address, they’ll be logged in automatically

  • No additional setup or account linking is required - and all their data (collections, sharelinks, etc) will still be there.


A user signed up with Google or Microsoft SSO, but these were disabled

If a user originally signed up with Google or Microsoft, and both options are disabled leaving Email & password only enabled, our Support team will need to generate a temporary password for them.

Get in touch via the in-app chat with the user(s) email address, and we'll do it for you.

This step is required because users who signed up via Google or Microsoft don’t have a password by default.

Did this answer your question?