> ## Documentation Index
> Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise Single Sign-On (SSO)

export const GCell = ({children, className}) => <div className={`grid-table-cell ${className || ""}`} role="cell">
    {children}
  </div>;

export const GTH = ({children, className}) => <div className={`grid-table-th ${className || ""}`} role="columnheader">
    {children}
  </div>;

export const GRow = ({children}) => <div className="grid-table-row" role="row">{children}</div>;

export const GBody = ({children}) => <div className="grid-table-body" role="rowgroup">{children}</div>;

export const GHead = ({children}) => <div className="grid-table-head" role="rowgroup">{children}</div>;

export const GTable = ({children, className, cols}) => <div className={`grid-table not-prose overflow-hidden rounded-2xl ${className || ""}`} style={{
  "--grid-table-cols": cols
}} role="table">
    {children}
  </div>;

Anaconda provides customers on Business or Custom plans the ability to authenticate with Anaconda products directly from their internal identity platform (IdP), via OpenID or SAML.

To make the setup and provisioning process for your employees even more seamless, Directory Sync (SCIM) is also available for many IdPs. Both SSO and SCIM support the automated provisioning of Anaconda products, but SCIM additionally enables bulk importing of employees from internal directories, management of employee access and permissions, and automated deprovisioning of Anaconda products from your IT infrastructure and HR workflows.

<Note>
  This service is offered to organizations that have five or more licensed organization members.
</Note>

## Setting up Enterprise SSO

Upon request, a self-service setup link will be emailed to you or to your IT representative. Click either **Configure Single Sign-On** or **Configure Directory Sync**, then follow the prompts for your IdP to set up your Anaconda SSO configuration.

To request a self-service setup link, please contact your dedicated Customer Service Manager (CSM) or [open a support ticket](https://support.anaconda.com/hc/en-us/requests/new).

<Accordion title="Supported Single Sign-On providers">
  <GTable cols="40% 30% 30%">
    <GHead>
      <GRow>
        <GTH>Provider</GTH>
        <GTH>SSO Support</GTH>
        <GTH>Directory Sync Support</GTH>
      </GRow>
    </GHead>

    <GBody>
      <GRow>
        <GCell>ADP</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Auth0</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>CAS</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>ClassLink</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Cloudflare</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>CyberArk</GCell>
        <GCell>Yes</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>Duo</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Entra ID</GCell>
        <GCell>Yes</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>Google Workspace</GCell>
        <GCell>Yes</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>JumpCloud</GCell>
        <GCell>Yes</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>Keycloak</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>LastPass</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Microsoft AD</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>miniOrange</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>NetIQ</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Okta</GCell>
        <GCell>Yes</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>OneLogin</GCell>
        <GCell>Yes</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>Oracle</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>PingFederate</GCell>
        <GCell>Yes</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>PingOne</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Rippling</GCell>
        <GCell>Yes</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>Salesforce</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Shibboleth</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>SimpleSAMLphp</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>VMWare</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Custom SAML</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Custom OIDC</GCell>
        <GCell>Yes</GCell>
        <GCell>—</GCell>
      </GRow>

      <GRow>
        <GCell>Custom SCIM</GCell>
        <GCell>—</GCell>
        <GCell>Yes</GCell>
      </GRow>

      <GRow>
        <GCell>Custom SFTP</GCell>
        <GCell>—</GCell>
        <GCell>Yes</GCell>
      </GRow>
    </GBody>
  </GTable>
</Accordion>

## Enterprise Managed Users

Enterprise managed users are accounts that your organization owns and governs, rather than the individual user. When you enable Enterprise SSO with SCIM, your organization members become enterprise managed users.

Unlike standard Anaconda accounts where individuals sign up on their own and join organizations through invitations, your IT team provisions and controls enterprise managed users entirely through your identity provider.

### Enterprise managed users vs. standard accounts

<GTable cols="30% 35% 35%">
  <GHead>
    <GRow>
      <GTH>Capability</GTH>
      <GTH>Standard account</GTH>
      <GTH>Enterprise Managed User</GTH>
    </GRow>
  </GHead>

  <GBody>
    <GRow>
      <GCell>Account creation</GCell>
      <GCell>Self-service signup</GCell>
      <GCell>Provisioned via SCIM by IT admin</GCell>
    </GRow>

    <GRow>
      <GCell>Authentication</GCell>
      <GCell>Email/password, social login, or SSO</GCell>
      <GCell>Organization's IdP (SSO) only</GCell>
    </GRow>

    <GRow>
      <GCell>Organization membership</GCell>
      <GCell>Can belong to multiple organizations</GCell>
      <GCell>Belongs to a single organization</GCell>
    </GRow>

    <GRow>
      <GCell>Deprovisioning</GCell>
      <GCell>User leaves organization voluntarily, or admin removes them</GCell>
      <GCell>Automated via SCIM when removed from IdP directory</GCell>
    </GRow>
  </GBody>
</GTable>

## Next steps

With SSO enabled, employees with matching domains in their email will be prompted to authenticate via your IdP when signing in to Anaconda. Signing in using SSO for the first time creates their Anaconda account, adds them to your organization with baseline permissions, assigns them a seat, and sends an organization access <Tooltip tip="A randomly generated string that proves your identity and permission to access resources like channels, packages, or APIs.">token</Tooltip> to their email.

Instruct your organization members to follow the steps in the email for authenticating to Anaconda by setting their organization access token. For more information about tokens, see [Tokens](/anaconda-platform/cloud/user/tokens).
