This guide will help you on how to connect your domain to LottieFiles using Single Sign-On (SSO) and SAML, ensuring a seamless login experience for your team.
Prerequisites
1. To use the Single Sign-On (SSO) / SAML feature, you must be on a LottieFiles Enterprise plan.
2. Only the Workspace Owner and Admins have access to enable and manage SAML & SSO settings.
Step 1: Access Workspace Settings
-
Log in to your LottieFiles account.
-
Navigate to Workspace Settings > click on Access & SSO settings
Step 2: Connect Your Domain
-
On the Access & SSO Settings tab, locate the option to Add a domain to your organization.
- Click on + Add Domain and enter your domain to initiate the connection.
-
This allows you to set up SSO with your Identity Provider (IdP), such as Okta, Azure AD, or others.
Step 3: Configure SAML Settings with Your IdP
-
After initiating the domain connection, you’ll be redirected to the Integration page.
-
Follow the step-by-step instructions provided, tailored to your specific IdP setup.
Step 4: Complete the Setup
- Follow the on-screen instructions carefully to finalize the integration.
- This process typically involves authenticating and linking your external identity provider with LottieFiles.
Step 5: Verify the Integration
-
Once setup is complete, the SSO integration status will be displayed as active in your Workspace Settings.
Once enabled, all users will be required to log in via your Identity Provider (IdP) to access the workspace.
⚠️ Important Note:
If you have an existing LottieFiles account created before setting up the Single Sign-On (SSO) integration, you'll need to link your account to SSO in order to log in using your SSO credentials.
For step-by-step guidance, please refer to this article: How to link your existing account to SSO login?
Need Help?
If you encounter any issues or have questions during the setup process, please contact our support team at support@lottiefiles.com.
If you're escalating an SSO login issue to Support Team, please include:
- the affected user's email
- a brief description of the issue, any error messages or screenshots
- the name of your identity provider (e.g., Okta, Azure AD).
The more details you provide upfront, the faster we can help troubleshoot and resolve the problem.
Updated
Comments
0 comments
Please sign in to leave a comment.