We would like to request an enhancement to HelloID provisioning regarding timing of target attribute updates.

Currently, when a source attribute is changed or becomes available, HelloID will immediately update the corresponding target attribute during provisioning. There is no possibility to take into account a future effective date, such as a contract start date. This means that attributes are always provisioned as soon as they are detected, even if they should only become active at a later moment.

For many organizations, there is a strong need for future-dated or conditional provisioning, where certain attributes should only be set or activated after a specific date field has been reached (for example: contract start date, first working day, onboarding date, etc.).

We would like to have functionality that allows something like:

“Only update this target attribute when today >= contractFromDate (or another date field).”

Without this, it is currently not possible to properly align provisioning with real employment start dates, and external scheduling or custom workflows are required.

Example:

We use SSRPM for password resets, where an SMS is sent to the phone number stored in SSRPM.

When our support desk sets a work phone number in HelloID, this is immediately provisioned to SSRPM.

If this happens before the employee has started, the password reset SMS is sent to the work phone number, which the employee cannot access yet.

Ideally, we would like the script that sets the work phone number to only run about two weeks after the contractFromDate, so after the employee has actually started.

At the moment, this is not possible with native HelloID provisioning rules.