In this article:
Learn how multi-factor authentication (MFA) works in Logiqc.
MFA adds a second step to signing in, alongside a username and password. Once enabled, users confirm their identity with a one-time code from an authenticator app on their mobile device.
This article explains who MFA applies to, what the sign-in experience looks like, how to get help if something goes wrong, and a summary of the administrator controls available.
MFA reduces the risk of account takeover from compromised passwords. With MFA active, users need a one-time code from an authenticator app as well as their username and password.
It's commonly required by organisations with a security policy that includes MFA, or as part of a compliance or assurance review.
Q: Does MFA apply to every user?
A: It applies to users who sign in directly to Logiqc with a username and password. Users who sign in through single sign-on (SSO) are not affected — their MFA is managed by Microsoft Entra ID.
Q: How long does MFA setup take?
A: Setup usually takes around two minutes once the user has an authenticator app installed.
Q: What happens if a user loses access to their authenticator app?
A: An administrator can reset their MFA from user administration, after which the user goes through setup again.
Who is affected by Logiqc MFA
Logiqc MFA applies to users who sign in directly to Logiqc with a username and password.
Username and password users
These users are guided through MFA setup at their next sign-in once enforcement is turned on.
SSO users
These users sign in through Microsoft Entra ID. Logiqc MFA enforcement does not apply to them.
How MFA works
The first time an affected user signs in after MFA is turned on, they are guided through a short setup process:
- They install an authenticator app on their mobile device, such as Google Authenticator, Microsoft Authenticator, or Authy.
- They scan a QR code (or enter a setup key) shown on screen to link their Logiqc account to the app.
- From then on, each sign-in requires a 6-digit code from the authenticator app, alongside their username and password.
For step-by-step guidance, see:
Getting help
Most users complete MFA setup without any trouble. The most common issues, and how to resolve them, are below.
Can't complete setup
- Check that the authenticator app is installed, and that the Logiqc account shown on screen is the one being added.
- On Logiqc Mobile, the setup key shown on screen can be copied and pasted into the authenticator app when adding the account.
- For step-by-step setup guidance, see Set up MFA.
Wrong code or code expired
- Codes refresh every 30 seconds. Wait for a new code and try again.
- If codes consistently fail, the time on the mobile device may need to be set to automatic in device settings.
- For sign-in troubleshooting, see Sign in with MFA.
Lost access to the authenticator app
- This requires administrator action.
- An administrator resets the user's MFA from user administration. See Reset a user's MFA.
- Once reset, the user can sign in and go through MFA setup again.
Administrator controls
A quick reference for the MFA actions available to administrators.
| Situation | What to do |
|---|---|
| Require MFA for users who sign in with username and password | Turn on MFA enforcement. See Turn on MFA for your organisation. |
| Enable MFA for one user only | Use the MFA toggle in the user's account. See Manage MFA for individual users. |
| Disable MFA for one user | Use the MFA toggle, only available when organisation-wide enforcement is off. See Manage MFA for individual users. |
| User is locked out of their authenticator app | Use Reset MFA in the user's account. See Reset a user's MFA. |
| SSO user needs MFA support | Direct them to your Microsoft Entra ID administrator. Logiqc does not manage SSO MFA. |