Solink supports single sign-on (SSO) over SAML 2.0, so your team signs in to Solink with the same corporate credentials they already use. Your IT team keeps control of who has access, and users have one less password to manage.
This guide is intended for IT administrators who manage your organization's identity provider (IdP).
Supported Identity Providers
Solink works with any identity provider that supports SAML 2.0.
Examples include:
Microsoft Entra ID (formerly Azure Active Directory)
Okta
OneLogin
JumpCloud
SSO Flow Types
Solink supports both of the following SSO flow:
IdP-Initiated: Users log in by clicking the Solink title from your corporate dashboard.
SP-Initiated: Users visit solinkcloud.com, enter their email, and are redirected to your IdP.
How Users Sign In
Solink supports both SAML sign-in flows, so users can start from either place.
Flow | Where the user starts | What happens |
IdP-initiated | Your corporate app dashboard | User selects the Solink tile and lands in Solink, already signed in. |
SP-initiated | User enters their work email, is redirected to your IdP to sign in, then returns to Solink. |
How to Configure SSO
Before you begin, ensure the following:
Get your customer identifier. Your Solink Customer Success Manager provides a unique identifier for your organization. It appears as XXXXX in the values below; replace every instance with your own.
Decide on provisioning. If you want your IdP to assign each user's Solink role and locations, plan your role values and location groups now (see step 2).
Step 1
Create a new SAML 2.0 application for Solink and enter the values below. Replace XXXXX with your customer identifier.
Setting | Value |
SP Entity ID (Identifier / Audience URI) | urn:auth0:solink:XXXXX |
Reply URL (Assertion Consumer Service URL) |
Then map these two required user attributes (claims):
Attribute | Contains | Claim URI |
name | User's full name | |
User's email address |
Step 2
Skip this step if you manage roles and location access inside Solink. To have your IdP control them instead, add these attributes:
Attribute | Contains | Example |
role | The user's Solink role. One value per user. | Manager |
locationGroups | Comma-separated location group IDs defined by your team | WEST,EAST |
locationList | Comma-separated store numbers. Must match store numbers in an existing data integration. | 1001,1002,1045 |
Rules to follow:
Include locationGroups, locationList, or both. At least one is required.
To grant access to every location, set either attribute to ALL_LOCATIONS.
Values are case-sensitive: Manager and manager are different.
Every role and location group must already exist in Solink. Send your list to your CSM and Solink can help set them up.
Don't put individual store numbers in locationGroups; use locationList for those.
Step 3
Email your CSM:
Your IdP Sign-on URL
Your X.509 signing certificate
The email domains your users sign in with
Optional: your federation metadata XML or metadata URL (Entra ID and ADFS generate this automatically)
Optional, if using step 2: your list of roles and location groups
Solink validates the configuration and completes the setup.
Need Help with SSO?
To enable SSO, set up role and location provisioning, or troubleshoot a connection, contact your Customer Success Manager or email product@solinkcorp.com.