We have moved the Talos Perform integration with HiBob (Bob) onto a new, more secure connector that uses OAuth instead of an API key. Bob now also lists Talos Perform as an official app in the Bob Marketplace.
We have already switched your integration over and carried across all of your settings. There is one step we cannot do for you: authorising the new connection from inside your own Bob account. This guide walks you through it and should take about five minutes.
Important: Your user sync is paused until this is done. No new joiners, changes or leavers will come through from Bob into Talos Perform until the new connection has been authorised.
What we have already done for you
You do not need to set the integration up again. We have copied all of the following across from your previous connection:
User field mappings
Sync schedule
Run completion notification email addresses
New joiner welcome email settings
The internal references that link each Talos Perform user to their record in Bob
You have already accepted the Apideck sub-processor terms, so you will not be asked to do that again.
Info: Because your mapping is already configured, there is nothing for you to set up or change. If anything does not look right after you reconnect, please email [email protected] rather than adjusting the configuration yourself. It is much quicker for us to put right if the settings have not been altered.
Before you start
You will need to be:
A Talos Perform user with Configurator, Administrator and Moderator access
A user with permission in HiBob to install apps from the HiBob Marketplace, and access to the employee data you share with Talos Perform
This is usually the same person. If not, arrange to do it together, as the authorisation happens in one continuous flow.
Read this before you authorise
Important: When you authorise, Bob asks you to choose whose employee data Talos Perform can access (People data access). Choose the same group of people your integration covered before, which for most organisations is everyone.
Remember the selection needs to cover everyone who logs into Talos Perform, not only the people who are reviewed. That includes:
Managers and other reviewers who complete reviews for other people
People who give 360° feedback
HR staff who run reports or administer the system
If your organisation does need to restrict which employees are shared, Bob's filtering options on that screen let you do so. Just make sure the group you choose still covers everyone who needs a Talos Perform account, and let us know so we can help you check the result.
If you are unsure what to choose, contact [email protected] before you authorise rather than afterwards.
Step 1 - Open your user provisioning settings
Log into Talos Perform and go to the User Provisioning section of the configuration.
Step 2 - Authorise the new connection
Press the Open Settings button to launch the Apideck vault.
In the Added section, find HiBob (OAuth). It will show as Unauthorised.
Click Authorise.
Bob's consent screen appears. Check the permissions being requested, choose your People data access as described above, and approve.
You are returned to the vault once the connection is made. It should now show as authorised.
Exit the Apideck vault.
Step 3 - Run a sync to check it works
Back in Talos Perform, open the HiBob (OAuth) section of the integration panel and press Queue run.
Syncs are queued, so this may take a few minutes depending on how many people you have. You can wait for the completion email and come back to the page.
Step 4 - Check the results of that first run
This is worth two minutes of your time. Open the logs for the completed run and check for:
Any errors. A healthy first run should update your existing people with no errors. Errors usually mean a person could not be matched to their existing Talos Perform account, and they need looking at before the next scheduled sync.
Anyone made inactive who should not be. This would point to the People data access selection being narrower than the group you intended to share.
A spot check. Open one or two people and confirm their job title, department and manager look as you would expect.
Info: If you see errors or anything unexpected, please email [email protected] and we will take a look. Please do not change your field mapping or run another sync in the meantime.
After that, nothing changes
Once the first run looks correct, your integration carries on exactly as before, on the same schedule, with the same mapping. You can still start a run yourself at any time from the Runs tab.
Getting help
If you run into any problems at any point, please contact [email protected] or speak to your Customer Success Manager, and we will help you get connected.