Login enforcement lets you decide how team members sign in to your Avaza account: with their Avaza email and password, with Google single sign-on (SSO), or either. For example, you can require Google sign-in so that people use the accounts your company already manages.

Choose how your team signs in

  1. Go to Settings › General and scroll down to Security.

  2. Under Login Options for Team Members, switch each method on or off.
    Avaza Login is email and password, plus multi-factor authentication if it's set up. Google is Sign in with Google.

  3. Click Save at the bottom of the page.

  • Who can change it: anyone who can open Settings › General, which means Administrators and Finance Managers. See general settings.
  • At least one method stays on. If you switch both off, saving shows "At least one login method must be enabled".
  • It applies to this account only. People who belong to other Avaza accounts sign in there as those accounts allow.
  • It applies to team members only. External contacts, such as customers and contractors, can still sign in with either method.
  • Google is the only single sign-on provider at the moment. To ask for another one, contact Avaza Support.

The same Security section can also require multi-factor authentication. It works with both methods: people who sign in with Google are still asked for their code. See multi-factor authentication.

Before you switch off Avaza Login

  • Check that everyone can sign in with Google. Each team member needs a Google account. It connects to their Avaza login automatically when it uses the same email address. Otherwise they link it once. See Google sign-in.
  • Test it yourself. Sign out, sign back in with Sign in with Google, and make sure you get into the account.
  • Tell your team before you save, so nobody is surprised at their next sign-in.

What your team sees

The Avaza sign-in page doesn't change, because one login can belong to several accounts. The rule applies when someone opens your account.

If a team member opens it after signing in with a method that's switched off, Avaza signs them out and shows Login Options Enforced on this Account. The page has a button for each allowed method, such as Login with Google. People who are already signed in see this page the next time they open a page in your account.

For example, if only Google is on, a team member who signs in with their email and password is sent to this page, and has to choose Login with Google.

People you invite need an allowed method too. With Google only, they sign in with the Google account for the email address you invited. See managing users and contacts.

If someone can't sign in

  • Their Google account uses a different email address. After choosing Google, Avaza asks them to link their logins. They sign in once with their Avaza email and password, click Link, and from then on Google works.
  • Or change their Avaza email address. An Administrator can change the email address on the person's Avaza user to match their Google account. Avaza sends an invitation to the new address to confirm it. See changing an email address.
  • They're asked for a code they can't get. That's multi-factor authentication, not the login option. See multi-factor authentication or reset a user's MFA.
  • You need everyone back in quickly. Switch Avaza Login back on and save.