Synchronisation with HRIS
You may already have an HRIS with all the Team structure and Contributor information. Rather than double-entering the information in your HRIS and then again in Echoes, we propose to configure Echoes to synchronizes periodically with your HRIS. To support a large number of HRIS we embed a third-party connector named Finch from inside Echoes. The setup is as follows: connect your HRIS with Finch, then configure the synchronization in case you want to limit the synchronization to a small number of Teams (for instance, to select only engineering teams).
The HRIS system will then periodically synchronize:
- the Team tree of all subteams selected for synchronizatoin
- the Membership of all these (including name, current Team of attachment, and work email)
Automated synchronization systems can go sideways, in particular we prevent automated large deletions of teams. Such an event could occur because of technical errors, clerical errors in the HRIS, or expected large team re-shuffling. Since Echoes does not have the full-context, we prevent the synchronization resulting in large changes and get alerted if the synchronization is stuck for too long. It is always possible to run a one-off synchronization with a visual preview of the change.
On the Teams page, select the HRIS mode. Then click Install Finch an in-browser window will open and ask you to connect your HRIS. You will need credentials and the specific process may change depending on your specific HRIS solution.
ο»Ώ
ο»Ώ
Once connected, you can always re-install Finch and follow the same procedure if your HRIS changes.
When you have a working HRIS connection you can prompt a listing of the Team-tree as Echoes understands it and lets you pick the one you will synchronize automatically. All subteams of a selected Team will also be synchronized.
For instance, in this example, we unselect the "Product" Team because the team has not onboarded on Echoes yet.
We recommend you run a one-off synchronization after connecting or re-configuring an HRIS. The one-off synchronization will show you a summary of the changes that will take place. And if these changes include a lot of Team changes you will be able to notice and adapt the configuration if required.
In the above example we see that removing the "Product" teams actually remove a teams and move their members to the undispatched team (which is not billed).
