The Integration section has been designed to assist you in securely and seamlessly connecting Lemon Learning to your digital environment. It centralizes all the information needed to choose, prepare, and configure the integration method best suited to your tools, IT constraints, and adoption goals.
Integration Overview: Explore the different available approaches (browser extension, native integration, etc.) and their specific use cases.
Technical Prerequisites & Architecture: Identify key requirements upfront: compatibility, access rights, technical structure, access governance, and security policies.
Step-by-Step Implementation Guides: Access clear, methodical instructions for every integration scenario.
Best Practices & Recommendations: Save time and ensure a future-proof integration with technical advice drawn from our most successful client implementations.
Testing & Validation: Learn how to verify your integration, manage a pilot phase, and securely transition to production.
IT Teams: Integration, Security, Network, and Governance specialists.
Platform Technical Administrators.
Digital and Business Project Managers responsible for the rollout.
Specialized Teams: SaaS, Digital Workplace, SSO, and Application Integration experts.
Every organization is unique — which is why this section provides both a solid foundation and advice that can be adapted to your specific constraints. Your Lemon Learning Project Manager remains by your side to guide you, answer your questions, and guarantee a successful integration.
The Player is the primary extension, which will be installed on your end-users' workstations. It is used to run the content previously created using the Editor.
The Editor is used to create the content that your end-users will view through the Player. Generally, this extension is only installed on a limited number of workstations.
Extension-based integration is typically chosen in the following cases:
No access to the application’s source code
Security constraints
Business constraints
Direct integration is typically chosen in the following cases:
Access to the application’s source code is available
Specific differentiation variables are only accessible within the tool (e.g., user roles, specific metadata, etc.)