Skip to content

SucceedLEARN + HiBob

HiBob integration.
Learning,
connected.

Bring employee data and learning administration together. Sync people from HiBob, assign relevant courses and return certificates and task updates through the features you choose.

For HR administrators, L&D managers and system owners.

YOUR HR DATA. YOUR LEARNING PLATFORM.

01 / CONNECT
HiBob SucceedLEARN
HiBob connected status screenshot
HiBob connection status in SucceedLEARN.
  • OAuth or service-user connection
  • Daily schedules or webhooks
  • Choose the employees you sync

A connected learning workflow

From people data
to learning progress.

The integration connects HiBob employee information with SucceedLEARN administration. Configure the features your organisation needs, from importing learner profiles to making completion records available in Bob.

Keep learner profiles aligned

Map employee names, departments, managers and selected custom attributes to LMS profiles.

Assign relevant training

Use profile-based rules to enrol employees in the right courses, with due dates and mandatory settings.

Share completion certificates

Upload issued certificates to the employee's Bob documents, with upload results for administrators.

Close mapped training tasks

Connect course completions to open, assigned Bob tasks using exact task names and All or Any criteria.

Made for your administration team

The right people.
The right setup.

Bring HR, learning and technical owners together to agree access, mapping and the features you want to use.

Check the prerequisites
01

HR administrators

Agree which employees the connection can access and arrange the appropriate Bob permissions.

02

L&D and LMS administrators

Set profile mappings, course rules, activation emails and the completion features your organisation needs.

03

IT and system owners

Prepare connection credentials, API access, public URLs and webhook or OAuth configuration where required.

The complete administrator guide

Connect. Configure.
Keep it running.

All 16 sections of the supplied guide, organised for practical use. Most settings are optional unless your integration plan requires them. Start with your connection, then choose the features you need.

Showing all 16 guide sections. Open any technical detail for more information.

Browse all 16 guide sections
01

PREPARE

Prerequisites

Confirm the access, connection method and features your organisation needs before you begin. This guide is for HR administrators, L&D managers and system owners.

Start with your use case. Most settings are optional unless your integration plan requires them. Begin with Connect to HiBob, then complete the other sections that apply.
RequirementOwnerWhy it matters
Bob Admin accessHR / ITUse a Bob Admin account, or ask a Bob Admin to create the service user. Admin access is needed for System settings, Service users and Permission groups.
LMS administration accessLMS adminAn LMS site admin, or a role with the HiBob manage capability, creates the integration and saves connections, mappings and schedules.
Outbound HTTPS to api.hibob.comIT / networkThe LMS server must reach Bob's API. A blocked connection prevents employee sync and learning calls.
A decision on the features to enableHR / L&DFor employee sync, choose a daily schedule or webhooks for the company. Enrolment rules, activation emails, Learning provider, Goals, Docs certificates and Tasks are optional.
HiBob Developer Portal accessPartner / ITRequired for Marketplace partner apps using OAuth; not needed for a service-user setup.
A public LMS HTTPS URLITRequired so Bob can reach the LMS webhook endpoint and OAuth redirect when those features are used.
Keep credentials secure. Treat the service-user token and OAuth client secret like passwords. Bob shows a token only once when it is created or regenerated. Store it in a password manager; do not put it in Git or shared tickets.

Source: supplied HiBob Administrator Guide, pp. 1 - 2.

02

PREPARE

Create a service user in HiBob

Use these steps if you will connect with a service-user ID and token. A service user exists for API access: it is not an employee login and cannot sign in to Bob. OAuth connections follow section 5 instead.

  1. Sign in as a Bob Admin

    Open app.hibob.com. If you cannot see System settings, ask a Bob Admin to complete these steps and share the ID and token securely.

  2. Open System settings

    Open the Bob menu at the top left, then select System settings.

    Bob System settings menu screenshot
    Open System settings from the Bob menu.
  3. Open Service users

    Go to Integrations → Service users → Manage. In the supplied sidebar screenshot, the group is labelled Integration tools.

    Bob Integrations Service users screenshot
    Integrations → Service users in Bob.
  4. Create the service user

    Select + Create service user, enter a clear display name such as Succeed LMS integration, and save.

    Create service user form screenshot
    Give the service user a clear display name.
  5. Copy the ID and token immediately

    Bob displays an ID, for example SERVICE-39971, and a secret token. Copy both into your password manager before closing the window. Redact credentials before sharing screenshots.

    Service-user ID and token screenshot
    Copy the credentials once; redact values before publishing.
  6. Create a dedicated permission group

    Go to System settings → Account → Permission groups → + Create permission group. The page is at app.hibob.com/app-settings/permission-groups.

    Name the group, for example LMS Service Users Group. Set User type to Service user, add the new service user as a member, and save.

    Create permission group screenshot
    Create a service-user permission group and add the service user as a member.
A new group starts with no permissions. Continue to Required permissions. For this one-service-user setup, the list should show a Custom group, User type: Service user, and Members: 1.
Bob permission groups list screenshot
Confirm the Custom service-user group and member count.

Related official reference: API Service users.

Source: supplied HiBob Administrator Guide, pp. 2 - 6.

03

PREPARE

Required permissions

Edit the service user's permission group. Bob organises the settings into Features, People's data and Access rights. Grant the permissions needed for the features you use.

Choose whose data the integration can access

  1. Open People's data → Access data for.

  2. Choose Everyone for a typical organisation-wide setup, or limit access by condition or by name.

  3. If you need to sync or suspend leavers and inactive employees, select by condition and remove Lifecycle status equals Employed so terminated people are included.

Bob access rights audience screenshot
Choose the employee audience and check the lifecycle filter.

Minimum data permissions for employee sync

Grant View on the default categories: Basic info/root, About, Employment and Work. Without them, People Search can return empty data.

Bob People's data permissions screenshot
Grant View on the required People data categories.
Bob permissionWhen it is needed
People → Basic info (root) - ViewAlways for employee sync
People → About - ViewAlways for employee sync
People → Work - ViewAlways for employee sync
People → Employment - ViewAlways for employee sync
People → Lifecycle - ViewWhen syncing or suspending leavers
Extra categories for mapped custom fieldsWhen those categories are used in Field mapping

Permissions for each LMS capability

LMS featureBob permission area
Employee syncThe People's data View permissions above, plus Access rights for the audience to sync
Certificate syncPeople → Docs → Shared - Upload / View
Task mappingTasks and flow → People's tasks - View / Complete
Reports / Job catalog / Time offOnly if these advanced modules are used

The employee counts and names in the screenshots are examples from the supplied guide.

Source: supplied HiBob Administrator Guide, pp. 7 - 8.

04

CONNECT

API configuration and authentication

The API base URL is a site-wide setting on HiBob app, at /local/hibob/app_credentials.php. Keep https://api.hibob.com/v1 unless your IT team supplies a different host. The URL is copied to each company connection when that connection is saved.

Connect with a service user

On Connect to HiBob, switch Service user on and enter the service-user ID and token. The LMS uses Basic authentication for API calls.

API authentication and endpoint reference

Each service-user API request includes this header, using the actual ID and token:

Authorization: Basic Base64(SERVICE-USER-ID:TOKEN)
PurposeRequest
Connection testGET /v1/company/people/fields
Employee syncPOST /v1/people/search

These are API paths for the configured HiBob host; they are not pages to open in the LMS.

Lost the token? Regenerate it in Bob → Service users. With the Service user switch on, paste the new token into Connect to HiBob, save and retest the connection.

Related official reference: Authorization.

Source: supplied HiBob Administrator Guide, p. 8.

05

CONNECT

OAuth 2.0

OAuth is the default connection method. Keep the Service user switch off. Configure the OAuth app once on HiBob app; each company connection uses that app configuration.

  1. Prepare the app in the Developer Portal

    Create or open the app in the HiBob Developer Portal. Set its scopes and installation mode.

    HiBob Developer Portal app screenshot
    Create or open the app in the HiBob Developer Portal.
  2. Register the exact redirect URI

    Copy the Redirect URI shown on HiBob app and register it in the Developer Portal. Its format is:

    https://<lms-domain>/local/hibob/oauth2callback.php

    Replace the example domain with the actual LMS domain by copying the value from your app settings.

  3. Save the app credentials and installation URL

    On HiBob app, save the Client ID, Client secret and full App Installation URL. The installation URL contains the scopes. Paste the Developer Portal webhook secret into Webhook secret when using OAuth webhooks.

    SettingValue / guidance
    OAuth token URLhttps://auth.app.hibob.com/oauth2/v1/apps/token
    API base URLhttps://api.hibob.com/v1, unless IT specifies otherwise
    Redirect URICopy exactly from HiBob app and register in HiBob
    Webhook URL and secretUse the app-wide values for OAuth; see Synchronisation
    LMS HiBob app OAuth configuration screenshot
    Save the shared API, OAuth and webhook configuration on HiBob app.
  4. Connect the company and approve consent

    Open the company connection, leave Service user off and select Connect to HiBob. Review the requested permissions and choose whose people data the app can access, then select Authorize.

    HiBob OAuth consent screenshot
    Review the permissions and employee access scope before authorising.
  5. Reconfirm access after scope changes

    Recopy the App Installation URL after changing scopes. If renewed consent is required, uninstall and reinstall the app in Bob.

Disconnect and uninstall are separate actions. Disconnecting in the LMS clears the tokens. Uninstall the app in Bob separately when that is required.

Related official reference: OAuth 2.0.

Source: supplied HiBob Administrator Guide, pp. 8 - 11.

06

SET UP

Quick start checklist

Follow this sequence for a typical employee-sync setup. Configure optional features only where your integration plan needs them.

  1. Confirm access and authentication

    Check the prerequisites. Prepare either the OAuth app or a service user with the required permission group.

  2. Create or open the integration

    In the LMS, open HiBob → Add integration, or select an existing instance. New connections are enabled and named automatically, such as HiBob or HiBob 2.

    LMS HiBob instances list screenshot
    Open or pause connections from the HiBob instances list.
  3. Connect to HiBob

    For OAuth, leave Service user off and select Connect to HiBob. For service-user authentication, turn the switch on and save the ID and token. OAuth app details and API base URL belong on HiBob app.

  4. Confirm employee access

    Check that the LMS can read employees from Bob.

  5. Check field mapping

    Confirm first name and last name. Both email and username should use the work email. Save the mapping.

  6. Set enrolment rules and the activation email

    If needed, configure Enrollment rules, then Activation email, with immediate or delayed sending. Save both before the first import.

    By default, course enrolment is applied when the account is created. See Enrollment rules for the optional Run at the time of sync behaviour. The welcome email is sent for newly created accounts.

  7. Choose the synchronisation method

    On Synchronisation, select a daily schedule or webhook for this company, configure and save the shared user criteria, then use Initial run for the first import. OAuth uses one app-wide webhook URL and secret. A service-user connection uses its own URL and secret here. Then configure any optional Learning features.

  8. Review the first sync

    Open Logs and confirm the run completed successfully.

  9. Pause the connection when needed

    Switch the connection off from the HiBob instances list. New connections start enabled.

Source: supplied HiBob Administrator Guide, pp. 11 - 12; enrolment sync-run detail in section 9, p. 18.

07

TAB 1

Connect to HiBob

Connect the current LMS company to Bob. OAuth is the default; enable Service user only when you are entering a Bob service-user ID and token.

Choose the authentication method

For OAuth, keep Service user off and select Connect to HiBob. For Basic authentication, turn it on, enter the ID and token, and save the connection.

Connect to HiBob OAuth screen screenshot
OAuth connection with Sync users from HiBob enabled.
View the service-user connection screen
Connect to HiBob service-user fields screenshot
The Service user switch reveals the ID and token fields.

Connection settings and defaults

SettingDefault / requirementWhat it does
NameAutomaticThe LMS assigns the connection name, for example HiBob or HiBob 2. You do not enter a name.
EnabledOn by defaultPause a connection using the toggle on the instances list, not on this page.
Service userChoose one methodOff uses OAuth and the Connect to HiBob button. On displays ID/token fields for service-user authentication.
Service user ID / tokenRequired when Service user is onGet these from Bob's Service users settings. Leave the token field blank to keep an already saved token.
Sync users from HiBobOn by defaultCreates and updates employees in the LMS. Turn it off when users already arrive through SSO, SCIM or Active Directory and this connection should only update learning, tasks and certificates for a matching Bob employee.
About this connectionShown for OAuthExplains employee sync and training assignment. Its protection note covers encrypted credentials, renewed access permissions and access restricted to this organisation.
API base URL and OAuth appSite-wide configurationConfigure these once on HiBob app, not on this page. The same API host is used for every company.
When employee import is off: Field mapping, Synchronisation, Enrollment rules and Activation email remain hidden. Learning, task and certificate updates can still use the connection for matching Bob employees.

Common connection mistakes

MistakeHow to correct it
Using an employee passwordCreate a dedicated service user and use its token, not an employee's password.
Changing the API URL on the wrong pageUpdate the host on HiBob app only if your IT team supplies a different value.
An OAuth redirect mismatchCopy the Redirect URI from HiBob app into the Developer Portal exactly. Do not type it from memory.
Trying OAuth with Service user onTurn Service user off to start OAuth. With the switch on, the page saves ID/token credentials.

Source: supplied HiBob Administrator Guide, pp. 13 - 15.

08

CONFIGURE

Field mapping

Choose which Bob employee details populate each LMS profile field, keeping names, emails and departments accurate.

This tab is required for employee sync. Most fields have sensible defaults. Settings are grouped into Basic details, Profile defaults and Custom attributes.

Field mapping interface screenshot
Match Bob employee fields to LMS user profile fields.
Work email is the identity. Email and Username are fixed to the employee's work email from Bob. Check duplicate email addresses before importing users.
All profile fields and defaults
LMS fieldRequirementGuidance
First NameRequiredUsually map to Bob First name.
Last NameRequiredUsually map to Bob Last name (surname).
EmailRequiredFixed to the employee's work email from Bob. The control is disabled.
UsernameRequiredFixed to that same work email. The control is disabled.
Authentication typeOptionalChoose how new users sign in: Manual, OAuth, SAML or Token Auth. For SAML, choose identity provider(s) under SSO Auth Option.
Manager EmailOptionalUsually map to Reports to. The LMS links the manager if that person already has an account.
Default manager IDOptionalUsed when Bob has no manager. Tick Update to refresh on later syncs.
Employee IDOptionalStore HiBob ID or Bob's Employee ID so later syncs can match the same person.
DepartmentOptionalUsually map to Bob Department.
Default departmentOptionalUsed when Bob has no department. Tick Update to refresh on later syncs.
DesignationOptionalJob title from Bob.
Default designationOptionalUsed when Bob has no title, for example Learner. Tick Update to refresh on later syncs.
Team IDOptionalMaps Bob site or location. Leave blank if you do not use teams.
Default team IDOptionalUsed when Bob has no site. Tick Update to refresh on later syncs.
Phone NumberOptionalChoose work mobile, work phone, or leave unselected.
Custom attributesOptionalUp to seven extra profile fields. Use the edit icon to rename each field with 100 characters or fewer. The first three default to City, Country and Site. Enrolment rules can match these attributes.
Missing setup tabs? If Sync users from HiBob was switched off, Field mapping, Synchronisation, Enrollment rules and Activation email disappear. Turn it back on and save.

Source: supplied HiBob User Guide, pp. 16 - 17.

09

CONFIGURE

Enrolment rules

Automatically enrol people in LMS courses when their synced profile matches the rules you define.

The Enrollment rules tab is optional. Skip it if you enrol users manually or through another process. Save and Next on Field mapping opens this tab. Rules use the LMS profile after field mapping.

Set rules before Initial run. Creation rules apply as the account is created, whether the import uses a daily schedule or webhooks. The optional Run at the time of sync setting also enrols matching existing users on later updates and removes their enrolment if they no longer match.

Create and manage a rule

Choose Add rule. The list includes Display archived rules and columns for Rule name, Field, Condition, Value, Course(s) and Actions.

FieldRequirementGuidanceExample
Rule nameRequiredClear internal name, up to 60 characters.Sales onboarding
Course(s)RequiredBeside the rule name. Select at least one LMS course.Induction course
ConditionsRequiredAdd a field, comparison and value on each line. Use + for up to 10 lines. Conditions are explained below.Department Equal to Sales AND Designation Equal to Manager
Due dateOptionalNone, Same as course, fixed calendar date, or a relative number of days.Relative, 30 days
MandatoryOptionalNo leaves the enrolment optional. Yes makes each selected course compulsory. Same as course uses the mandatory flag stored on each course.Same as course
When to runRequiredRun at the time of user creation is on for a new rule. Run at the time of sync can also be enabled to apply rules when existing users are updated.Both on
LMS enrolment rules screenshot
Create profile-based course enrolment rules.
LMS enrolment add condition screenshot
Add field, comparison and value conditions to a rule.
How rule conditions work
  • AND / OR: evaluated from left to right. AND requires every condition so far to match; OR allows either side to match.
  • All: matches every synced user; comparison and value are hidden.
  • Profile fields: Manager, Designation, Team ID, Department and the custom attributes from Field mapping.
  • Comparisons: Equal to, Not equal to, Greater than and Less than. Equal to and Not equal to accept more than one value.
  • User created before / User created after: choose a date; comparison is hidden. The selected day itself is excluded.

Source: supplied HiBob User Guide, pp. 17 - 18.

10

CONFIGURE

Activation email

Welcome new users when their LMS account is created from Bob.

This step is optional if users receive their welcome through an SSO portal, HRIS email or another channel. Save and Next from Enrollment rules opens this tab; Save and Next here opens Synchronisation.

Save before Initial run. The activation email is queued only when an account is created. The same message is used for daily imports and webhook imports.
SettingRequirementGuidance
Activation emailMaster switchWhen off, the Email settings section is unused.
Schedule emailOptionalImmediately, 12, 24 or 48 hours after creation, or Custom with a number of hours. A delay gives authentication time to finish.
SubjectRequired when enabledThe subject recipients see in their inbox.
BodyRequired when enabledWrite the message under Email settings. Use Variables for first name, last name, username, email, organisation, LMS URL or a set-password button. The email does not include a password.
CCOptionalCopy HR or a shared mailbox on every activation email.
Mail attachmentsOptionalOne file, up to 10 MB. Accepted types: PDF, DOC, DOCX, ODT, XLS, XLSX, JPG, JPEG, PNG, CSV, GIF and TXT.
LMS activation email settings screenshot
Optional welcome email settings for new LMS accounts.

Source: supplied HiBob User Guide, p. 19.

11

CONFIGURE

Synchronisation

Choose a daily import or event-driven webhooks, and decide which employees to include.

The same user criteria apply to both methods. If Bob reports an employee as terminated, inactive, left or on garden leave, the LMS suspends their account. The connection must be allowed to see those people.

SettingRequirementGuidance
How employees are synchronisedRequiredSelect Daily schedule or Webhook. Only the chosen method runs.
Run user sync atDaily schedule onlyImport time of day. The offset beside it is the timezone stored for this schedule. Last sync shows the latest completed import, or Not synced yet. No daily run occurs while Webhook is selected.
User sync criteriaOptionalAlways visible. The same field/value rows filter daily imports, webhooks, Initial run and Manual sync. Fields include Manager Email, Designation, Team ID, Department, custom attributes and a user-created date. Leave empty to sync everyone the connection can see.
Initial runRequired onceImports existing employees for either method, because webhooks do not import people already in Bob. The button is hidden after use and replaced by progress cards. Save enrolment rules and the activation email first.
Manual syncOptional; Webhook onlyRecovery when LMS downtime caused missed Bob events. Imports the current employee list once.
LMS synchronisation schedule screenshot
Choose daily schedule or webhook synchronisation.
LMS Initial run screenshot
Run the first employee import with Initial run.
Understand Initial run and progress
  1. Before import: Initial run is visible; the HiBob tabs remain across the top.
  2. Start the import: click Initial run. Synchronisation status replaces the button; queued cards show Processing.
  3. Track jobs: Users added completes first. Enrollment and Activation email show completed totals and remaining items with progress bars.
  4. Check completion: full bars show enrolled and sent counts. If Activation email is off, a note links to its settings instead.
LMS synchronisation processing status screenshot
Synchronisation status while jobs are processing.
LMS synchronisation progress cards screenshot
Progress cards for users, enrolment and activation email.

Pending enrolment and activation cards continue reading progress while jobs wait or cron tasks run. The enrolment card links to Enrollment rules; activation cards or the off-state note link to Activation email. Activation mail is only queued at account creation; later rule execution depends on each rule's Run at the time of sync setting.

How webhooks are configured

Webhooks apply employee hires, updates and departures as Bob sends them. Daily imports stop while Webhook is selected. Logs → Webhook events stays available with either method.

ConnectionWhere configuration livesWhat each company sees
OAuthA site administrator sets one shared app Webhook URL and secret on HiBob app.Every OAuth company shares this pair but chooses Daily schedule or Webhook independently. Synchronisation shows a note and Manual sync; it does not edit the app secret.
Service userConnection-specific Webhook URL and secret on Synchronisation.Select Webhook to see the URL and secret for that connection.
Set up OAuth webhooks
  1. Open developers.hibob.com → your app → Develop → Webhooks.
  2. Turn on Allow event subscription.
  3. Paste the LMS Webhook URL from HiBob app into Endpoint URL and validate it.
  4. Copy the portal Secret into Webhook secret on LMS HiBob app and save. Leave the field blank on later edits to keep the saved secret.
  5. Subscribe to employee events: created, joined, deleted and any others you need.
HiBob Developer Portal webhooks screenshot
Configure event subscriptions in the HiBob Developer Portal.
LMS webhook configuration screenshot
The site administrator stores the app Webhook secret on HiBob app.
Set up service-user webhooks
  1. On Synchronisation, choose Webhook and copy the displayed Webhook URL.
  2. Paste it into Bob's webhook configuration and subscribe to Employee created, Employee updated and Employee terminated.
  3. Save in Bob, copy the secret that Bob generates or shows, and paste that same value into the LMS Webhook secret field. This secret belongs to this connection only.
Bob webhook page screenshot
Bob webhook configuration for a service-user connection.
Bob webhook settings screenshot
Register the LMS webhook URL and shared secret in Bob.
Validate the Ping. Bob sends a Ping test during registration; the LMS must return HTTP 200. If it fails, check the complete URL was copied and the integration instance is saved.

Source: supplied HiBob User Guide, pp. 20 - 23.

12

MANAGE

Learning: certificates and task mapping

Share completion certificates and close relevant HiBob tasks when learning is completed.

Learning features are optional. Use only the items your organisation needs.

LMS Learning provider settings screenshot
Optional Learning provider identifier for Bob Learning.

Certificate Sync (Docs API)

Upload issued LMS completion certificates to Bob employee documents through the HiBob Docs API, so HR can view certificates in each person's profile. Skip this if your organisation does not store certificates in Bob.

ControlRequirementWhat it does
Course(s)RequiredChoose the courses whose certificates should upload. Only courses with issued certificates for Bob-linked users appear.
Force re-syncOptionalRe-upload certificates already synced. Leave off to skip previous uploads and process new ones.
Run Certificate SyncActionStart uploads and view each user, course, status, assigned Bob document ID and any error.
LMS certificate sync screenshot
Upload issued LMS certificates to Bob Docs.
Certificate results and recent completions
ColumnMeaning
User Name / Email / CourseLMS user and course whose certificate was uploaded.
HiBob Employee IDBob employee who received the certificate.
Upload StatusSuccess or the error that occurred.
HiBob Document IDFile ID assigned by Bob.
Error MessageBob or LMS detail when an upload fails.
Synced AtDate and time the upload was processed.

Recent completions

Select Last 7 days or another period, then View Completions. The table shows User, Course, Completed, Sync status and Actions. Sync All Certificates stays disabled until completions are loaded. Previously synced rows are marked and skipped unless Force Re-sync is on.

Task mapping

Link LMS completions to open Bob tasks, such as onboarding checklist items. The task closes when the configured All or Any course-completion criteria are met. Skip this if Bob Tasks is not used for learning.

Closed tasks cannot be reopened through Bob's Public API. If a user's LMS completion is reset later, the Bob task stays closed.
FieldRequirementGuidance
HiBob Task NameRequiredEnter the exact name in Bob, for example Complete induction training. The LMS matches an open task for that employee at completion time.
Select course(s)RequiredChoose one or more LMS courses that should close the same task.
Task Completion CriteriaRequiredAll: every selected course must be completed. Any: one completed course is sufficient. Shown in the list as Course completion criteria.
Add task mappingActionOpen the form. List columns: Task name, Selected course(s), Course completion criteria, Status and Actions.
StatusControlPause a mapping without deleting it, for testing or while a task is temporarily unused.
LMS task mapping screenshot
Map LMS course completion to open Bob tasks.
Create and assign the task in Bob

Every employee needs their own open assigned task before course completion can close it. Use the exact same task name in Bob and the LMS.

  1. In Bob, open Tasks → Task lists settings.
    Bob task lists settings screenshot
    Open Tasks → Task lists settings in Bob.
  2. Open a folder, for example General, then choose Create task list.
    Bob create task list screenshot
    Create the Bob task list that will hold the learning task.
  3. Enter a Name, choose Save to folder, and set Task list owner. The owner's permissions apply. Set Timing (time and timezone), then Create.
  4. Open Task list trigger. Leave it on Manual when someone will send the list, then save. The triggering person sends it using their permissions.
    Bob task list trigger screenshot
    Set the task list trigger, often Manual.
  5. Choose Add task → General task.
    Bob add general task screenshot
    Add a General task with the exact LMS task name.
  6. Enter the task Name, exactly matching the LMS HiBob Task Name.
  7. Set Task ownership to Personal.
  8. Under Assignee → Employees, select recipients. Select every employee for a company-wide task.
    Bob general task assignees screenshot
    Assign the task to the required employees.
  9. Save. The list shows Conditions: All company, type General Task and the assignees. Trigger the list so each assignee has an open task. The task closes when the configured All or Any course-completion criteria are met.
    Bob all company task screenshot
    Confirm Conditions: All company after saving the task.
Optional goal mapping in Bob

If your organisation uses Bob Goals, map LMS progress to a goal title and key result that match Bob exactly.

LMS goal mapping screenshot
Optional LMS goal mapping for Bob Goals.
LMS add goal mapping screenshot
Add a goal mapping in the LMS.
Bob browse goals menu screenshot
Open Browse goals in Bob.
Bob browse people's goals screenshot
Review people's goals in Bob.
Bob goal owners everyone screenshot
Select everyone when mapping company goals by name.
Bob goal key result screenshot
Confirm the key result name matches the LMS mapping.
Bob my goals saved screenshot
Confirm the goal is saved for the employee in Bob.
How task matching works
  1. A user completes a mapped LMS course.
  2. The configured All or Any course-completion criteria must be met before the corresponding task is closed.
  3. The LMS finds their Bob employee ID in the user map.
  4. The LMS calls Bob's GET /v1/tasks and looks for an open task whose name exactly matches the mapping.
  5. If a match is found, the task is marked complete in Bob.
  6. If there is no matching open task, a warning is logged. This is not an error; the employee simply has no open task with that name.

Source: supplied HiBob User Guide, pp. 24 - 26.

13

MANAGE

Logs

Review recent activity to check integration health or investigate a problem.

This tab is read-only: it does not change settings. Sync logs, API logs and Webhook events are separate items in the Logs menu.

Log typeWhat it shows
Sync logsEmployee import and learning sync results, including successes and errors.
API logsIndividual LMS calls to Bob. Useful when support asks for a timestamp or error code.
Webhook eventsBob messages for employees who were created, updated or left.
Last 30 days. Search by person, message or error text to find a relevant entry.
LMS HiBob logs screenshot
Review Sync logs, API logs and Webhook events.

Source: supplied HiBob User Guide, p. 27.

14

REFERENCE

Troubleshooting

Use the symptom to find the next check.

ProblemLikely causeWhat to do
Connectivity test fails (401)Incorrect ID/token, whitespace, or a regenerated token not updated.Re-copy the ID and token from Bob, paste carefully, save and retest. Confirm auth type is Service user.
Connection works, but no employeesEmpty permission group, restricted Access rights or sync filters.Confirm service-user membership; grant People's data View; widen Access data for; clear User sync criteria; run Initial run; check Sync logs.
Some profile fields stay blankMissing permission for the field's Bob category.Grant View for that category. Remapping alone is not enough.
Leavers are not suspendedInactive people excluded or Lifecycle not viewable.Include inactive people in Access data for and grant Lifecycle View. The LMS suspends terminated, inactive, left and garden-leave accounts.
Duplicate or incorrect usernamesTwo Bob people share a work email, or an LMS account already uses it.Username is always the work email and cannot be changed. Correct the duplicate email in Bob or the existing LMS account.
OAuth shows "Not connected"Redirect URI mismatch or unsaved credentials.Save client ID, secret and URL first. Copy the Redirect URI exactly into the HiBob portal, then Connect.
OAuth token expiredRefresh token unused for about 60 days, or revoked.Choose Reconnect and complete consent again.
Learning is not appearing in BobLearning push-back off, missing provider identifier or permissions.Enable Learning push-back; confirm the provider identifier; grant Learning permissions; check API logs.
Certificate upload failsMissing Docs Shared upload permission.Grant People → Docs → Shared Upload/View.
Task is not closed in BobName mismatch, no open task assigned to that person, or missing Tasks permission.Match the task name exactly. Ensure the task list was triggered and the employee is an assignee with an open task. Grant People's tasks. Closed tasks cannot reopen through the API.
Goal progress is not updatedGoal title, key result or owner does not match; or Goals permission is view-only.Use the same goal title and key-result name as Bob. Mapping by name requires a goal owned by that employee (Browse goals, Type Company, everyone selected). Grant Goals permission for that goal type, including key-result updates. Check API logs.
Webhook does not fireURL unregistered, secret mismatch, or LMS not publicly reachable.Service user: re-copy URL from Synchronisation with Webhook selected and match the secret. OAuth: administrator checks the app URL and secret. Confirm Ping returns HTTP 200; check Webhook events.
Firewall or timeoutLMS cannot reach api.hibob.com or auth.app.hibob.com.Allow outbound HTTPS and retry the connectivity test.

Source: supplied HiBob User Guide, pp. 28 - 29.

15

REFERENCE

Glossary

The terms used throughout this guide.

Bob / HiBob
Your organisation's HR platform for people data, organisational structure, learning and goals.
Service user
A system account, not a person, for API access using an ID and token. The permission-group User type is Service user.
Permission group
Bob settings that grant Features, People's data and Access rights to the service user.
API base URL
The address the LMS uses to contact Bob. Default: https://api.hibob.com/v1. Set once on HiBob app and copied onto each connection when saved.
OAuth 2.0
The default connection on Connect to HiBob. The OAuth app is configured once on HiBob app. Enable Service user instead when entering a service-user ID and token.
Webhook
An employee-change event sent by Bob as it happens. Each company chooses webhooks or a daily schedule. OAuth uses one app URL and secret; a service-user connection uses its own values on Synchronisation.
Field mapping
Rules that copy Bob employee fields into LMS user profile fields.
Enrolment rule
Automatic course enrolment when a synced LMS profile matches one or more conditions joined by AND or OR.
Learning provider identifier
A short code that identifies this LMS in Bob Learning.

Source: supplied HiBob User Guide, p. 29.

16

REFERENCE

Official HiBob references

Use the official documentation for platform and API setup.

Prepared from document version 3.3, "HTML administrator guide", local_hibob. The source guide is for administrator use.

Source: supplied HiBob User Guide, pp. 29 - 30.

Download the original PDF. Keep the Administrator Guide for offline setup and handoff to HR, L&D or IT.

Download original guide

Your questions, answered

A clearer path
to your first sync.

Quick answers to common questions about the SucceedLEARN and HiBob integration.

Go to troubleshooting
What does the SucceedLEARN and HiBob integration do?

It connects Bob employee data with LMS administration. Depending on your configuration, you can create and update learner profiles, apply course enrolment rules, send welcome emails to newly created users, upload completion certificates and close mapped open Bob tasks.

Do we need a service user to connect?

Not for the default OAuth connection. Leave the Service user switch off to connect through OAuth after the app is configured. Turn it on only when your organisation is using a Bob service-user ID and token.

Can we keep our existing SSO, SCIM or Active Directory user setup?

Yes. Turn off Sync users from HiBob when users already arrive through another process. The connection can then update learning, tasks and certificates for matching Bob employees. Employee mapping, synchronisation, enrolment-rule and activation-email tabs are hidden in this mode.

Can we choose which employees are included?

Yes. Bob access permissions define which people the connection can see. User sync criteria in the LMS can further filter that audience. The same criteria apply to daily imports, webhooks, Initial run and Manual sync.

Is Initial run needed when we use webhooks?

Yes. Webhooks do not import employees who already exist in Bob. Initial run imports the existing audience once. Manual sync is available in webhook mode to recover from missed events, for example after LMS downtime.

When do course enrolment rules run?

New rules are enabled to run when a user is created. You can also enable Run at the time of sync to apply them to existing users during later syncs. That option removes an enrolment if the person no longer matches the rule. Configure your rules before Initial run.

When are activation emails sent?

The optional email is queued only when an account is created. Choose Immediately, 12, 24 or 48 hours later, or a custom delay. The message can contain a set-password button; it does not include a password.

What happens when an employee leaves?

When Bob reports terminated, inactive, left or garden leave, the LMS suspends the account. The connection must have access to those people and the required Lifecycle permission for the service-user route.

Can the integration reopen a completed Bob task?

No. Bob's Public API cannot reopen a closed task. Resetting an LMS course completion later leaves the Bob task closed. Each employee must have their own open, assigned task with an exactly matching name before completion can close it.

Where do we check sync errors and activity?

Use the read-only Logs menu: Sync logs, API logs and Webhook events. The guide specifies the last 30 days of activity, searchable by person, message or error text. The troubleshooting section lists the next checks for common issues.

Bring your workflow together

Make HiBob part of
your learning workflow.

Explore how SucceedLEARN can connect employee information, course enrolment and completion records for your organisation.

See the integration in action

Speak with our team about connecting HiBob employee data with SucceedLEARN learning administration.

Request a Demo

Already setting up? Open the quick-start checklist.