diff --git a/connection-guides/lms/360learning.mdx b/connection-guides/lms/360learning.mdx
index 50f01b5..a4ce3fa 100644
--- a/connection-guides/lms/360learning.mdx
+++ b/connection-guides/lms/360learning.mdx
@@ -85,6 +85,39 @@ You can use the Company ID and API Key to link your 360 Learning account.
+## SSO Configuration
+
+Proper SSO (Single Sign-On) configuration is essential for the 360 Learning integration to work correctly. The configuration ensures that users are properly identified and matched between your platform and 360 Learning.
+
+
+ Before configuring SSO, check the authentication approach with your content provider to ensure compatibility and proper user mapping.
+
+
+### Configuration Options
+
+The SSO configuration should use the following approach:
+
+#### Custom Field Configuration
+
+
+ Configure a custom field called `lms_user_id` and set it to the **Email** field value.
+
+
+
+ Ensure the `lms_user_id` custom field is properly populated and accessible through the SSO configuration.
+
+
+
+
+ **Important:** Misconfigured SSO settings can result in users being unable to access their learning content or receiving incorrect learning records. Always verify the field mapping is accurate.
+
+
+### Customer Responsibility
+
+- Ensure the Email field is correctly populated in your user management system
+- Verify that the SSO configuration matches the authentication method used by 360 Learning
+- Test the SSO flow with a small group of users before full deployment
+
## Useful Links
diff --git a/connection-guides/lms/brainier.mdx b/connection-guides/lms/brainier.mdx
index dee2196..0fae262 100644
--- a/connection-guides/lms/brainier.mdx
+++ b/connection-guides/lms/brainier.mdx
@@ -98,6 +98,39 @@ Click **Test Connection** to verify that the credentials are correct.
+## SSO Configuration
+
+Proper SSO (Single Sign-On) configuration is essential for the Brainier integration to work correctly. The configuration ensures that users are properly identified and matched between your platform and Brainier.
+
+
+ Before configuring SSO, check the authentication approach with your content provider to ensure compatibility and proper user mapping.
+
+
+### Configuration Options
+
+The SSO configuration should use the following approach:
+
+#### Custom Field Configuration
+
+
+ Configure a custom field called `lms_user_id` and set it to the **User ID** field value.
+
+
+
+ Ensure the `lms_user_id` custom field is properly populated and accessible through the SSO configuration.
+
+
+
+
+ **Important:** Misconfigured SSO settings can result in users being unable to access their learning content or receiving incorrect learning records. Always verify the field mapping is accurate.
+
+
+### Customer Responsibility
+
+- Ensure the User ID field is correctly populated in your user management system
+- Verify that the SSO configuration matches the authentication method used by Brainier
+- Test the SSO flow with a small group of users before full deployment
+
## Content Visibility
In order for a user to be able to view content either on the UI or in the API, they need to be assigned to the content. This can be done directly or by bring
diff --git a/connection-guides/lms/cornerstone_library_single_tenant.mdx b/connection-guides/lms/cornerstone_library_single_tenant.mdx
index 1bc0e0d..fa52728 100644
--- a/connection-guides/lms/cornerstone_library_single_tenant.mdx
+++ b/connection-guides/lms/cornerstone_library_single_tenant.mdx
@@ -1,6 +1,6 @@
---
-title: "Cornerstone Library (Single Tenant)"
-description: "Follow these steps to connect Cornerstone Library (Single Tenant) via the StackOne Hub successfully."
+title: "Cornerstone (1:1 Connector)"
+description: "Follow these steps to connect Cornerstone (1:1 Connector) via the StackOne Hub successfully."
---
import IntegrationFooter from "/snippets/integration-footer.mdx";
@@ -16,4 +16,37 @@ import IntegrationFooter from "/snippets/integration-footer.mdx";
+## SSO Configuration
+
+Proper SSO (Single Sign-On) configuration is essential for the Cornerstone (1:1 Connector) integration to work correctly. The configuration ensures that users are properly identified and matched between your platform and Cornerstone.
+
+
+ Before configuring SSO, check the authentication approach with your content provider to ensure compatibility and proper user mapping.
+
+
+### Configuration Options
+
+The SSO configuration should use the following approach:
+
+#### Custom Field Configuration
+
+
+ Configure a custom field called `lms_user_id` and set it to the **username or user id** field value.
+
+
+
+ Ensure the `lms_user_id` custom field is properly populated and accessible through the SSO configuration.
+
+
+
+
+ **Important:** Misconfigured SSO settings can result in users being unable to access their learning content or receiving incorrect learning records. Always verify the field mapping is accurate.
+
+
+### Customer Responsibility
+
+- Ensure the Username or User ID field is correctly populated in your user management system
+- Verify that the SSO configuration matches the authentication method used by Cornerstone
+- Test the SSO flow with a small group of users before full deployment
+
diff --git a/connection-guides/lms/docebo.mdx b/connection-guides/lms/docebo.mdx
index c0b8548..a108c32 100644
--- a/connection-guides/lms/docebo.mdx
+++ b/connection-guides/lms/docebo.mdx
@@ -127,3 +127,36 @@ description: "If you've been directed to StackOne to integrate with Docebo, the
+
+## SSO Configuration
+
+Proper SSO (Single Sign-On) configuration is essential for the Docebo integration to work correctly. The configuration ensures that users are properly identified and matched between your platform and Docebo.
+
+
+ Before configuring SSO, check the authentication approach with your content provider to ensure compatibility and proper user mapping.
+
+
+### Configuration Options
+
+The SSO configuration should use the following approach:
+
+#### Custom Field Configuration
+
+
+ Configure a custom field called `lms_user_id` and set it to the **User ID** field value.
+
+
+
+ Ensure the `lms_user_id` custom field is properly populated and accessible through the SSO configuration.
+
+
+
+
+ **Important:** Misconfigured SSO settings can result in users being unable to access their learning content or receiving incorrect learning records. Always verify the field mapping is accurate.
+
+
+### Customer Responsibility
+
+- Ensure the User ID field is correctly populated in your user management system
+- Verify that the SSO configuration matches the authentication method used by Docebo
+- Test the SSO flow with a small group of users before full deployment
diff --git a/connection-guides/lms/oracle.mdx b/connection-guides/lms/oracle.mdx
index 3819857..ab728ba 100644
--- a/connection-guides/lms/oracle.mdx
+++ b/connection-guides/lms/oracle.mdx
@@ -3,6 +3,8 @@ title: "Oracle"
description: "If you've been directed to StackOne to integrate with Oracle, the following steps will help you understand the process and any necessary actions to configure successful integration."
---
+import IntegrationFooter from "/snippets/integration-footer.mdx";
+
This guidance assumes you have Admin privileges for your Oracle account.
@@ -37,6 +39,39 @@ description: "If you've been directed to StackOne to integrate with Oracle, the
+## SSO Configuration
+
+Proper SSO (Single Sign-On) configuration is essential for the Oracle integration to work correctly. The configuration ensures that users are properly identified and matched between your platform and Oracle.
+
+
+ Before configuring SSO, check the authentication approach with your content provider to ensure compatibility and proper user mapping.
+
+
+### Configuration Options
+
+The SSO configuration should use the following approach:
+
+#### Custom Field Configuration
+
+
+ Configure a custom field called `lms_user_id` and set it to the **Email or username** field value.
+
+
+
+ Ensure the `lms_user_id` custom field is properly populated and accessible through the SSO configuration.
+
+
+
+
+ **Important:** Misconfigured SSO settings can result in users being unable to access their learning content or receiving incorrect learning records. Always verify the field mapping is accurate.
+
+
+### Customer Responsibility
+
+- Ensure the Email or username field is correctly populated in your user management system
+- Verify that the SSO configuration matches the authentication method used by Oracle
+- Test the SSO flow with a small group of users before full deployment
+
## Useful Links