--- title: WAVE Dispatch Multi-Factor Authentication (MFA) description: gredhtf --- [Skip to content](https://help.xeva.group/whawave-dispatch-multi-factor-authentication-mfat-question-is-your-article-answering#main-content) English - United Kingdom Show submenu for translations [![](https://help.xeva.group/hs-fs/hubfs/XEVA%20Logos/XEVA%20BLUE%20logo%20transparent%20background%20170%20x%2040.png?width=170&height=40&name=XEVA%20BLUE%20logo%20transparent%20background%20170%20x%2040.png)](https://help.xeva.group/?hsLang=en-gb) Open main navigation Close main navigation - English - United Kingdom Show submenu for translations - [Contact us](https://www.xeva.group/contact-us) [Contact us](https://www.xeva.group/contact-us) How can we help you? - There are no suggestions because the search field is empty. 1. [XEVA Support](https://help.xeva.group/?hsLang=en-gb) 2. [WAVE PTX](https://help.xeva.group/wave-ptx?hsLang=en-gb) 3. [WAVE Devices and Users](https://help.xeva.group/wave-ptx?hsLang=en-gb#wave-devices-and-users) 17 October 2026 # WAVE Dispatch Multi-Factor Authentication (MFA) 1 Updates • Dispatch Sign-in now with Multi-factor Authentication (MFA) Signing in with the WAVE PTX Dispatcher now has added security with the addition of Multi-factor Authentication (MFA). The Dispatch user guide has been updated to reflect this change: To sign into the Dispatch, the dispatcher first has to activate the account by clicking the activation link received in their email. The dispatcher has to choose the password and sign in with the registered email ID. The password must meet the minimum requirements of the password policy of the application as follows: • At least 16 characters • One lower case letter \[a to z\] • One upper case letter \[A to Z\] • One number between \[0 to 9\] • One of these special characters: @#$%^&+= NOTE: These system-wide settings may change based on your service provider configuration. First-time log in requires account activation. User must install the MFA mobile application. Motorola Solutions has certified the use of the Google Authenticator. The application can be downloaded from the application store on a mobile device. If the administrator enables the MFA, each log-in requires two-factor authentication. To access the application, after entering credentials user must enter the OTP from the mobile app. The dispatcher can reset or change the password from the sign-in page or the Settings in the Dispatch respectively. The authentication can be done in two ways, which we have described below: • QR Code • Seed Key We have also provided some helpful notes and tips. WAVE PTX Dispatcher – Release 12.3 2 The new process using the QR code: We have taken snips of the new process so dealers are able to understand what changes have been made, where they appear and what they look like. 1\. The first change is after a new dispatcher is created. The user creates a new password which is entered twice and confirmed, the user will login and following page will appear: On this page, the user will need to either download and log into an Authenticator app or just log into an existing authenticator app on their mobile phone. The list of apps that can be used are more than what’s shown on the screen, the process uses TOTP (Time-based One Time Password) authenticators. Examples below: • Google Authenticator – Only Motorola tested option. • Microsoft Authenticator • Okta • Authy (from Twilio) for Android or iOS • Free OTP • Google Authenticator plugin for Chrome • Authy (from Twilio) • WinAuth for Windows 3 2\. Once the chosen method is open, the user will need to use a specific feature of the app to scan the shown QR code. This links this dispatcher to the used account, whether that’s a google account, Microsoft account etc. a. Example below using the Google Authenticator b. Use the + symbol at the bottom right to open the camera for scanning a QR code c. Once scanned, it will show WDS Realm and then the dispatcher ID to identify it d. The code changes every 30 seconds 3\. Enter the code shown in the APP at the bottom of this page and SUBMIT to continue. 4 4\. You will be brought to the login screen. 5\. Now, each time the user logs in, they will enter their email and password and then it will take them to a new page where they need to enter the code that’s shown on the authenticator app. Shown below: 6\. The process from there is standard for the dispatcher, with the plugin, extension and terms and conditions. 5 The new process using the Seed Key: We have taken snips of the new process so dealers are able to understand what changes have been made, where they appear and what they look like. 1\. The first change is after a new dispatcher is created. The user creates a new password which is entered twice and confirmed, the user will login and following page will appear: On this page, the user will need to either download and log into an Authenticator app or just log into an existing authenticator app on their mobile phone. The list of apps that can be used are more than what’s shown, the process uses TOTP (Time- based One Time Password) authenticators. Examples below: • Google Authenticator – Only Motorola tested option. • Microsoft Authenticator • Okta • Authy (from Twilio) for Android or iOS • Free OTP • Google Authenticator plugin for Chrome • Authy (from Twilio) • WinAuth for Windows 6 2\. Once the chosen method is open, the user will need to click on “Unable to scan?” on the right of the QR code. 3\. This will bring up a new page which provides a 32 digit key to use in the app: 7 4\. In the Google authenticator app, when you press the + key, the user will choose “Enter a setup key”. 5\. This will bring up a new screen for the user to enter the 32 digit code: 6\. Account name is just the reference for this link e.g. WAVE Dispatcher, the key is typed in with or without spaces and the type of key is Time based. 7\. This links this dispatcher to the used account, whether that’s a google account, Microsoft account etc. a. Once entered, it will show your identifying account name and current code b. The code changes every 30 seconds 8 8\. Enter the code shown in the APP at the bottom of this page and SUBMIT to continue. 9\. You will be brought to the login screen. 10\. Now, each time the user logs in, they will enter their email and password and then it will take them to a new page where they need to enter the code that’s shown on the authenticator app. Shown below: 11\. The process from there is standard for the dispatcher, with the plugin, extension and terms and conditions. 9 Notes/Tips: • You can use the same QR code or seed key for multiple users if they share the same dispatch position. If you have all users’ authenticator apps ready when you get to the QR screen, you can scan the code on all apps at once. Each user, even with different google accounts, can then see the current code to log into the dispatcher. o Note: we do not recommend screenshotting and saving the QR code or seed key for security reasons. It’s also best to have as few users as possible sharing the OTP. • Motorola have only tested the Google Authenticator, using any other one-time verification app may not be fully supported. • Changing the email address of the dispatcher pushes a password creation email to the new address however, they will still need the previous QR/seed code to continue. Once entered, they will be provided a new QR/Seed code to use from there on. If you do not have the previous QR/Seed code then you will need to delete the dispatcher account and create a new one. - [WAVE PTX](https://help.xeva.group/wave-ptx?hsLang=en-gb#main-content) - [WAVE Devices and Users](https://help.xeva.group/wave-ptx?hsLang=en-gb#wave-devices-and-users) [![](https://help.xeva.group/hs-fs/hubfs/XEVA%20Logos/XEVA%20BLUE%20logo%20transparent%20background%20170%20x%2040.png?width=170&height=40&name=XEVA%20BLUE%20logo%20transparent%20background%20170%20x%2040.png)](https://help.xeva.group/?hsLang=en-gb) Unit 5, The Ringway Centre Edison Road Basingstoke RG21 6YH  [mailto:sales@xeva.group](mailto:sales@xeva.group) Copyright © 2026, XEVA Ltd