Report: Personalized Learning Data

Here you will find details about each column in the E-Learning report (Personalized Learning)

Column: customerId

Description:
Internal SoSafe customer ID. It associates each user with the correct customer.

Column: Mandant

Description:
Official name of the customer in the SoSafe Manager.

Note:
This field is especially useful in multi-tenant data exports.

Column: Campaign

Description:
Specific learning campaign to which the user is assigned to.

Note:
This field is especially useful in multi-tenant data exports.

Column: User ID

Description:
Internal SoSafe User ID. Used for internal tracking and analytics across learning modules.

Column: Firstname

Description:
User’s given name, pulled from the identity provider or user import file. Information pulled from User Management → Users.

Column: Lastname

Description:
User’s family name, pulled from the identity provider or user import file. Information pulled from User Management → Users.

Column: Email

Description:
User's email address. This is their unique login credential and also the primary channel for email-based training delivery. Information pulled from User Management → Users.

Column: Language

Description:
Language in which the user receives their training content.

Column: Created

Description:
User SoSafe account creation date. This is when the user was first imported or synced, but not necessarily when training began. Information pulled from User Management → Users.

Column: Registered

Description:
User training registration date. This is when the user registered and logged into the E-Learning Platform the first time.

Column: Active

Description:
Indicates whether the user is currently considered an active learning account in the system. Users will be deactivated via identiy provider or manual via User Management → Users.

Column: Progress [Deprecated]

Description:
Numerical value that reflects a user’s progression through their assigned learning path. This column is a deprecated artifact and will be removed in a future update.

Column: Level Achieved [Deprecated]

Description:
Deprecated artifact that will be removed or enhanced in a future update.

Column: User Group

Description:
Organizational group or groups to which the user belongs. The content depends on the customer’s feature configuration:

If Profile-Based Personalization is enabled:

• The column will display all user groups the individual user belongs to.

• Groups are shown in alphabetical order, separated by a delimiter.

• These groups are used to determine role-based content or risk-based personalization.

If Profile-Based Personalization is not enabled:

• The column will show the user's group, as imported from your connected identity provider (e.g. Microsoft Entra, Okta) or your manual user upload.

• Each user will belong to exactly one group.

Column: Passed modules

Description:
Total number of completed training modules (mandatory + optional) out of the total number of modules assigned to the user based on the filter set in the Analytics dashboard at the time of download.

Display format:
X / Y

• X = Number of completed modules

• Y = Total number of assigned modules

This is an aggregated completion count that combines both required and optional modules.

Example:
1 / 63 → The user has completed 1 out of 63 total assigned modules.

Column: All modules passed

Description:
Flag that indicats whether the user has completed all assigned modules. It includes both mandatory and optional ones based on the filter set in the Analytics dashboard at the time of download..

• Yes → The user has completed 100% of their assigned modules.

• No → At least one assigned module (mandatory or optional) is still incomplete.

Note:
This column is helpful for quickly filtering users who have fully completed their training.

Column: Overdue mandatory modules

Description:
Total number of mandatory learning modules that are currently past their due date and still incomplete, relative to the total number of modules that are due.

Display format:
X / Y

• X = Number of due modules that the user has not completed (i.e., overdue)

• Y = Number of mandatory modules that are due

If a user has mandatory modules assigned but none of them have reached their due date yet, this column will show 0 / 0.

Example:
How “Overdue Mandatory Modules” is Calculated:

Let’s walk through a sample scenario to illustrate how this column works.

User: Jordan M.

• User account created: March 11

• User first logged in and completed the initial survey: March 15

• Learning path calculated: March 15

• Module due date: April 12 (28 days after learning path calculation)

Between March 15 and April 11

• Jordan has mandatory modules assigned.

• But none are past their due date yet.

• Overdue Mandatory Modules will display:
  0 / 0 (Modules are not yet due, so none can be overdue)

On or after April 12

The first set of mandatory modules becomes due. At this point:

• If Jordan has completed 3 out of 4 due modules:
  → 1 / 4 will display (1 module is overdue)

• If Jordan has completed all due modules:
  → 0 / 4 will display (0 overdue modules)

• If Jordan has completed none:
  → 4 / 4 will display (all are overdue)

Important Notes:

• Due dates are dynamic and always calculated as 28 days after a learning path is created or recalculated.

• Learning paths are recalculated when:

  • The user completes the initial survey

  • There is no initial survey and the user logs in for the first time

  • A manager updates the Personalized Learning setup (e.g., assigned additional modules), and the user logs in again

  • The system assigns a default path overnight if the user never logs in (to avoid a permanent 0 / 0)

Note:
The numbers in this column may fluctuate over time based on when the learning path was calculated, user activity, and any changes made to the training configuration. This means a user who shows 0 / 0 today could show 2 / 4 tomorrow as due dates pass or their assigned modules change.

Column: Passed mandatory modules

Description:
Total number of mandatory modules the user has completed out of the total number of mandatory modules that have been assigned to them.

Display format:
X / Y

• X = Number of completed mandatory modules

• Y = Total number of mandatory modules assigned

This count accumulates over time as users complete more training. It includes both on-time and overdue completions.

Example:
4 / 6 → The user has completed 4 out of 6 mandatory modules assigned to them.

Column: Passed optional modules

Description:
Total number of optional modules the user has completed out of the total number of optional modules they were offered.

Display format:
X / Y

• X = Number of completed optional modules

• Y = Total number of optional modules assigned

Optional modules are not required to be completed but may be offered to deepen learning or cover additional topics.

Example:
2 / 5 → The user has completed 2 out of 5 optional modules that were available to them.

Column: Recently finished module

Description:
Completion date of the most recently finished training module (mandatory or optional) for each user.

Column: [Learning Module Name]

Description:
Each column in this section represents the title of a specific training module available on the SoSafe platform (e.g., “Importance of Cyber Security”, “Device Theft”, “Detecting Phishing Mails”). These modules cover key cybersecurity and compliance topics.

• A date in a cell indicates that the user completed that module on that specific date.

• A blank cell means the user has not completed that module.

Example:

• User 1 completed “Importance of Cyber Security” on April 10.

• User 2 completed “Device Theft” on March 31.

• The blank cells do not confirm whether the modules were skipped, incomplete, or simply not assigned in their personalized path.

Column: Division

Description:
User’s organizational division, department, or business unit. The value is typically pulled from your identity provider.

Column: Login_identifier

Description:
Login handle or system-level credential used to uniquely authenticate the user.
It may differ from the user’s email address if configured (e.g., in SSO environments where user principle names or employee IDs are used instead).