For the security conscious amongst you (isn’t that everyone these days?), our recent product improvements might be interesting…
Every individual user account on GeckoEngage (but not Chat, for the moment) can now enable two-factor authentication (2FA).
2FA is an extra layer of security used to make sure that people trying to gain access to an online account are who they say they are.
In addition to a username and password, a user selects an additional method of authentication (such as receiving a temporary passcode via text), making it harder for others to impersonate them and gain access to their account. For more information on how 2FA works with your Gecko account, and how to get set up, please see this article.
Single sign-on (SSO) also helps secure your GeckoEngage accounts, but in a different way.
SSO can allow users to login to their Gecko accounts using existing login credentials from third-party accounts, such as Microsoft and Google.
(You may have seen this on many popular websites, where you can sign up for services using your Facebook, Google, Microsoft or LinkedIn credentials. This is single sign-on in action.)
Why is this useful?
Many institutions use a single sign-on provider (such as Microsoft) to allow their staff members to access various tools. Using these same login credentials to access GeckoEngage gives administrators more control.
- New users do not have to setup a password to access the system. This streamlines the process for onboarding new users.
- Lapsed users (such as colleagues who have left the institution) do not have to be manually removed from your Gecko account. When their SSO account is disabled (via Microsoft in the example above), the user is automatically locked out of Gecko too.
Jonny has written this short article on what you need from your IT team in order to set this up.
If you’d like to learn more about how SSO can be enabled for your institution please reach out to our Customer Success team.