Litmus Enterprise: Advanced Security & Privacy Settings

Available exclusively to Litmus Enterprise customers, Enterprise Security provides an additional level of security to further protect Enterprise accounts. Litmus Enterprise customers can utilize Enterprise Security features, like two-step verification, custom session lengths, customizable password settings and single sign-on (SSO) for full control over their Litmus account and to further protect their business.

TWO-STEP VERIFICATION Litmus Enterprise customers have access to five versions of two-step verification:

  1. Individually-enforced
  2. Account-wide requirement (all subaccounts and parent account)
  3. Parent account requirement
  4. Subaccount requirement (all subaccounts)
  5. Subaccount requirement (only select subaccounts)

Individually-enforced two-step verification Within your personal security settings, you can turn on two-step verification as an added level of security on your account. This will force you to follow an SMS-based two-step verification experience for every login and at least once every 30 days.

Account-wide required two-step verification To further protect their business and their users, Account Holders can enforce two-step verification as an added level of security on their entire account (includes the parent account and all subaccounts). Once enforced, two-step verification requires all users to follow an SMS-based two-step verification experience for every login and at least once every 30 days.

If the account-wide setting is enforced, users will not be able to edit their individual settings to turn off two-step verification.

Note: Account-wide two-step verification settings are only available within the team security settings on the parent account. Once implemented, it impacts the parent account and all subaccounts. Both boxes must be checked to implement this (see screenshot below).

Two-Step Verification

Parent account requirement To further protect their business and their users, Account Holders can enforce two-step verification as an added level of security on just their parent account. Once enforced, two-step verification requires all users on the parent account to follow an SMS-based two-step verification experience for every login and at least once every 30 days.

Note: Parent account two-step verification settings are only available within the team security settings on the parent account. Once implemented, it impacts the parent account only (checking only the first box in the screenshot above).

Subaccount requirement (all subaccounts) To further protect their business and their users, Account Holders can enforce two-step verification as an added level of security on just the subaccounts (and not parent account).

If enforced, users will not be able to edit their individual settings to turn off two-step verification.

Note: Subaccount two-step verification settings are only available within the team security settings on the parent account. Once implemented, it impacts only subaccounts (checking only the second box in the screenshot above).

Subaccount requirement (only select subaccounts) To further protect their business and their users, Account Holders can enforce two-step verification as an added level of security on select subaccounts.

If enforced, users will not be able to edit their individual settings to turn off two-step verification.

Note: In order to turn on two-step verification on the subaccount level, Account Holders will need to uncheck the second box within the security settings of the parent account. They can then go into each subaccount and turn two-step verification on / off for each subaccount in the security settings.

CUSTOM SESSION LENGTHS To further protect Litmus accounts from unauthorized access, Account Holders can add customizable session lengths so idle Litmus accounts will be automatically logged out after a specified time frame.

Note: Custom session lengths are customizable at the subaccount level and not universal across all accounts.

CUSTOM PASSWORD SETTINGS Customizable by password character diversity, blacklisting, and reuse parameters, Account Holders can set minimum requirements for passwords on their account. It includes:

Password Character Diversity: Enforce a baseline of complexity for passwords by requiring any number of digitals, symbols, uppercase, and lowercase characters.

Password Blacklisting: Blacklist prefixes and fields can be used to prevent common phrases (such as “password” and “1234”) from being included in a password.

Password Expiry and Reuse: Setting an expiry will ensure passwords change on a regular basis. Configure how many password changes are required before a password can be reused, or prevent reusing passwords altogether.

Note: Custom password settings are customizable at the subaccount level and not universal across all accounts.

SINGLE SIGN-ON WITH SAML Single sign-on (SSO) powered by SAML lets you easily authenticate and manage user access, while your team enjoys a streamlined login process—access to Litmus with a single click. Learn more about enabling SSO with SAML and your Identity Provider.

Still need help? Contact Us Contact Us