We’re excited to introduce Login Enforcement, a new security feature that gives administrators greater control over how team members access their Avaza account.
This feature allows you to enable or restrict specific login methods, ensuring your team signs in using only approved authentication options.
What’s New?
With Login Enforcement, admins can now:
- Control which login methods are allowed for their team
- Enable Single Sign-On (SSO) providers (e.g., Google)
- Disable/enable standard Avaza email/password login if required
- Enforce consistent and secure authentication across the account
Where to Find This Setting
Go to:
Settings → General Settings → Security Panel
You will see a new section:
“Login Options for Team Members”
This section lists all available login methods supported by Avaza.
Available Login Options
Currently supported login methods include:
- Avaza Login (Email & Password)
- Google SSO
Admins can enable or disable each option using toggle controls.
How It Works
1. Enable or Disable Login Methods
- Toggle ON the login methods you want your team to use
- Toggle OFF any methods you want to restrict
2. Save Changes
- Click Save to apply changes
- Settings are applied at the account level
Important Safeguards
To prevent accidental lockouts:
- You cannot disable Avaza Login unless at least one SSO option is enabled
- If attempted, you’ll see this message:
“At least one login method must be enabled”
Enforcement During Login
Once login restrictions are applied:
- Users attempting to log in with a disabled method will be blocked
- They will see a message instructing them to use an approved login option
Example Scenario
If only Google SSO is enabled:
- Users logging in with email/password will not be allowed access
- They must sign in using Google
User Communication
Admins should communicate changes proactively to avoid confusion
User Access Scenarios
Inviting New Users
- New users must sign in using an enabled login method
Existing Users
- If their current login method is disabled:
- They must switch to an enabled method
Best Practices
- ✅ Always keep at least one login method enabled
- ✅ Test login providers before enforcing them
- ✅ Inform your team before making changes
- ✅ Ensure users have access to the required provider (e.g., Google accounts)
Summary
Login Enforcement provides:
- Stronger security controls
- Centralized authentication management
- Flexibility to adopt SSO-based workflows
This is a foundational step toward more secure and scalable access management within Avaza.
What’s Coming Next for SSO
We’re continuously working to expand our Single Sign-On (SSO) capabilities.
In the future, we plan to support additional SSO providers (such as Microsoft and others) to give teams more flexibility in how they authenticate and manage access.
If there’s a specific provider you’d like to see supported, we’d love to hear from you. Please reach out to our support team or your account manager with your request, your feedback helps us prioritise future enhancements.