Members can authenticate into Userled using Google authentication if they have a google email address. It's possible to login with email even if you've created the account via Google SSO, simply follow the login instructions once you select that option.

If you do not use Google SSO or prefer email login, you can login via email with our password-less email login. Every time you login, we'll send you a secure login URL to your email. The desktop app and browser should keep you logged in unless you logout of the app, clear history/cookies on the browser, or use private browsing mode.

Userled supports Enterprise SSO via the SAML protocol, enabling you to create authentication strategies for an Identity Provider (IdP). With Enterprise SSO, users can sign in seamlessly using their IdP's credentials and have their user data synchronized with Userled.

Currently, Userled offers direct integrations with Microsoft Azure AD, Google Workspace, and Okta Workforce as IdPs. However, you can also integrate with any other IdP that supports the SAML protocol. If you need a custom integration, or to upgrade to en Enterprise plan, please reach out to support@userled.io.

Once SAML is enabled, all members in your workspace will be required to login via SAML. They can login via your identity provider's website or by clicking the option to Sign in with SAML/SSO on the Userled login page. They will not be able to load Userled if they try to login with Google or email.

To enable SAML, you will need support from the Userled team and your Identity Provider (IdP) admin.

Each SSO Identity Provider requires specific information to create and configure a new Connection. Often, the information required to create a Connection will differ by Identity Provider.

To create a custom SAML Connection, you’ll need the Identity Provider Metadata URL that is available from the organization’s SAML instance.

Reach out to your Userled CSM in your shared Slack channel or via email emily@userled.io.

The Userled team will create a SAML configuration for your organisation and share with you the Single sign-on URL and the Audience URI (SP Entity ID) values that can be used by your IdP admin to create the SSO connection.

In order to integrate you’ll need the IdP Metadata URL.

Normally, this information will come from the organization’s IT Management team when they set up your application’s SAML 2.0 configuration in their Identity Provider admin dashboard. But, should that not be the case during your setup, here’s how to obtain them.

1. Enter Service Provider Details

Copy and Paste the Single sign-on URL and the Audience URI (SP Entity ID) into the corresponding fields for Service Provider details and configuration. For some SAML setups, you can use the metadata found at the SP Metadata link to configure the SAML connection.

2. Obtain Identity Provider Metadata
Copy the IdP Metadata URL from your SAML settings and share them with you Userled point of contact who will add it to your Userled Connection settings. Your Connection will then be linked and good to go!

3. Configure Attribute Mapping

Your IT management team may need to complete additional steps such as mapping IdP claims to user attributes and assigning selected users/groups in your IdP.