A Guide to ‘Security Settings’ on SpringVerify

A Guide to ‘Security Settings’ on SpringVerify

What are the ‘Security Settings’ features on SpringVerify?

‘Security Settings’ features are the second layer authentication mechanism available to SpringVerify customers to improve protection against threats to the access and usage of candidate/company data.

NOTE: These settings are applicable to users and not to candidates.

Login Methods

  • Authenticate a user to log into the SpringVerify portal using a specific login method (User ID -Password, Google SOS, Microsoft account, etc…). Enabling or disabling certain login methods for your user will allow or restrict logging into the SpringVerify portal, respectively.
  • Example:  
    • If you enable only google login for your company, users can log in to SpringVerify using their Gmail account only. No user will be able to login using ID-password or Microsoft account.
    • This scenario is helpful when a user leaves your organization and no more has access to their official Gmail account. They won't be able to login to SpringVerify using their ID-password as the password login is disabled for your organization.


Password Expiry

  • Password expiry helps to foil an attacker who intercepts or guesses the older password for any users in your workspace. Enabling this setting will mandate all your users to change their SpringVerify login password after certain days. 
  • Example: If you enable, Password Expiry settings for 15 days, it will mandate all users to change their password, every 15 days to access their SpringVerify account.


Domain Whitelist

  • Domain Whitelist security settings prevent unauthorized access to your data by people outside our organization or with email IDs from a different domain.
  • Example: If you enable a domain Whitelist for @springverify.com, any user with different domains (such as abc@springverify.in) will not be allowed to log in to your SpringVerify workspace. 


Auto-Log out

  • Protect your workspace from unauthorized access by automatically logging out users from the SpringVerify portal after a certain period of inactivity.
  • Example: If you enable Auto-log out period for 3 hours, any user who is inactive on this portal will be logged out and will be asked to log in again to access SpringVerify.



Got more clarifications to make about your SpringVerify account? Write to us at cs@springverify.com


    • Related Articles

    • SpringVerify Dashboard Related FAQs

      Q. Can HR select the checks on the dashboard before initiating the case? Yes, HR can select the preferred package and add any specific checks for each candidate. Here’s how: Step 1: Add Candidate Step 2: Select Packages and Add-on checks When you ...

    • SpringVerify India - APIs Documentation

      Introduction Welcome to SpringVerify India API Documentation. The endpoints exposed in this documentation are to initiate background verification of a candidate and query the verification report. The SpringVerify India API is organized around REST. ...

    • Additional Cost Settings

      What is an additional cost? Additional costs are the charges that either a university or the ex-employer charges SpringVerify to provide us with the candidate’s data. These additional costs will get Charged by the universities and companies who hire ...

    • How to generate an API key on SpringVerify portal?

      Steps to generate API token on SpringVerify 1. Log into your SpringVerify account with your login credentials 2. Go to Profile (top right corner) 3. Click Setting from the Dropdown 4. Navigate to API section 5. In this section, click on Generate ...

    • Integration of SpringVerify with Recruitee

      Overview: This guide provides step-by-step instructions for integrating SpringVerify with Recruitee, allowing you to perform background checks on candidates within the Recruitee platform. Prerequisites: Access to the SpringVerify Access to the ...