Glup fra Visma SmartSkill

This document describes the integration between eADM and Glup, a learning platform from Visma SmartSkill developed for Norwegian municipalities. The integration automates the management of users, departments, and roles in Glup based on data from your organization's Human Resources (HRM) system.

Overview

The integration transfers users, departments, and their associations from eADM to Glup. It automatically creates, maintains, and deactivates user accounts in Glup based on information from the HRM system. Users are created with the correct department affiliation and position code. When an employee changes departments, their affiliation is updated accordingly in Glup. The integration also maintains the organizational hierarchy and assigns users the correct role, either "employee" or "manager". If an employee leaves the organization or changes positions, their Glup account is automatically deactivated.

For more information on the integration please see; https://www.smartskill.no/glup

Pre-configuration

Before the configuration process can begin, the following preparatory steps must be completed:

1. Order the Integration: You must first contact Identum to order the integration.

2. Obtain API Access: After you place the order, we will contact Visma SmartSkill to get the necessary API access that eADM requires.

Configuration

Once the prerequisites are met, we will schedule a technical meeting to finalize the setup.

Workshop Agenda:

• Define which users and departments will be exported from eADM to Glup.

• Determine which data attributes to export for each user.

• Establish the rules for assigning "manager" and "employee" roles in Glup.

• Decide if existing users and departments in Glup need to be linked to their counterparts in eADM.

The integration can be activated as soon as these points are clarified.

Connecting to Existing Data

Linking to Existing Users

To connect employees from your HRM system to existing user accounts in Glup, both systems must have a matching unique identifier.

Warning: You must ensure that the user's email address in Glup matches their work email or UserPrincipalName (UPN) in Azure AD. If your organization uses Visma Connect for Glup authentication, the email address in Glup must match the one registered in Connect. Failure to do this will result in duplicate user accounts.

Linking to Existing Departments

You have two options for handling the organizational structure in Glup.

• (Recommended Method) Visma SmartSkill recommends that eADM creates a new, separate organizational structure in Glup that mirrors the structure in your HRM system. All course history in Glup is tied to the individual user, not the department. Unmatched users will remain in the old structure, making cleanup easier later. Visma Smartskill can assist with this cleanup process after the integration is active.

• Alternative Method: Matching Existing Structure If you choose to link to the existing organizational structure, departments in eADM and Glup must share a matching unique ID. This ID is typically a serial number for the department that is sourced from the HRM system and can be found in eADM.

Warning: You must enter this ID into the department's ID field in Glup. In Glup, this ID often follows the format HRM_<kommuneid>-<Avdelingsnummer>; it is critical that this value is changed to match the "Organizational ID" of the department in eADM. If this is not done, you will create duplicate departments. Other values, like a unit number from Visma HRM, can be used by agreement with your Identum consultant.

Example Data Mapping

The following table shows a typical mapping of user attributes from eADM to Glup.