---
title: "exSsoLoginSaml"
canonical: "https://help.agiloft.com/space/HELP/65242467/exSsoLoginSaml"
format: markdown
---
Once the integration is complete, users can access Agiloft CLM with SAML 2.0 SSO. Follow the steps below to locate the SAML SSO login URL and share login details with your users.

> 📝 If you're supporting multiple SAML IdPs and haven't set up profiles for all providers, you might want to wait and perform these steps once all the setup is complete. That way you can send out all of the login URLs at once.

1. Retrieve the SSO URL for your KB:
  1. Go to **Setup > Access > Configure SAML 2.0 Profiles**.
  2. Edit the profile for which you want to retrieve the SSO login URL.
  3. Go to the Service Provider Details tab.
  4. Copy the URL under Single Sign-On URL. Make sure you copy the complete URL.
  5. Go to the URL in a browser. Depending on how you configured SAML Authentication Profile in [Configure Service Provider Details](#service_provider), you are either prompted to log in to the IdP or are forwarded directly to the Agiloft user interface.
2. Depending on how you want users to access Agiloft, you can choose one or more of the following options:
  - Send the URL to all users who should log in via SP-initiated SAML SSO and ask them to bookmark it or add it to their favorites.
  - Add the URL to an existing webpage if you use a [custom login method](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/925466673). Then direct users to that page.
  - Set up IdP-initiated SSO and send users to the IdP to access the Agiloft CLM application. Refer to the documentation for your IdP to set up IdP-initiated SSO.
3. For logins from Agiloft Contract Assistant applications, tell users to click Login via SAML.
  If you set up multiple profiles, users see an additional dialog box after clicking Login via SAML. They need to select their provider from the drop-down list and click Login via SAML again.

4. If you manually created other hyperlinks for use in the system, you need to update those links to accommodate both SSO logins and standard login users. This step is only necessary for links you manually created. For information, see [Hyperlink Syntax and Examples](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718366).

> ℹ️ For system-generated email hotlinks, you don't have to make any changes to accommodate multiple SAML providers or SSO versus non-SSO users. Based on a user's login method, Agiloft CLM manages which hotlink URL they receive in email. Each time a user logs in, the system sets a hidden SSO Authentication Method field in the user's record. If a user logs in with a standard username and password, the value is `STANDARD`. If a user logs in with SAML 2.0 SSO, the value is `SAML20`. This value determines whether email hotlinks go to `login.jsp` or `samlssologin.jsp`. Don't edit a user's SSO Authentication Method because you might prevent them from accessing the system.

5. Finally, to make sure users can't circumvent SSO and log in to Agiloft directly, follow the instructions in [Force SSO Login](#force_sso) below.