Login & Authentication Methods

SigningHub offers a range of secure login and authentication methods to ensure a seamless and protected experience for all users. You can conveniently access your SigningHub account using your SigningHub ID or choose from various third-party authentication options that integrate seamlessly with your existing systems. These include popular platforms such as Microsoft Active Directory, Salesforce, Microsoft ADFS, Microsoft Office 365, LinkedIn, and Google.

To enhance security, SigningHub also supports two-factor authentication (2FA) through One-Time Passwords (OTP), ensuring that only authorized users can access sensitive information. For added flexibility, users can utilize SSL client certificates, as well as identity solutions like Freja Mobile, Freja eID, Bank ID, and itsme.

Organizations looking for advanced authentication methods can leverage options like Azure Active Directory, corporate logins, OpenID Connect (OIDC), OAuth2, and Azure SAML for a streamlined login experience. Selecting the authentication method that best fits your needs is crucial for maintaining security and ensuring ease of access to your SigningHub account. With these versatile options, you can choose the most suitable way to log in and manage your digital signing processes effectively.

Select the authentication option you wish to use.


  1. The "Remember Me" functionality will retain the email address used to log in via SigningHub ID, as well as via third-party private authentication methods. However, this retention is applicable as long as the user manually enters the email address into the designated field.

  2. If the ''Only display the logos of the authentication and signing profiles' checkbox is checked in SigingHub Admin and a logo has not been configured for an authentication profile in the connector, the system will pick and display a logo for the authentication profile from the SigningHub directory, on the login screen.

  3. The authentication profiles with sort order 1 to 3, in SigningHub Admin, will be displayed on the login screen and the authentication profiles with the succeeding sort order will be displayed in the "More Login Options" dialog on the login screen.

  4. The authentication profiles for which a sort order has been provided, in SigningHub Admin, will follow the defined sort order and the remaining authentication profiles will follow the default system sort order.

  5. If the sort order has not been specified for any of the authentication profiles, the default system sort order will be followed.

  6. As a part of GDPR compliance, the "Service Agreement" dialogue box will appear after successful user authentication. This dialogue box contains the links to the "Terms of Service" and "Privacy Policy" pages. SigningHub will ensure that you agree to them before letting you use your account.

  7. The "Service Agreement" dialogue box will not appear after successful user authentication if no Service Agreement is marked active.

  8. Following is the list of authentications that are SigningHub supports in its mobile web/native apps version, in addition to SigningHub desktop web. Rest of the authentications are supported in SigningHub desktop web only.

    • Password-based authentication (i.e. SigningHub)

    • One-Time Password as secondary authentication

    • Time-based One-Time Password as two-factor authentication

    • Microsoft Active Directory

    • Microsoft Office 365

    • Microsoft Azure Active Directory

    • OAuth2

    • OpenID Connect (OIDC)

  9. In case your login session reaches the limit set by Admin for "Concurrent Sessions Limit>Global Configurations", then a dialogue box will appear with the message "Your account's login limit has been reached". Users also have the option to "Logout and Continue"; this will log out a user from all previous sessions and allow login into a new session.

  10. The availability of Time-based One-Time Password and One-Time Password as a two-factor authentication method is subject to your subscribed service plan. In case you lose access to your mobile device and recovery codes, or have used all of the recovery codes, you can ask your enterprise admin to reset the two-factor authentication (2FA) against your account.

  11. Once the enterprise administrator enforces a Time-based One-Time Password as a secondary authentication method on a role, and a user under that role does not have two-factor authentication (2FA) configured at the time of login, they will be prompted with a 'Configure Two Factor Authentication' dialogue to set up and provide a Time-based One-Time Password. If the user has already configured two-factor authentication (2FA), they will be prompted to provide the Time-based One-Time Password from the authenticator app configured on their mobile device.

  12. To configure the two-factor authentication (2FA), the user will need to install an authenticator app (Google Authenticator, Microsoft Authenticator, etc.) on their mobile device. The 'Configure Two-Factor Authentication' dialogue shown to the user will contain:

    • QR Code

    • Manual Key

    Recovery CodesTo set up two-factor authentication (2FA), the user can either scan the QR code or manually enter the Manual Key into an authenticator app. After successful registration, the user must provide the Time-based One-Time Password (TOTP) generated by the app to proceed in SigningHub. A set of recovery codes is also provided in the configuration dialog, which can be used in place of a TOTP to regain access if the user loses access to their mobile device. Each recovery code is valid for one-time use only, and it is strongly recommended to store them in a secure location. Users can regenerate a new set of recovery codes anytime from the Manage Two Factor Authentication (2FA). If an enterprise user loses access to both their mobile device and recovery codes, or has used all of them, they can contact their enterprise administrator to reset the two factor authentication (2FA) for their account.

  13. If the 'Trusted Device Authentication' option is enabled in Configurations > Enterprise > Advanced Settings, then device authentication will be enforced for all users under that enterprise. Upon successful login, if the browser or device is not already registered with SigningHub, the user will be prompted with a One-Time Password (OTP) screen. The available OTP methods will be shown based on the Service Plan and Enterprise Role's Secondary Authentication Settings, allowing the user to select from the configured methods such as Email, SMS, or TOTP.

  14. Once the user successfully completes the OTP verification, the device/browser will be marked as trusted, and future logins from that environment will bypass the OTP screen unless the cookies are cleared or the device is explicitly removed from the trusted list. An email notification will also be sent to the user, containing details such as the browser name and version, operating system, device mode, CPU type, and login location. This helps users stay informed about new trusted devices and detect any unauthorised access attempts.

  15. When an enterprise URL is entered in the browser, the background and slider images defined in that enterprise’s branding settings are applied. If no customisation has been made, the default background and slider images set in SigningHub Admin are used. Similarly, when the default SigningHub URL is entered, the login page will always display the background and slider images configured in SigningHub Admin.


Last updated

Was this helpful?