SSOID: Talent Suite Onboarding New Hire Export

SSOID: Talent Suite Onboarding New Hire Export

Abstract

What is the SSOID?

When creating a new hire export for an Onboarding Talent Suite client, you must add the element SSOID to the export. This is not a field in the system, so you will not be able to add it to your export mapping document as you would a field.

SSOID is a unique identifier created by Onboarding for the use of updating the new hire in Gate Keeper. This happens behind the scenes, but the PSE group is aware of it and knows how to export it.

A hive ticket to the PSE to add this element to the export is all that is needed. You can make this a part of your New Hire Export ticket or your migration New Hire Export TS changes ticket. Example of this hive ticket is 184350.

Why must the SSOID be exported in the New Hire Export for Talent Suite clients?

The SSOID must be exported to the client's HRIS system from Onboarding and should be stored by the client as a field for each record in their HRIS. Everything filters through the Talent Suite.

When new hires get sent to Onboard New Hire from Brassring, they are sent a link to the Talent Suite where they log in and complete their Onboarding tasks. Occasionally a new hire will be a recruiter, hiring manager, admin, and so on, and will need access to Brassring and Onboard.

Since these new hires already came through Onboard New Hire and are present in Gate Keeper, the SSOID is the unique identifier for Gate Keeper to update this new hire as also a user of Brassring and Onboard in the Talent Suite.

The way users are provisioned for the Talent Suite, you have to produce a csv file to the Gate Keeper team, giving certain users access to the different interfaces in the Talent Suite. This SSOID must be in the file for anyone who came through Onboard New Hire and also needs to be a user anywhere in the Talent Suite.

Migration/Upgrade implementations only: It's very important that this be discussed early in the process because a client's New Hire Export for Onboarding must change. While it would seem not to be an issue to add a field to the export and have a client build that into their import and house that in a field in their HRIS system, it is a big issue for certain clients. Some clients outsource their HRIS imports and have no one in the company who can build fields into imports or add new fields in their HRIS to support the SSOID. Such clients need to find resources to modify their HRIS system, and this shouldn’t happen late in the process when Go Live is near.