Skip to main content
All CollectionsIntegrationsIntegration Hub
Integration Hub: How To Remap User Fields
Integration Hub: How To Remap User Fields

Remapping Fields for Integrations Set Up in the Integrations Hub (Standard Integrations)

Camilla Orloff avatar
Written by Camilla Orloff
Updated over 2 months ago

In a standard integration, set up in the Integration Hub, information like job profile and department is mapped to a standard user data field in your HR or user management system.

If key information is stored in a different field, you may need to be remapped. This remapping process is available through our Support. Here's a quick guide to help you get started and understand the process.



What We Need from You

To complete the remapping, we require the following information:

  1. True Name of the Field:
    Provide the actual name of the field (from AD) that you want to remap*

  2. Sample Users and Field Data:
    Send us 3-5 sample users (email) and their value from the field you want to remap to. This helps us verify that we are mapping to the correct field, as similar field names may exist. Do not provide users from admin or skip list groups; instead, provide regular users as examples.

*Access to the Field: For Learningbank to remap fields, we must have access to the field through your provider's API (e.g., Entra ID). When we receive the field name verification test, it will be completed. If access is not available, you'll need to contact your provider to "expose" the field to Learningbank through their API.



The Remapping Process

  1. New Information Mapping:
    Once the remapping is done, all users will have their information updated in the new field (e.g., Department). These new departments will be created in Learningbank with a flat hierarchy.

  2. Setting Up the New Hierarchy:
    After remapping, you'll need to set up the new department hierarchy in the platform manually (if the remapping impacted the department field).

  3. Cleaning Up Old Data:
    The old field (e.g., the previous department structure) will remain in the system, and you must manually delete it. While we may assist with this, we recommend handling it internally to save time.

  4. Impact on Sharing Automatic Rules:
    If you have any automatic rules in Sharings set up based on the original field (e.g., Department), these will need to be updated to reflect the new field.

  5. Analytics Impact:
    Keep in mind that after the remapping, analytics will reflect the new department, permission type and or job profile (depending on which fields were remapped).


Support and Timeline

To start the process and get technical assistance, contact [email protected].

Summary Checklist ✅

  • Confirm Learningbank has API access to the field.

  • Provide the true name of the field and 3-5 sample users with their data.

  • Expect new departments in a flat hierarchy and manually delete the old ones.

  • Update any automatic rules that use the remapped field.

  • Reach out to Support for any scheduling and practical handling of the task.

Did this answer your question?