O4 allows users to set up two factor authentication. Once enabled, a user will be asked to provide a confirmation code each time they log in. If they remain signed in for more than 30 days, the confirmation code will expire and the user will be signed out, requiring a new confirmation code to be entered. Confirmation codes will be sent to the user's email address that is set up in their user editor.
For a video walkthrough about enabling two factor authentication, click here.
There are three ways two factor authentication can be enabled:
- Users can enable it for themselves
- Admins can enable it for another user
- Admins can enable it for all users
Enabling Two Factor Authentication For Your User
1. Select the icon.
2. Select Security Settings from the drop-down list.
4. The User Security page will appear.
5. Under the Authentication section, turn on Two Factor Authentication.
6. Select .
Enabling Two Factor Authentication For Another User
Users with admin access to Users can enable two factor authentication for other users.
1. Select the icon.
2. Select Configuration from the drop-down list.
3. Select Users.
4. The Users Listing will appear.
5. Click a user in the listing to open it.
5. The User Viewer will appear.
6. Click, then click the General Tab.
7. In the Security section, turn on Two Factor Authentication.
8. Scroll down and click to save.
Enabling Two Factor Authentication For All Users
Users will admin access to Users can enable two factor authentication for all users.
1. Select the icon.
2. Select Configuration from the drop-down list.
3. Click Software.
4. O4 Settings will appear. Click the Global Settings tab, then the Web tab.
5. Turn on Global Two Factor Authentication.
5. Select .
Verification Email
The next time a user logs in they will be asked to provide a confirmation code. Users should receive an email containing the code. Once received, enter the confirmation code and select .
If users do not receive an email, they may select the Resend Code link at the bottom of the screen.
An example of the email is below:
Comments
2 comments
Can this setting be forced to the ON position by an admin so that an individual user is unable to bypass an organizational requirement for 2FA?
Hi James,
This is currently in our development queue. It will be published in our release notes as soon as it is pushed to production. Our release notes can be found here.
Thank you,
Lauren
Please sign in to leave a comment.