This article covers the use of Two Factor Authentication for the Nexus system. This is in place to protect accounts with access to Pupil level records and/or permissions to make significant changes to the system or create new users.
Who this is for
Users who will need to use Two Factor Authentication to access Nexus (or will reset that 2FA for other users in the LA)
Which users will need to use Two Factor Authentication
- All users with access to identifiable pupil/child level information through Nexus. More information can be found here.
- Some other users with permissions to create or allocate permissions to other users (though they will usually have pupil level permissions anyway)
- Other users can opt to use two-factor authentication for additional security but are not required to do so.
- Nexus Administrators who will need to reset the 2FA for one of their users
Before you start
If you have any permissions granting access to identifiable pupil level information in Nexus, you will need to download a two-factor authentication app onto a phone/tablet (Android or IOS devices).
There are many free apps available over multiple platforms and you can use most of them. Google and Microsoft both have authenticator apps that will work on Android and IOS devices and are used by many Local Authorities for internal purposes. You are recommended - where possible - to use the same app for Nexus as for your LA account.
The phone/tablet you install it on need not belong to the Local Authority and can be a personal device. It is only assuring your possession of a known device and is not required to directly tie to your Local Authority.
Using a phone or tablet app to log into NCER Nexus - Initial set up
- Go to https://www.ncer.org/Login.aspx and log in as normal with your username and password.
- You'll be presented with a new screen that has a QR code you can scan.
- Open up the app store on your phone, search for and install the app you want to use, such as Microsoft Authenticator.
- If you do choose Microsoft Authenticator, you'll be presented with a number of screens asking you to sign in, skip past all of the initial screens.
- You'll then have an opportunity to add your first account, choose other account if you're using Microsoft Authenticator but in other apps, you might not need to choose a type of account.
- You can then scan the QR code that you will see on your computer screen when you log into Nexus.
- Your Nexus account will automatically be linked to your app, select the account in your app and you'll see your verification code.
- Once you have entered your verification code into the box on the Nexus page you'll need to log into Nexus again.
-
The next time you will just be asked for your two-factor code, check the number in your app again and enter this to complete the setup and login process.
Subsequent log-in after set up
After your phone is set up for the first time it will constantly generate codes for accessing Nexus:
- Open Nexus and enter your username and password
- Tick to accept the terms and conditions of use
- Open your authenticator app
- Add the code that has been generated when asked to do so
- If the code was close to expiry you may need to repeat this step
Resetting Two Factor Authentication
To help Nexus Administrators, the 'reset two-factor authentication' button will be available on the account pages for all users in their own LA. This means that if someone can't log into their account because of an issue with their two factor authentication, they won't need to contact Nexus Support anymore, they will be able to contact their LA Admin for it to be reset. Admins can access this through the Users page by clicking on their user name and scrolling to the bottom right to see the button:
In addition to a user experiencing issues, this button may also need to be used where a user changes their phone/device and has to reinstall their Authentication app.
Troubleshooting any issues
If you experience any issues after following this guidance, please either email 2factor@angelsolutions.co.uk or call 0845 129 7197.
Last reviewed / owner
Last reviewed: July 2026 / Owner: Technical Support Director