Single Sign On (SSO)
      Back to home
      1. Knowledgebase
      2. User Management
      3. Single Sign On (SSO)

      Single Sign-On Best Practice

      This article will provide best practices for implementing SSO for your organisation.

      Implementing Gatekeeper SSO


      When implementing SSO (Single Sign-On), it's recommended that your IT lead or Gatekeeper admin should follow a careful deployment process to avoid locking all users out of your tenant - including the Gatekeeper support team. This article covers the recommended approach before configuring the SSO method.

      ⚠️ Note:

      • When implementing SSO, it is strongly recommended to select Allow All Authentication Methods. This ensures users aren't locked out of Gatekeeper if there are issues with your SSO configuration. See Manage SSO Integration for steps on how to do this.
      • If you require users to sign on using OneLogin, Okta, Microsoft, or SAML 2, it is strongly recommended to enable the Support Access toggle. This allows Gatekeeper staff (@gatekeeperhq.com) to bypass SSO and access your tenant for support purposes.
      • Communication - Inform your organisation about the upcoming change. Communicate the benefits of SSO and provide instructions on how they'll need to log in to Gatekeeper using the new method, including the rollout date.

      Note: If you restrict your Gatekeeper tenant to only allow one login type, the other options will remain on the log in screen, but users will not be able to use them. Ensure that all users are aware of the correct login method to avoid access issues.

      • Support Channels - Set up a dedicated internal support channel (e.g. a help desk or support email) for users who encounter difficulties with the new SSO setup. Provide clear instructions for users to seek assistance.
      • User Training - Provide training materials or sessions to guide users through the new SSO process, including how to log in to Gatekeeper and troubleshoot common issues.
      • Scheduled Downtime - Plan the SSO implementation during off-peak hours or weekends to minimise disruption.
      • Testing and Validation - Before full deployment, conduct thorough testing of SSO with a sample of users to ensure everything works as expected. Use the audit trail to verify successful logins.
      • Monitoring Post-Deployment - After deploying SSO, closely monitor and solicit user feedback and system logs to identify and address any unforeseen issues promptly.

      By following these steps and taking a cautious and gradual approach, you can manage the rollout successfully and minimise the risk of locking users out of your Gatekeeper tenant when implementing SSO.