Skip to main content

SAP Litmos

Learning management integration

Use NIM to automate SAP Litmos user lifecycle provisioning, create teams, and add users to teams from trusted source data.

About the organizationOrganization name: LitmosOrganization type: Learning technology companyAreas of focus: Workplace learning, learning management, compliance training, and training content.Product website: LitmosOrganization website: Litmos

At a glanceDirect link to At a glance

The SAP Litmos integration connects Tools4ever NIM to learner accounts, teams, and team memberships. It supports reading and provisioning users, creating teams, and creating teams_users assignments. Use a connected HR system or database as the source for the identity data and eligibility rules that drive those changes.

Before you start: Arrange API access with Litmos and obtain the Tenant URL and Token. Follow the connection guide to test access by retrieving one user. Collect users, teams, and memberships before building matching rules.

Use SQL Server records to provision Litmos usersDirect link to Use SQL Server records to provision Litmos users

In this pattern, SQL Server is the identity data source and Litmos is the provisioning target. NIM collects database records, selects eligible people, matches existing learner accounts, and maps approved changes to the Litmos user operations. Configure and validate the pattern for your database schema and Litmos tenant before scheduling it.

  1. Follow the Microsoft SQL Server connection guide. Give the collection account read access to the table or view containing the identity data, then collect it in NIM.
  2. Confirm that each source person has a stable, unique identifier and the attributes required by the Litmos operation. Define which source records are eligible for a learner account.
  3. Collect the existing Litmos users. Configure an inter-system relation using a matching value actually available in both systems. Do not assume that the SQL primary key is also the Litmos user identifier. Use email only when it is guaranteed to be unique, stable, and consistently formatted for this process.
  4. Build separate filters for eligible people without a Litmos account and for matched accounts that need approved updates. Inspect the filter output for missing and duplicate identities.
  5. Create a Litmos user-create mapping for the first population and a user-update mapping for the second. Populate the fields required by your installed connector and tenant; define any team assignments separately.
  6. Add the mappings to a job. Evaluate one safe test record, check the planned user and attribute values, then run the approved test and verify the result in Litmos.
  7. Recollect the changed systems and evaluate again. Confirm that the new account now matches and is no longer selected for creation before using a recurring sync task.

Check the matching outcomesDirect link to Check the matching outcomes

Example source recordCollected Litmos matchExpected filter outcome
One eligible person with all required attributesNo matching userIncluded in the create population.
One eligible person with approved attribute changesExactly one matching userIncluded in the update population.
Missing identity key or ambiguous matchCannot establish one intended userExcluded from automatic provisioning for investigation.
Person outside the configured eligibility ruleAnyExcluded from these create and update populations.

These are selection rules to configure and validate, not automatic behavior supplied by the connection test. Define any deactivation or removal process separately from this initial create/update pattern.

This section covers SQL Server-to-Litmos identity provisioning. A Litmos-to-SQL Server export needs a separate destination schema, field mapping, write permissions, and validation of the intended reporting data; this pattern does not define that export.

Solutions This Integration SolvesDirect link to Solutions This Integration Solves

User lifecycle provisioning

Create, update, and delete SAP Litmos users from trusted source data as learners join, change roles, or leave.

  • Reduces manual learner account setup
  • Keeps user details aligned with lifecycle changes
Plan user lifecycle provisioning

Team provisioning

Create SAP Litmos teams and add users to teams through NIM automation.

  • Builds learning teams from source data
  • Reduces manual team and user assignment work
Connect SAP Litmos for team provisioning

GuidesDirect link to Guides

Connector repository

Browse the SAP Litmos connector repository on GitHub.

Supported operationsDirect link to Supported operations

Filter tables by supported operation

Showing 10 of 10 tables
TableReadCreateUpdateDelete
achievements
courses
teams
teams_admins
teams_courses
teams_leaders
teams_teams
teams_users
users
users_customfields