Skip to main content

Integrations: Having more than one

Maria Ørgaard avatar
Written by Maria Ørgaard
Updated this week

Yes, you read that correctly. It is possible to have more than one integration running at the same time. Here's what you need to know💡


When running two or more integrations at the same time, it is crucial that we follow best practices to avoid conflicts, data errors or potential time-consuming cleanups. These guidelines will go through the best practices to mitigate these risks.

Last Day Should Be Used

When two integrations are active, the deactivation setting cannot be used. If it is, the systems will conflict with one another and deactivate users that should not be deactivated.

Instead, both integrations must have a “last day” set in their respective systems to ensure proper offboarding. Not doing this will result in messy data and a time-consuming cleanup process.

Unique Users Across Integrations

Each integration must manage a distinct set of users. Never assign the same user to both integrations. This prevents duplicate users, errors with synchronisation and general confusion.

Department Names Must Be Different

Departments must have unique names in each system. If a department name is reused in both integrations, it will create conflicts during synchronization. We recommend reviewing department naming conventions in advance to avoid duplication.

Integration Management Access

If you are using two different systems, it is possible to set up both in the Hub (for example, Planday and Entra). If the requirement is the same system twice, for example, two different Entras, then only one of the integrations can be directly managed by you in the hub. The second integration will run in the background and can only be monitored and maintained by our team. If you need changes to the background integration, please contact us directly.

Did this answer your question?