Welcome to the TalentBox Documentation Hub – your central space to learn how to get the most from TalentBox. This site brings together product overviews, configuration guides, integration details, and best‑practice examples to help you design and manage your talent processes more efficiently.

Whether you are configuring TalentBox for the first time, setting up integrations, or looking for ways to optimise existing workflows, you’ll find step‑by‑step guidance, screenshots, and explanations organised by topic and area of the platform. Use these resources to support onboarding, answer how‑to questions, and build a consistent understanding of how TalentBox works across your team.

The site also includes a powerful global search that scans all available TalentBox documentation. Just start typing a feature name, process, or question, and the search will surface the most relevant pages so you can jump straight to what you need, without clicking through multiple menus. This makes it easy to troubleshoot issues, explore new capabilities, or quickly revisit something you’ve read before.

As TalentBox evolves, this hub will grow with it, so you can always rely on it as the up‑to‑date source of truth for how TalentBox is designed, configured, and used in practice.

QR Code-Based Attendance System is a modern, secure solution designed to automate and streamline classroom attendance management, fully integrated with SAP SuccessFactors Learning. Leveraging SAP Business Technology Platform (BTP), the application delivers real-time attendance capture, seamless data synchronization, and comprehensive reporting, all while ensuring GDPR compliance and robust security. The system is accessible via both mobile and desktop interfaces, providing flexibility and convenience for employees, instructors, and administrators.

Key Benefits:

• Eliminates manual attendance processes

• Ensures accurate, real-time data capture and reporting

• Integrates directly with SAP SuccessFactors Learning for training record maintenance

• Scalable and mobile-friendly for enterprise environments

Based on the class setup configured by instructors, attendees will receive both a check-in and a check-out QR code.

Scanning the QR Code: Attendees can use their mobile device’s camera application to scan the provided QR codes. Scanning the code will direct users to the company’s login page. Upon successful authentication, users will be checked in or checked out accordingly.

Scenarios:

• Successful Check-in/Check-out: When the process is completed successfully, users will receive a confirmation message indicating their check-in or check-out was successful.

The References section of the Admin screen is used to manage the 'For Credit' and 'Not for Credit' completion statuses. These statuses can be configured for each item type and are utilized to accurately record user learning progress.

Please note: The Component Type (item type) and Completion/Non-Completion Status IDs must match with the configurations in SuccessFactors LMS. If non-completion statuses are not configured, the system will not record learning for users who did not attend the class or did not meet the required completion threshold.

Fully integrated with the SAP SuccessFactors ecosystem, it empowers organisations to assess and develop role-specific skills, close skill gaps, ensure compliance, and drive workforce excellence—whether in safety, technical proficiency, or regulatory requirements. ​ ​ Through a structured framework defining the roles of Admins, Observers, and Users, it fosters seamless collaboration, effective communication, and actionable insights across the assessment workflow.

From this screen admins can:

• View existing Autorized Observers

• Create new Authorised Observers

From this screen Admins can

• Create new Rating scales

• View Existing rating scales

• Edit/Delete rating scales

From this screen Admins can

• Upload a logo which will be visible to end users of this application (Observers and Observees)

• Publish Method via OCN or Manually Content Object

• Disable XSS SCan for Observation

This is the Merge Duplicate Users screen, used by administrators to clean up duplicate user accounts.

It presents two main actions:

• Select Users – Opens a flow to search for and select duplicate user records that should be merged.

• Remove Selected Users – After duplicates are identified and marked, this option removes the extra accounts, keeping only the primary record.

Issue: Import fails repeatedly

• Solution: Check the Log File in Import Job Data for errors. Ensure the file format matches TalentBox requirements.

Issue: AI-generated content is inaccurate

• Solution: Refine your company profile and template settings, or use Fixed Text for more control.

Issue: Unable to find an approver

This job imports the item labels for titles and descriptions from SuccessFactors LMS.

Company Logo: This is the logo displayed to both instructors and end users within the application.

Configure Application Icon Image: This image serves as the application's icon in the web browser.

QR Code Timeout (in Seconds): Specifies the duration after which the QR code will automatically refresh. Note: If set to 0, the QR code will remain static and will not expire. In this case, instructors will also have the option to download the QR code as a PDF for printing and classroom display.

Event History (Number of Days): Defines the maximum number of days for which historical class data will be visible to instructors. Please note: the date range will be calculated based on the start date of the last segment of any class. Maximum days allowed: 180

Completion Percentage Threshold: Determines the minimum completion percentage required for user learning to be recorded in SuccessFactors LMS. For example, if set to 80%, users must complete at least 80% of all class segments for their progress to be recorded.

Class Report File Name: Specifies the file name for the class report, which transmits detailed class data from SFLMS to the application.

Class report date time format: specifies the date format in which the incoming class report is sending the data. this is usually date format of the user who is sending this report to SFTP.

example: MMM-dd-yyyy HH:mm:ss

Catalog ID: Indicates the catalog ID where all classes from SuccessFactors LMS are stored. This must match the catalog ID configured in the LMS.

Custom Title (Max 100 Characters): A customizable title for the application, visible to instructors on the app's landing page.

Custom Description (Max 200 Characters): A customizable description for the application, visible to instructors on the app's landing page.

Allow Auto Checkout: If enabled, instructors can activate the auto-checkout feature for their classes.

Allow Manual Mark Attendance: If enabled, instructors can manually check in and check out users.

Record Not for Credit Learning History When this feature is enabled, learning history will also be recorded for users who do not meet the completion threshold. These instances will be documented as "Not for Credit" in SuccessFactors LMS. Please note that "Not for Credit" completion statuses must be listed in the Reference>Completion Statuses section corresponding to the relevant Item ID.

Review and tag learning content to skills data from your organisation’s skill library with Learning Skill Tagger.

Maximise the effectiveness of your learning content by tagging it to skills. Learning Skill Tagger ensures that learning initiatives are precisely aligned with skill development needs, facilitating targeted and impactful training programs.

This is the Merge Duplicate Users background job history.

• The job is marked as Scheduled, with a Re-Schedule button to change when it runs.

• Each row shows a daily execution with:

  • Start Time / End Time – When the job ran.

  • Status – All runs show SUCCESS, meaning the process completed as expected.

  • Comment – Each entry states “INFO: No records to merge”, indicating that on those days the system did not find any duplicate user records that met the merge criteria.

  • File / Log File – Placeholders for output or logs (empty in this screenshot).

The banner at the top notes that the job runs on UTC time, with the current UTC time displayed.

The Skill Library Builder has been designed to help organisations quickly and efficiently build, maintain, and enhance their skill library, map the skill to roles with expected proficiency and provide text descriptors for individual proficiency values.

Within TalentBox, The Skill Library Builder is structured into a series of dedicated tabs, each focusing on a particular aspect of the skill library development process. The below tabs guide you step-by-step through from the import of your role data to be analysed to the addition of the data to SuccessFactors.

TalentBox’s Job Profile Generator is an AI-driven platform designed to streamline the creation and management of job profiles, helping organizations transition to a skills-based approach.

This guide provides step-by-step instructions to set up, generate, edit, and manage job profiles effectively. Whether you're an HR professional or a manager, this guide will help you harness TalentBox’s features to transform your talent management process.

This is the Global Assignments Configuration screen, where you define how global assignment users are identified and updated.

It includes:

• LMS Duplicate Fields – A comma-separated list of LMS fields (here Fname,Lname) used to detect duplicate users across global assignments.

• Custom Column 999 update for Global Assignment Users – A toggle (set to Yes) that controls whether a specific LMS custom column (e.g. column 999) is updated for global assignment users.

• Basic Authentication Username / Password – Credentials (shown here in encoded form) used for basic authentication when connecting to the SuccessFactors LMS as part of the global assignments processing. Currently this uses LMS oAuth Keys.

A Save button is provided to store any changes to these settings.

To generate the role to skill mapping files for Job Profile Builder, import the validated role to skill export from step 1 and select ‘Extract Skills’. The file is now ready to be added to SuccessFactors via the Import/ Export Job Profile Data option.

• Input File Path: Path of the folder where the file will come from LMS and picked up by the Tag Learning Skills job

• Input File Name: Name of the File

• Output File Path: Where the 2 files below will be placed

• Existing skills report: Course–skill links for skills already in our library (course ID, type, revision date, skill ID, rating).

• New skills report: Courses linked to skills that are not yet in our library (course ID, type, revision date, course title, suggested skill name), so your team can review and decide whether to add them

System Name: The title of the application shown to administrators on the landing page.

Welcome Message: A short description of the application shown to administrators on the landing page.

Global Colors (currently only used in AttendanceIQ)

• Primary Color: The main color used across all user-facing applications.

• Secondary Color: The secondary color used across all user-facing applications.

• Text Color: The default font color for all user-facing applications.

Buttons (currently only used in AttendanceIQ)

• Background Color: The default background color for buttons in user-facing applications.

• Hover Color: The background color shown when a user hovers over a button.

• Text Color: The default color of button text.

• Text Hover Color: The color of button text when a user hovers over it.

Font Type (currently only used in AttendanceIQ)

• Standard Font: The list of standard font types available for all user-facing applications.

• Custom Font: Lets you upload a custom font for user-facing applications. The font must be uploaded as a zipped .TTF file.

Application Logo: The logo displayed in the header of the Administration Console.

Landing Page Image: The image shown on the Home tab of the Administration Console.

This is the job to import Coursera Courses

Learning Content Manager, an ingenious solution to simplify content management in SAP SuccessFactors Learning. For organizations using Open Content Network Integrations, manual mapping and administrative tasks are a challenge. Our Learning Content Manager connects seamlessly with content sources, intelligently mapping content to specific libraries, topics, and skills taxonomies. This automation ensures a seamless user experience and eliminates administrative burdens.

The Attendance application integrates with the LMS via APIs; however, it is recommended to schedule certain synchronization jobs on a regular/weekly basis to ensure optimal data consistency between the LMS and the application. This approach is advised for the following reasons:

• Language Support: The APIs currently support only a single language. If multi-language functionality is required, utilizing the synchronization jobs becomes essential.

• Course Descriptions: APIs do not retrieve course descriptions. To include this information, the synchronization jobs must be used.

• Catalog Configuration: The APIs require that all classes and courses be included in a specific catalog, which must then be within the application. This is a necessary pre-requisite for API integration.

• Class Completion Thresholds: The synchronization jobs provide the flexibility to define class completion thresholds on a per-class basis. Without these jobs, the threshold is managed as a global within the application.

• Credit Status Management: The jobs also allow for differentiated "For Credit" and "Not for Credit" statuses for individual classes. In the absence of these jobs, these statuses are governed by global application .

• Secondary Instructors: The Import Class job also enables the inclusion of secondary instructors, allowing them to view and access the classes. Without utilizing this feature, only primary instructors will be able to see the classes and manage attendance.

Scheduling these synchronization jobs ensures greater flexibility and functionality, particularly in environments with diverse requirements.

Types of Jobs

1. and : These jobs sync the course details from LMS to the Application.

2. : This job syncs all details about the class including Start times, end times, Segment details and also VLS settings which admins can configure to bring For Credit completion status, Not for Credit Completion status, completion threshold, Primary and Secondary Instructors for the specific class. This job also brings in the Instructor and User relationships. if your instance has different Instructor IDs and UserIDs, then it is crucial this job runs periodically.

To facilitate this setup, TalenTeam will provide custom reports that can be imported into the LMS. These reports should be scheduled for regular delivery to an SFTP location. The application job will then retrieve these files from the SFTP server and process the data accordingly.

Custom Reports to be imported in LMS

1. Import Classes

From the Manage Tasks screen, administrators can create and manage tasks in two ways:

• Manually – by clicking the New button

• In Bulk – by using the Import button to upload predefined tasks

Creating a New Task Manually

To create a task manually, follow these steps:

Step 1 – Click New Select the New button from the Manage Tasks screen.

Step 2 – Fill in Required Details Provide the necessary details for the task:

• Task Name – Unique name for the task

• Task Description – A clear description of the task

• Task Type – Select one of the following:

Administrators can also bulk create tasks through the import function:

1. Download the template file from Tools > Download Templates.

2. Fill in the required task information within the template.

3. Go back to the Manage Tasks screen, click Import, and upload the completed file.

This option allows faster creation of multiple tasks and ensures consistency across observations.

The Read-Only Admin Role allows administrators to view data and configurations in Observe IQ without making any changes. This role is ideal for stakeholders, auditors, or leadership teams who need visibility but should not modify system settings or records.

Modules of ObserveIQ Supported with Read-Only Access

Read-Only permissions are available for the following modules:

• Manage Observations

• Manage Tasks

• Manage Authorized Observers

• Manage Rating Scales

• Dashboard

Admins can access observations in read-only mode by clicking the Eye icon. All values within the observation are displayed in view-only mode and cannot be edited.

This is the Manage Translations area, focused on language versions of your job profiles.

Translation Management Tabs

The translation management interface is organized into the following tabs to help you track and manage profile translations efficiently:

Not Translated

Displays all active profiles that do not yet have any translations assigned. This tab is useful for identifying profiles where translation work has not yet begun, allowing you to prioritize untranslated content. Profiles can be selected in bulk to generate translations. On this page, user can see Job profile name, job family and sub family.

In Progress

Shows all profiles currently undergoing translation, pending approval, or marked as translation failed. Use this tab to monitor active translation work and identify profiles requiring reviewer action before they can be approved and published. For the profiles that has been re translated, and the main profile has been sent for approval again, the translated version stays in "on hold" state. once the main profile is approved, the profile is assigned to the translations approver if it is scheduled, if not then it goes to ready to publish.

Displays all approved language-specific (translated) profiles that are ready to go live. Administrators can use this tab to publish approved translations and make them active for end users.

Shows all language-specific profile translations that have already been published and are currently live in the system.

Important Note: The Published tab is read-only. Any new translations or repeat translation requests must be initiated from the main translation workflow, not from this view.

This page shows the submission request details. The skill expert can view evidential submissions made by users—for example, Sara Torres requesting assessment for "Artificial Intelligence." Actions available include downloading the evidence, approving, or rejecting the request. On this page, clicking the "History" button shows past submission requests. Skill experts can review previously approved or rejected submissions, helping them track decision history and maintain consistency in evaluations.

Elevate Workforce Capability Through Verified Skill Assessments Move beyond subjective self-assessments with our rigorous, AI-driven validation process. The Skills Assessments platform empowers organisations to accurately validate the skills listed in employees’ SAP SuccessFactors “Growth Portfolio.” While employees can initially rate their skills on a scale of 1 to 5, our system enhances this by incorporating AI-driven assessments, evidence submissions, and expert reviews. This thorough validation provides a clear and accurate view of employee capabilities, enabling informed decisions on talent management and development, and positioning your workforce for sustained success.

Expert-Led Endorsements and Evidence Submission:

Leverage your organisation’s internal expertise to ensure unbiased validation of advanced skills through a robust endorsement process. Employees can request endorsements from colleagues or managers, and advanced skills may require evidence submissions, such as work samples or manager reviews. Selected experts within your organisation review these submissions, ensuring a thorough and unbiased validation process. This expert review guarantees that skills are validated based on solid evidence, resulting in a capable and confident workforce, underpinned by a reliable foundation for talent development initiatives.

This is the Translation Approvals worklist, showing translated job profiles that need review before publication.

• The Pending tab is active, listing profiles by Profile Name, Job Family, sub family and Language (German, French, Italian, etc.).

• For each row, the approver clicks the chevron arrow on the right to open the translated profile, review and edit the content, then saves and uses the Mark as approved action inside the profile to complete the approval.

If there is a requirement to define specific settings for individual classes, the VLS settings at the class level in SuccessFactors LMS (SFLMS) must be enabled and appropriately configured. The following parameters can be specified using these settings:

• For Credit Completion Status

• Not For Credit Completion Status

• Minimum Percentage Attendance

When these fields are populated for a class and the Import Class background job is active, the specified settings will be applied to that particular class.

Addressing the complexities of global assignments and concurrent employments, our application streamlines learning management, providing seamless journeys for employees. Challenges such as distinct user profiles, varied training requirements, and fragmented learning histories are tackled head-on. By automating processes, consolidating profiles, and providing holistic data insights, you can focus on talent development.

This is the Content Categories Configuration screen in the content manager.

• Each row defines a catalog Category ID (for example, ANTI_BRIB_CORRUPT, BUS_SKILLS) and its human‑readable Category Description such as Anti Bribery & Corruption or Business Skills.

• The Actions column gives you edit and delete controls to maintain the category list, while the Add button at the top-right lets you create new categories.

• At the bottom, the More link and the [10 / 69] indicator show that you are viewing 10 out of a total of 69 available categories, with paging controls to navigate through the rest.

The References section of the Admin screen is used to manage the 'For Credit' and 'Not for Credit' completion statuses. These statuses can be configured for each item type and are utilized to accurately record user learning progress.

Please note: The Component Type (item type) and Completion/Non-Completion Status IDs must match with the configurations in SuccessFactors LMS. If non-completion statuses are not configured, the system will not record learning for users who did not attend the class or did not meet the required completion threshold.

This is the Content Sources Configuration screen in your content manager.

• Each row represents a learning content source (TALENTHUB, INT, OPENHPI, COURSERA, GO1, LYNDA, EDX).

• For each source you can see the configured Libraries and Categories, and flags for Enable Category Mapping and Enable Processing; in this view only EDX has both mapping and processing enabled (set to Yes), so it is the only source currently being actively processed into the catalog.

• The Actions column provides edit and delete icons so you can adjust configuration or remove a source, and the Add button at the top-right lets you register a new content source.

This screen is a Skills management list where an administrator can browse and manage all skills in the system.

Each row represents a single skill, with columns for:

• External Id – The external or source identifier for the skill (e.g. from a content provider or external skills catalog).

• Name – The skill name, often including exam or certification titles.

• Description – A short description of the skill, with a “Show More” link to expand and read the full text.

• Type – The kind of record (here shown as SKILL for each row).

• Status – The current status (e.g. A for Active).

On the left, there are checkboxes to select one or more skills for bulk actions, and at the top right there is a Search box and a download icon, likely to filter or export the skill list.

This is the Content Manager Configuration screen, where you define file locations and names for content processing and reference data.

Processing files configuration

• Input File Path / Name – Where the raw input file (here Test.csv under /content_manager1.0) is picked up.

• Output File Path / Name – Where the processed item data file (e.g. item_data.txt under /content_manager) is written.

• Cloned Locales Output File Name – Name of the locale-specific output file (here item_locale_data.txt).

• Processed Files Path – Folder where processed input files are moved after successful processing (e.g. /content_manager/ProcessedFiles).

Reference data configuration

• Reference Files Path – Base folder for reference CSVs (here /content_manager).

• Active Locale File Name – File listing allowed locales (e.g. Active_Locales_CSV.csv).

• Catalogs Input FileName – Reference file to load catalog definitions (Catalog_Reference_Data.csv

The Save button persists these paths and filenames so scheduled jobs (like Import Reference Data and Process Item Data) know where to read and write their files.

On this screen you can download templates of some of the data import jobs. Currently one template is available which relates to ObserveIQ Application.

The screen shows the System Audit Reports section where an administrator can choose which audit report to run.

There is a “Report Name” dropdown listing several available audit report types:

• Configuration

• Role

• User Role Access

• Background Job Scheduling

• Notification Templates

By selecting one of these options, the admin would typically generate or view an audit report focused on that specific area of the system (for example, who changed roles, how background jobs are scheduled, or how notification templates are configured).

This is the Notifications Settings screen, where you control how system notification emails are sent and formatted.

• From Email Address for Notifications – The sender address that appears on outgoing emails (example: donotreply@blendlxp.com).

• To Email Address for Notifications – A target address for system‑level notifications or test messages.

• Email Every X Days – Frequency control for batching or digest emails; set to 0, which typically means send immediately or on every event.

• Email Threshold in Minutes (1000 email) – Rate‑limiting parameter; here 1 minute per 1000 emails to avoid overloading mail infrastructure.

• Logo – Upload to brand notification templates with your organisation’s logo.

• Under Notification Templates, you map categories such as Observations to a specific template. Clicking Save applies these settings to future notifications.

This job imports the item metadata from Successfactors LMS.

To schedule the background job click on Reschedule and upload the file

Once file is uploaded admin can schedule the job

Additionally Job can be Schedule Daily/Houry/weekly/Monthly

This is the Content Catalogs Configuration screen in the content manager.

• Each row defines a Catalog ID (for example SHOPIFY, EU_CAT, GLOBAL, MAND, PLURALSIGHT) and a descriptive Catalog Description such as Global Catalogue for all Users or All Mandatory Training.

• The Actions column provides edit and delete options for each catalog, while the Add button at the top-right lets you create new catalogs as your content strategy evolves.

This is the Process Item Data scheduled job, which handles exporting or syncing item data (likely learning items) from your content manager.

• The job is Scheduled, with an option to Re‑Schedule, and runs using UTC time.

• The last run on 11/May/2026 07:42 finished with Status = SUCCESS.

• The Comment log shows the detailed processing steps: clearing the outgoing item data table, processing records for different channels (including EDX and locales), moving processed files to /content_manager/ProcessedFiles/null, and writing out item and locale data files—though in this run all the counts are 0, meaning there were no new or changed records to process.

License Management

This section provides displays the Licence for your subscription.

Access Control: This screen is restricted exclusively to System Administrators. No other user roles should have access to this section to maintain security and control over licensing information.

Step 1: BTP Specific Configurations: TalenTeam will setup your BTP account and share the details.

• Please use the Token Shared by TalenTeam under SuccessFactors --> Extension Center

Step 2: SuccessFactors Configurations - The application requires the below details to connect to SuccessFactors.

• Company ID

1- Publish By OCN

2- Manually Publish by copy URL

Admin can publish observation in SFLMS by one click with the help of Publish to OCN button and to use this feature admin have to make sure Publish to OCN is checked in ObserveIQ >>configuration

Step 1: Create a new OCN Provider in SuccessFactors LMS. Refer to this:

Step 2: Add Provider name on >> System Configuration >> Application settings >> OCN providers and save the configuration.

In order to personalise the Skill Library Builder results, information about your organisation is added including Company Name, Overview and Industry.

When running the Skill Library Builder the following options can be selected:

This screen is a Locales management page for administrators.

It shows a table listing all available locales with four main columns:

• Locale ID – The technical code for the locale (for example, en, en-GB, cs-CZ).

The Integrations section manages all external integration configurations. SuccessFactors and SFTP-related settings are centrally maintained and accessible across all applications.

Navigation: System Configuration > Integrations

TalenTeam will enable the integrations during initial setup. Clients are responsible for providing configuration details for the following integrations:

• SuccessFactors

This job does 2 things:

1. Imports class data from SuccessFactors LMS via a custom report This process retrieves key information such as course start and end dates, VLS settings (utilized by the Attendance Application to specify completion statuses—For Credit and Not for Credit—as well as the completion threshold), primary and secondary instructors, and the relationships between instructors and users.

   • To enable this functionality, a custom report must be configured within the LMS and scheduled for periodic export of class data to the designated SFTP location. Scheduling regular exports is highly recommended, particularly when are critical and when instructor IDs differ from user IDs.

The Application Settings section includes the following key configurations:

This is the base URL of the SAP Business Technology Platform (BTP) application. Refer to the screenshot below for an example format.

If AI capabilities are enabled, Azure OpenAI is selected by default as the AI service provider.

This setting is specific to the Observations and Skills Assessment application. Enter the OCN Provider ID that has been created in SAP SuccessFactors LMS (SFLMS).

This value ensures the application is correctly linked to the appropriate OCN provider, enabling accurate data integration and reporting within the organization's learning ecosystem.

Select the preferred storage location for evidence file uploads. Available options include:

In this section you can configure notifications specific to the "" Application.

The Observer Analytics Dashboard provides observer with a comprehensive view of user and task analytics in a visually appealing and easily navigable interface. The dashboard is accessible via Analytics Tab.

This Screen will help Observers to get the detailed analytics data of the observer where observer can view the details of their personal observation and their assigned observee.

Tab 1 – Observation Reports

Section A: Observation Summary Tiles

Display four visually distinct summary tiles:

• Total Observations: Show total number of observations in the system.

• Completed Observations: Display count of completed observations.

• Active Users: Display number of users which are in progress of the observation and users who have requested the observation.

• Average Duration: Show average time taken to complete observations (in Mins)

• Provide a trend graph with three colors (green, blue, orange) to represent distinct status categories.

• This status report will show the data of the all observations that has been taken by the observer.

Observation Trends: which will show the following details by Month

• Green – In progress Observation

• Blue- Passed observation

• Orange- Failed Observation

• Show a line graph presenting distribution of Passed and failed status on Monthly basis

This Table will show the data of the In progress, passed and failed observations with the assigned users details with Progress of each task and completion dates.

Navigated from the main dashboard’s Task Report tile.

• Total Number of Tasks: The total published tasks.

• Passing Rate: Percentage of tasks that were passed.

• Failure Rate: Percentage of tasks that were failed.

• Average Duration: Average completion time for tasks.

• Display a line or bar graph showing the number of completed passed and failed tasks per week.

Columns included in table:

• Task Name

• User

• Task Type (Rating, Numeric, Pass/Fail)

• Evaluation Score

The "Reset Observation" feature allows an administrator to remove an observer from active observations. This ensures that when an observer leaves the company or changes roles, the ownership of their pending observations can be cleared, allowing for new observers to be selected for continuity.

Access & Permissions

• Menu Location: A new "Rerouting" option will be available in the ObserveIQ main menu.

• Role Access: Access to this feature is controlled via Role-Based Access via system Configuration.

• Interface: Click on New Button and Action popup will appear with the information and Admins proceed by clicking "Next button" to initiate the reset

Admin needs to select the reason to reset the observation by clicking on dropdown and click on NEXT button to Proceed

• Selection: The admin must search for and select the specific observer whose observations need to be reset.

• Search: Users can search by Name, Or user ID.

The system displays a scrollable list of "In Progress" or "Pending" observations associated with the selected observer and admin have to select at least one observation to proceed.

The admin determines how existing data should be handled for the selected observations:

• Delete all ratings from previous observations : Permanently removes all existing ratings and feedback; the new observer must start the evaluation from the beginning of task.

• Preserve Previous ratings as read-only: Existing ratings are kept for reference but cannot be modified by the new observer and new observer will see the previous ratings with the previous observer's name attached.

Confirmation Screen will popup with the waring message which will show the details summary of the source observer, reason and settings.

Even after clicking on complete reset Confirmation popup will popup with the information message.

Upon completion, a success message appears with an option to "Start New Resetting"

"Create Group" option, in case the group has not been created already.

• Back Button: Navigates to the main skill group overview.

• Search Bar: Allows filtering of listed experts.

• Edit Group: Likely enables adding/removing experts or modifying the skill group.

A structured table listing the details of ongoing assessments.

• Pass: Proceed with either an endorsement request or evidence submission.

• Fail: Follow reattempt rules, including any cooling-off period and the maximum number of attempts.

Next Steps

Request for an endorsement from co worker After you submit a request for an endorsement, you can view the details on the page. The request remains in a pending state until the endorser approves it. Once approved, the pending state changes to approved.

Submit your evidence here. Once submitted, it will be reviewed by a skill expert. Upon approval, it will be marked as approved.

To advance to the next level, pass the quiz, obtain the necessary endorsements, and get your evidence submission approved. Once done, you can see your assessment in "Completed" tab.

Access your skills and their proficiency levels on my skills page, and initiate assessments

• Login URL: The instructor login URL will be like this: . the first part of the URL is instance/customer specific.

• Authentication: Once the Instructor clicks on the URL it will redirect them to the company specific login mechanism. for example: if IAS is enabled, it'll take them to that screen

• Landing Page:

Users can perform the following actions within the observation process:

• Launch an observation

• Request an observation

• Track their progress

The admin-side Analytics Dashboard provides administrators with a comprehensive view of user and task analytics in a visually appealing and easily navigable interface. The dashboard is accessible via a dedicated tab in the admin panel called Dashboard

There are 2 tabs on this page: Observation Repot & Task Reports. The top section displays two large clickable Tabs.

• Observation Report (Default Landing Page)

The Manage System Labels feature allows Administrators to update system labels in different languages for ObserveIQ Application (both the Observer side and the Observeee side of the application)

Administrators can download system labels for all user-facing applications from this screen. The downloaded file contains the Label ID and Label Value for each label.

The file can then be updated to modify labels and imported back into the system using the Import System Labels background job.

Identify the system label text from either the Observer side or the Observe side and copy the required label text.

The Purpose of this job is to Import all Skills from SuccessFactors to TalentBox. This job can be run daily.

This is the Import Reference Data scheduled job status screen. the purpose of the job is to import referene date from SF LMS.

• The job Import Reference Data is marked as Scheduled, with a Re-Schedule button to change its run time.

• The row shows a run on 12/May/2026 05:51 with Status = SUCCESS.

The purpose of this job is to import Job Profiles and related data from SuccessFactors.

It imports the following data:

• Job Profile roles

• Job Profile–role–skill mappings

What the process does

The process takes a list of learning courses, keeps only those in English, adds or updates them in the system, uses their title and description (and subject descriptions) to automatically identify relevant skills via an external skills service, then produces two reports: one for skills already in our library, and one for newly suggested skills.

The process in three steps

flowchart LR
  A[1. Load course list] --> B[2. Sync courses into system]
  B --> C[3. Find skills and create reports]

Step 1 — Load course list The process reads the course list from the agreed file location (the same place your team uploads the CSV). It only keeps rows where the language is English. All other languages are ignored. The data is then ready for the next step.

Step 2 — Sync courses into the system Courses from the file are compared with courses already in the system (using course ID, type, and revision date). New courses are added; existing ones that need to be reprocessed are updated. After this step, the system has a clear list of which courses need skill extraction.

Step 3 — Find skills and create reports For each course that needs processing, the process:

• Sends the course title, course description, and subject descriptions to an external skills service (Lightcast), which suggests skills that match the content.

• For each suggested skill, the system checks whether it already exists in our skills library.

  • If it exists: the link between the course and that skill is saved (with a default rating).

  • If it does not exist: the course and suggested skill name are recorded for the “new skills” report.

• When all courses are done, two output files are written to the same type of secure location used for the input:

  • Existing skills report: Course–skill links for skills already in our library (course ID, type, revision date, skill ID, rating).

  • New skills report: Courses linked to skills that are not yet in our library (course ID, type, revision date, course title, suggested skill name), so your team can review and decide whether to add them.

Your file has many columns. Below they are grouped by how the process uses them.

Used to identify the course (and to sync / report)

• Course ID (CPNT_ID) — e.g. GO1_27124, LYNDA_18830.

• Course type (CPNT_TYP_ID) — e.g. ONLINE.

• Revision date (REV_DTE).

Together these uniquely identify a course when syncing and in the output reports.

Used to decide which rows are processed

• Language (CPNT_LOCALE) — Only rows with English are loaded. All other languages are skipped.

Used to find skills (most important for the “skill matching” step)

• Course title (CPNT_TITLE).

• Course description (CPNT_DESC).

• Subject 1 / 2 / 3 descriptions (CPNT_SUBJ_1_DESC, CPNT_SUBJ_2_DESC, CPNT_SUBJ_3_DESC).

These five fields are combined into one text and sent to the external skills service. Better, clearer titles and descriptions lead to better skill suggestions.

Stored and used when syncing courses

• Title, description, subject codes and descriptions, language, and “not active” flag (NOTACTIVE) are stored and used when adding or updating courses in the system.

Stored for reference but not used for skill finding or for the main course sync

• Classification, delivery method, source (e.g. GO1, LYNDA), creation/update dates, length, credit hours, secondary course ID, and system GUID are kept for reference but do not drive skill extraction or the main sync logic.

Course Import from LMS

Please used the attached file to export course data from LMS.

1. File location The process does not use a file you select at run time. It always reads from the configured file SFTP location. To run the process with a new list, the file must be placed there with the agreed file name.

2. Only English courses Rows with any language other than English are ignored. No error is raised; they are simply not processed.

3. Quality of skill suggestions The suggestions from the external service depend on the text we send: course title, description, and subject descriptions. Complete and accurate descriptions improve the relevance of suggested skills.

Table Columns Explained:

This screen provides the final detailed review of the employee’s assessment submission, including endorsement and evidence evaluation.

1. Quiz Details

• This section includes quiz questions, answers, and scoring details (currently collapsed).

2. Endorsement Details

• Endorsements Required: 1

• Endorsee Name: Sara David

• Status: ENDORSE

This confirms that the endorsement requirement has been met.

3. Evidence Submission

• Skill Expert Name: Sara David

• Status: APPROVED

• Notes: (none provided)

Revision can be created from the Manage observation Screen by Clicking on create a new Revision Button.

Steps to Create Revision

Step 1: Navigate to Manage Observation and click on Create Revision Button from the Action menu of the selected observation.

Step 2: Provide the Revision Number

Step 3: once click on save then copy of the selected observation will be created In Draft Status.

This is a Company Profile Setup screen used to capture high-level information about an organisation and its context.

Key sections on the form:

• Persona

  • A text field for the primary persona (e.g. “Senior Human Resources Specialist”).

• Company Information

  • Company Name, Company Size, and a free-text Company Overview.

  • On the right, Industry and Sector and Core Values fields describe what the company does and how it operates.

• Location and Market

  • Headquarters Location and Operational Regions describe where the company is based and where it operates.

  • Target Market defines the main customer or stakeholder groups.

• Products/Services

  • Main Products/Services describes what the organisation delivers (e.g. decommissioning, nuclear waste management, research, etc.).

• Strategy and Vision

  • Mission and Vision captures the long-term purpose and direction of the company.

• Language Tone

  • Language Tone describes the preferred writing style and tone (e.g. English UK, professional, mission-driven, inclusive).

At the bottom, there are Save and Reset buttons, so the user can store or clear the entered profile data.

The ‘Import Role Data’ screen is where the role data to be analysed is imported, processed and where the results and output files are visible.

• Step 1: Browse and Select your Role Data file. You can download a template with a sample row of data populated here.

This view provides a tabular list of all skills assessments that have been created within the system, along with useful administrative controls.

1. Skill Name: The name of the skill for which an assessment exists (e.g., Apache JMeter, Agile, AWS).

2. Completed Assessment: Shows how many users have completed the assessment for that skill.

Steps:

1. Navigate to from the left menu.

2. Upload your job data file on the SFTP.

3. Schedule and Run the Job.

This screen shows the Merge Global Assignments Learning Histories background job and its recent executions.

• The job is marked as Scheduled, with a Re-Schedule button to adjust when it runs.

• Each row in the table represents a daily run, with:

The Purpose of this job is to Import all User Attributes for example: Skills from SuccessFactors to TalentBox.

The Manage Observation feature allows administrators to create fully customizable observations consisting of a defined number of tasks. These tasks can then be monitored and assigned to an Authorized Observer, Manager, or an Admin-selected Observer.

While creating an observation, administrators can set specific evaluation criteria, edit existing tasks directly from the dashboard, and publish the finalized observation to the LMS with a single click.

Admin Dashboard

From the dashboard, administrators can view and manage all existing observations. The following information and actions are available:

• Observation ID – Unique identifier for each observation

• Revision Number - Unique Revision Number

• Observation Title – Unique title for the observation

• No. of Tasks – Number of tasks included within the observation

• Status – Displays the observation’s status: Draft, Ready to Publish, Published or Deactivated observations

• Action Buttons:

  • Pencil Icon – Edit the observation

  • Publish to OCN – Publish content to the LMS

• New Button – Create a new observation

• Search Bar – Search through the list of observations

Administrators can create observations in two ways:

1. Manual – Full admin control over setup and configuration

2. Assisted – AI-assisted creation using AI, with admin adjustments.

Step 1 – Provide Observation Details

• Observation ID ( non-editable once created)

• Observation Type (configurable labels from Manage System Labels)

• Revision Number (Unique revision Number)

• Observation Title

Step 2 – Add Tasks

• Select tasks from a dropdown or create new ones

• Rearrange task order using arrow controls

• Task table includes:

Step 3 – Set Criteria

• Capture Duration – Track time at observation level, task level, or both

• Allow Upload of Evidence – Collect proof at observation level, task level, or both

• Minimum Tasks Requirement – Define minimum tasks to complete (rules applied against mandatory and total tasks).Admins can define the minimum number of tasks a user must complete during the evaluation process. This setting is governed by the following rules:

  • The minimum number of tasks must be greater than the number of mandatory tasks.

  • It cannot exceed the total number of available tasks.

Observer Type – Select one of the following:

• Admin-selected Observer (with rules based on single vs multiple observers). n Next screen admin can selects any user from the organization and make them observer for that observation.

  • Rules & Conditions:

    If the observer type is set to Admin-Selected Observer and Multiple Observer is disabled, and if admin assigns more than one observer; so, in this case, the user will have the right to select which observer will conduct the evaluation.

• Manager (automatically assigned as the user’s manager from LMS data). if Admin selects manager then in next screen admin will not allow to select any one from the list and admin can complete the creation of observation Process and once observation is assigns to the user in Success Factors then their manager will directly become the observer for the observation.

• Authorized Observer- when Admin Selects Authorized observer then in next screen admin can selects any one from the List of Authorized observer which can be manage by Manage Authorized Observer Screen.

  • Rules & Conditions: If the observer type is set to Authorized Observer and Multiple Observer is disabled, and if admin assigns more than one observer; so, in this case Authorized Observer (selected from managed list in Authorized Observer screen)

Step 4 – Add Observers

• Search and add observers by username or User ID

• Selected observers are automatically updated in the table

• If Manager type is chosen, this step is not editable(skipped)

Step 5 – Publish Observation

• Once criteria and observers are assigned, click Publish to finalize

This feature utilizes Open AI to enable Assisted Observation, allowing users to create observations with AI-generated support. With this functionality, administrators can efficiently generate observation descriptions and tasks using Open Ai's capabilities.

Step 1 – Select Assisted Mode

• Click “Add New Observation”

• Choose Assisted Observation and proceed

• In the Create Observation screen click on "Auto Fill Description" to generate Observation description using AI.

Step 2 – Generate Tasks with AI

• Define the number of tasks to generate

• AI generates:

  • Task Name

  • Task Description

Step 3 – Set Criteria

• Configure as in Manual Observation (duration, evidence, minimum tasks, observers)

Step 4 – Add Observers

• Add observers by username or User ID

• Updates automatically reflected in the table

Step 5 – Publish Observation

• Finalize and publish to LMS with a single click

This is the main Job Profiles Dashboard giving you a health summary of your job profiles and quick navigation into key actions.

• Roles without Profile Number of roles in your framework that do not yet have a job profile created.

• Profiles with Low Score Profiles whose quality or completeness score falls below your configured threshold, indicating they likely need review or enrichment.

This job sends notifications to users based on the settings defined in the

This screen shows the Notifications background job history and schedule.

• At the top, the Scheduled label indicates this job is configured to run automatically, with a Re-Schedule button to change its timing.

• Each row in the table represents one job run, with:

This is the Add a Notification Template dialog, where you define email notification content for the ObservationsIQ Application (Currently)

• You provide a Template Name and choose a Notification Category (here set to Observations) to indicate when this notification is used.

• Template Language lets you localise the template (e.g. Portuguese Brazil), so different languages can have their own versions.

On this screen, you can manage roles and the permissions associated with each role. Your license determines the level of access granted to the application and its features.

Step 1: Configure Permission Roles and Groups in SuccessFactors Role-Based Permissions (RBP) Begin by configuring your permission roles and groups within the SuccessFactors RBP module. For example, the predefined role for System Administrators is TALENTBOX_ADMIN. Ensure that a corresponding permission group and role are created in SuccessFactors RBP using these same IDs.

Step 2: Create Application Roles on the Manage Roles Screen of TalentBox Once the role is established in SuccessFactors RBP, navigate to the Manage Roles screen. Here, you can create an application role and link it to the appropriate SuccessFactors role ID by clicking the Add button.

Provide the required Role ID and Description, then select the relevant SuccessFactors role ID from the dropdown menu.

Step 3: Repeat for Additional Roles

This is the Manage Completion Status screen, where administrators map old completion statuses to new ones. On this screen Admins can define the new completion statuses which will be awarded to the user once their learning history is merged to their Active/Secondary profile after the "Manage Global Accounts Learning History" job is completed.

Key elements:

• A Search bar at the top to filter specific statuses.

• A Choose CSV File / Upload area, allowing bulk upload of mappings from a CSV file.

This screen is the Import Filenames configuration section.

It lets an administrator define the expected CSV file names that the system will look for when running various import jobs. There are four text fields:

• Merge User File Name – Filename used for user merge data (e.g. MergeUsersFile.csv).

• External Learning History File Name

Provides access to oversee submissions and track review statuses.

Access the section to assign or manage skill experts.

• Create New Assessment: Initiate a new skill assessment.

• Pending Endorsements (0): Submissions awaiting endorsement (currently none).

This is the Profile Approvals screen showing job profiles that are waiting for approval before they become active.

• The tab is on Pending (there is also an Approved tab for already-approved profiles).

• Each row lists the Name of Approver, Job Profile Name, and Job Family; here, all three pending profiles are assigned to the approver Sara David.

Admins can run reports for each of the classes from this section.

The report contains details of Class, Users, Check-in time, Check-out times, and if the learning was recorded.

This is the Import Skills scheduled job, and it looks to be running correctly and consistently importing the LightCast skills set.

What the screen shows:

• The job Import Skills is marked as Scheduled, with a Re-Schedule option to adjust its timing.

• For each day (07–11 May 2026), the job ran around 14:35–14:36 and finished with Status = SUCCESS.

Once the skills have added to Talent Intelligence Hub, the data is called via API to bring the WSM ID into TalentBox. The set can be scheduled or run as necessary in readiness for the last step in the process.