Reading time 2 mins
Overview
- Multi‑Factor Authentication (MFA) adds an extra layer of security to user accounts in Radar Healthcare.
- In Phase 1, MFA allows users to enable MFA on their own accounts only.
What this guide covers
- What MFA is and how it works in Radar Healthcare
- What Phase 1 includes and its limitations
- Permissions required to use MFA
- Supported authenticator apps
- Known limitations
- What’s coming next
What is MFA in Radar Healthcare?
- MFA adds an additional verification step during sign‑in, using a one‑time code generated by an authenticator app.
- This reduces the risk of unauthorised access if a password is compromised.
Phase 1 scope
- In Phase 1:
- Permission to use MFA can only be enabled by administrators.
- MFA can only be enabled on the user’s own account.
- MFA cannot yet be enforced across the organisation.
Permissions required
- MFA setup is controlled by a dedicated Multi‑Factor Authentication permission.
- This permission is managed in System Administration → Access Control.
- Only users with this permission can enable MFA in Phase 1.
Supported authenticator apps
The following authenticator apps are supported:
- Microsoft Authenticator
- Google Authenticator
- Any TOTP‑compatible authenticator app
Known limitations
- Single Sign‑On (SSO) is not supported with MFA.
- MFA cannot be enforced for other users in Phase 1.
Help and support
If a super admin loses access to their authenticator device and their one‑time backup codes, they must contact Radar Healthcare Support for help restoring access.
What’s coming next
Users in enforced roles will be required to set up and log in using MFA and will not be able to turn this off unless disabled by a super admin.