Sign-in and identities
Use existing sign-in methods through SAML, LDAP or JWT in appropriate scenarios.
TUTORize Integrations
Integrate TUTORize into your existing IT environment.
Whether it's signing in, managing users or handling training data, TUTORize can be connected to existing IT processes through different methods.
REST API, webhooks, single sign-on and file imports provide technical integration options. What matters is which data needs to be exchanged, which system is responsible and how the actual process should work.
TUTORize ISO 27001 certified · GDPR compliant · Hosted in Germany · Multi-tenant · SSO & REST API · AI optional
Explore integration optionsIntegration overview
Not every connection serves the same purpose.
An existing company login, a recurring user import and a course completion notification require different technical methods.
Users and organisational data
Import user information and supported group and assignment data through suitable interfaces or files.
Business data and events
Access supported data areas through the REST API and send defined events to other systems via webhooks.
Learning content and formats
Use SCORM, xAPI and cmi5 in their supported learning contexts.
This turns a general integration question into a specific technical task.
Identity & Access
Use existing identities for sign-in.
Employees should not need a completely separate sign-in process for every application. TUTORize supports different ways to connect existing identity systems.
SAML 2.0
Federated sign-in through a configured identity provider, such as Microsoft Entra ID (Azure AD) or ADFS.
LDAP / Active Directory
Authentication and, in appropriately configured scenarios, user synchronisation with an accessible directory service.
JWT SSO
Token-based sign-in for integration scenarios configured for this purpose.
The appropriate method depends on your existing identity architecture and operating model. Successful sign-in does not automatically mean that all HR data or group assignments are continuously synchronised.
SAML in detail
More than just sign-in – but not a complete HR data sync.
With a SAML connection to, for example, Microsoft Entra ID or ADFS, additional supported identity information can be processed alongside sign-in.
Provision users at sign-in
Users can be created automatically within supported SSO scenarios.
Import profile information
Supported master data can be transferred and updated during sign-in.
Assign groups and roles
Transmitted group information and remote role mapping can be taken into account in the agreed configuration.
Certificates and identity providers
SAML certificates are part of the configuration. The documented standard model provides for one identity provider per TUTORize account.
Important for planning: Importing group information at sign-in is not a complete group reconciliation. In particular, it does not imply that obsolete group assignments are automatically removed.
Programming interface
Connect the specific data areas you need.
The TUTORize REST API allows supported functions and information to be incorporated into technical processes involving other applications.
Users and progress
Use user data and supported learning progress information for defined scenarios.
Groups and assignments
Include organisational groups and functional assignments via the relevant API functions.
Courses and knowledge
Access supported information on courses, events, learning paths and knowledge entries.
Roles and rooms
Include supported role and room data in integration processes.
The read or update operations actually available depend on the endpoint, permissions and implementation. An API does not automatically provide bidirectional synchronisation for all objects.
A more detailed interface description for developers is available on request.
Event-driven processes
Pass relevant events to other systems.
Some integrations do not need the complete data set, but rather a notification when a particular event occurs.
TUTORize supports webhooks for defined events. Documented examples include:
Course or learning path completed
Use a completion as the starting point for a downstream process.
Approval status changed
Take into account approval status changes for supported course or learning path objects.
How the receiving system processes the information and which additional data is needed is defined in the integration scenario.
Webhooks complement the REST API. They are not a replacement for complete master data reconciliation and are not guaranteed for every possible event.
File-based exchange
Import user data. Export selected information.
Not every use case requires a permanently operated interface from the outset. TUTORize supports user imports via CSV, XLS and XLSX as well as CSV exports for defined data areas.
Import users and master data
Import supported user information such as names, email addresses, personnel numbers and organisational details.
Update existing profiles
Maintain existing master data using supported import functions.
Include groups and roles
Include group assignments in import scenarios. According to documented behaviour, these assignments are added through file imports, not automatically fully replaced or removed.
Export users and training information
Use supported user and training data as CSV files for defined downstream processes.
For recurring imports, you must therefore clarify which fields will be updated and how existing groups and roles will be handled.
Learning standards
Provide learning content in supported standards.
Alongside IT and identity interfaces, TUTORize also supports common standards for digital learning content and learning activities within learning management.
SCORM
Use standardised e-learning packages within the supported LMS functionality.
xAPI
Process learning activities within supported xAPI scenarios.
cmi5
Use cmi5 for learning content supported accordingly.
These standards concern learning content and learning data. They do not replace user management, SSO or generic connections between arbitrary business systems.
Practical applications
From technical method to specific use case.
Sign in with the company account
Employees authenticate via a connected identity provider in a supported SSO scenario.
Import users from existing data
User and organisational information is included through an agreed file import or suitable API functions.
Use learning information in downstream processes
Supported progress data is accessed through the REST API for a defined administrative or business process.
React to learning events
A supported course or learning path event can be sent to another system via a webhook.
Every scenario requires a review of the systems involved, access rights and available data. This does not imply that preconfigured connectors are available for any third-party system.
Technical planning
Clarify data ownership first. Then choose the interface.
1. Systems and owners
Determine which system is responsible for users, organisational data and functional information.
2. Data and exchange direction
Define which information is needed, when it is needed and whether it must be read, created or updated.
3. Sign-in and data methods
Select identity integration, REST API, webhooks and file transfer according to their respective purposes.
4. Changes and errors
Review group changes, deactivations, incomplete records, permissions and technical errors before going live.
This helps distinguish early on what can be implemented with existing functionality and where additional configuration or custom integration is needed.
Frequently asked questions
What should your IT team know in advance?
Does TUTORize support SSO with Microsoft Entra ID?
Yes. SAML 2.0 integration with Microsoft Entra ID (Azure AD) or ADFS is supported. Configuration and the information transferred are agreed upon.
Can users be created automatically when signing in via SSO?
Yes. TUTORize supports auto-provisioning in appropriately configured SSO scenarios. This does not automatically include continuous, complete synchronisation of HR master data.
Are groups fully reconciled during SAML sign-in or file import?
Not by default. With SAML, group information can be imported during sign-in; this does not imply automatic removal of obsolete group assignments. In documented file imports, groups and roles are added but not automatically fully reconciled.
What information can we connect through the REST API?
Supported areas include users and progress, groups and assignments, courses and learning paths, knowledge entries, and roles and rooms. The exact operations and permissions are reviewed for each integration scenario.
Can data be imported or exported without a custom API integration?
Yes. CSV, XLS and XLSX imports are available for users. TUTORize also supports CSV exports of selected user and training information.
Can multiple identity providers be configured for one TUTORize account?
The documented SAML standard model provides for one identity provider per account. If multiple identity sources are required, the appropriate architecture must be assessed for the specific use case.
Next step
Discuss your integration requirements with us.
Which identity systems do you use? Where does user and organisational data come from? Which information needs to be exchanged between systems?
In a technical discussion, we review your target processes and assess which TUTORize interfaces, standards and configurations fit your requirements.