Encircle Single Sign-On

If you are interested in adding SAML SSO, please contact your Customer Activation Manager.

Encircle supports SAML (Security Assertion Markup Language) authentication for Single Sign-On (SSO). SAML lets users sign in with their existing corporate credentials instead of managing separate login credentials for the Encircle application.

In this article:

 

Prerequisites

Your Requirements

Technical Contact

Please designate a dedicated IT contact who:

  • Has permissions to configure your IdP, and
  • Can participate in testing and go-live coordination.

Identity Provider (IdP)

You will need administrator access to one of the following (or any SAML 2.0–compliant IdP):

  • Entra ID (formerly Azure Active Directory)
  • Google Workspace
  • Active Directory Federation Services (ADFS)
  • Another SAML 2.0–compatible provider

Domain Management

You must have control over the email domains that should use SSO (e.g. @company.com, @subsidiary.com).

Preparation Time

Your IT team should:

  • Confirm your preferred IdP, and
  • Ensure any internal pre-configuration (groups, access policies, etc.) is in place before we go live.

 

Implementation Process

At a high level, our typical setup includes three phases: configuration, testing, and production rollout. We will work with your IT contact throughout these stages.

Phase 1: Initial Configuration

Together with your IT contact, we will:

  • Create the SAML application in your IdP
  • Configure SSO on Our Side

Phase 2: Testing

We recommend validating configuration in a test or staging context before enabling SSO in production.

Phase 3: Production Rollout

Once testing is complete:

  • Go-Live Planning
  • Enable SSO in Production

 

Common Questions

Can we use multiple email domains?

  • Yes. We can map multiple domains (for example, @company.com, @subsidiary.com) to the same SSO connection. Additional domains can be added later if needed.

What if users cannot log in after SSO is enabled?

If there are login issues after go-live:

  • Your IT team can verify:
    • The SAML application is enabled, and the configuration hasn't changed.
    • The correct attributes (especially email) are being sent.
    • Any certificate or key used for signing is still valid.
  • On our side, we can:
    • Review logs to help identify the cause.
    • Temporarily disable SSO for your domain(s) if needed, which will revert users to the standard login flow while we investigate.

 

Updated

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request