Skip to main content
Skip table of contents

How do I set up MFA on my Publisher Account?

As an publisher account administrator user, you must be highly protected, so that no one else can access your account.

The Multi-Factor Authentication (MFA) process provides a second layer of security by asking you to enter a code from your smartphone every time you log in, so we know it’s you every time.

Step 1: Download a free authentication app to generate the one-time passcodes.

For example:

  • Google Authenticator

  • Microsoft Authenticator

  • Twilo Authy Authenticator

Step 2: In the authenticator app, scan the QR code that appears when you login to Webgains.

Alternatively you can use long string of characters displayed underneath the QR code and enter this manually in the app.

Step 3: Enter the one-time passcode from the app into the Webgains Login Page.

Webgains will ask you to enter a 6-digit code each time you login. This code can be generated from your authenticator app, and will refresh every 30 seconds. For this reason, please ensure the code is entered into Webgains promptly to prevent it expiring.

The QR code will only be visible on the first successful login. The next time you login, the QR will not be displayed, for security reasons, so please ensure you have this saved successfully in your app.

If you require a new QR code, please contact support@webgains.com providing details about your request and your user details.

The MFA can only be set up on 1 authenticator app/device per Webgains user. For this reason, along with best protecting your account, we strongly advise against using ‘shared’ logins. If you have different team members requiring account access, you should instead create separate user accounts for each team member.

Each member can then be set to the required permission level. Editor access level users will not be required to set up MFA. You can have up to 50 Active users on an account. (Active users does not include those set to “No Login”).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.