Skip to main content

Logging In with Single Sign-On (SSO) or MFA

This article explains the two methods WorkBuzz Dialogue uses to keep sign-in simple for users and secure for organisations: Single Sign-On (SSO), which allows people to sign in using an existing Microsoft or Google account, and Multi-Factor Authentication

Before you start

  1. Your organisation's administrator must have configured the permitted sign-in methods within Dialogue.

  2. If using SSO, your Microsoft (work) or Google account must already be active.

  3. If using MFA with an authenticator app, you will need a compatible app installed on your phone (e.g. Microsoft Authenticator, Google Authenticator, or Authy).

Step-by-step instructions

Single Sign-On (SSO)

  1. Navigate to the Dialogue sign-in screen and enter your email address.

  2. Dialogue recognises your organisation and displays only the sign-in options your organisation has enabled - for example, "Continue with Microsoft" or "Continue with Google".

  3. Select the relevant option and sign in using your existing provider in the usual way.

  4. You are signed in. No new password is required.

💡 There is nothing new to set up for SSO and no separate Dialogue password to create or manage. When someone leaves your organisation, removing their main work account also removes their access to Dialogue.

Multi-Factor Authentication (MFA)

  1. Enter your password on the Dialogue sign-in screen.

  2. Dialogue prompts you for a one-time code. Retrieve this from either an authenticator app on your phone (e.g. Google Authenticator, Microsoft Authenticator, or Authy), or text message (SMS) sent to your registered phone number.

  3. Enter the one-time code when prompted.

  4. You are signed in.

⚠️ First-time authenticator app setup only: If this is your first time using an authenticator app with Dialogue, the platform will display a QR code for you to scan. This is a one-off step. After scanning, your app will generate a fresh code whenever needed. You can skip this on subsequent sign-ins.

💡 For a full step-by-step walkthrough of the first-time MFA setup process, including creating your password, scanning the QR code, and entering your setup key manually if needed, see Setting up multi-factor authentication (MFA).

⚠️ Important: If your organisation requires MFA, it cannot be skipped or bypassed by an individual user. This is enforced at platform level.

Other account protections

These protections are built into Dialogue and apply automatically:

  • Strong passwords - enforced for all password-based accounts; passwords are never stored in a readable form, and a secure email-verified reset flow is available.

  • Protected session - sessions are time-limited and expire automatically; signing out ends the session immediately.

  • Right-account safeguard - if your browser is signed in to a different personal account, Dialogue detects the mismatch and prevents sign-in with the wrong identity.

  • Trusted infrastructure - sign-in is built on AWS enterprise-grade infrastructure using OAuth 2.0 / OpenID Connect and standard one-time-code methods.

What happens next

Once signed in, you have full access to Dialogue as configured for your role. Administrators can review and update which sign-in methods are permitted at any time via the organisation's settings. If access needs to be revoked for a user, removing their Microsoft or Google account will immediately remove their Dialogue access when SSO is in use.

Common questions

Can my organisation require everyone to use SSO without offering a password option?

Yes. Administrators choose which sign-in methods are available. You can require SSO exclusively, or allow a password option alongside it.

What happens if a user loses access to their authenticator app or phone?

The user will be unable to generate a one-time MFA code. An administrator should be contacted to reset MFA access for that user. Ensure your organisation has a documented recovery process in place.

Can a user bypass MFA if they find it inconvenient?

No. If your organisation requires MFA, it is enforced by the platform and cannot be skipped or bypassed by an individual user.

What is the difference between using an authenticator app and SMS for MFA?

Both deliver a one-time code, but an authenticator app generates codes locally on the phone without requiring mobile signal. SMS codes are sent to a registered phone number and require mobile reception.

What sign-in providers does Dialogue support for SSO?

Dialogue currently supports Microsoft (work accounts) and Google accounts for Single Sign-On.

Glossary

Single Sign-On (SSO)

Signing in with an account you already have (like Microsoft or Google) instead of a separate password.

Multi-Factor Authentication (MFA)

Confirming your identity in more than one way — usually a password plus a one-time code from your phone.

Authenticator app

A free phone app (e.g. Microsoft Authenticator, Google Authenticator) that generates the one-time codes used for MFA.

One-time code

A short number that changes regularly and can only be used once, proving you have your trusted phone.

OAuth 2.0 / OpenID Connect

The widely used, industry-standard technology that powers secure "Continue with…" sign-in across modern apps.

Related Articles
Did this answer your question?