Notification events (Provisioning)
You can dispatch notifications in response to the following events in HelloID Provisioning:
Triggered by an Account Access Grant entitlement action.
Useful for end users, because at this point their account is active and they can log in.
Triggered by an Account Update entitlement action, but only when changes are actually written into target accounts. If no changes have been written, no emails will be sent.
Useful to keep managerial and IT staff apprised of changes within their departments and systems.
Note
The {{Account.}} variable is not available in Account Update notification events.
{{differences}}
The {{differences}} variable in the message body inserts a summary of changes being written to the target account's mapped attributes.
Triggered by an Account Access Revoke entitlement action.
Useful to keep managerial and IT staff apprised of changes within their department and systems.
Triggered by an Account Revoke entitlement action.
Useful to keep managerial and IT staff apprised of changes within their departments and systems. Generally not useful for end users.
Note
For Active Directory target systems, the only notification variables available in Account Delete notifications are {{Person.}}, {{Account.}}, and any custom variables you've added via the Account property of $result in the Post-action scripts.
For PowerShell target systems, the only notification variables available are {{Person.}}, {{Account.}}, and any custom variables you've added via the Account property of $result in the Account scripts.
Other variables are not available, since the account is being deleted.
Triggered by an Evaluation. Not tied to a particular target system.
The {{SummaryHtml}} variable in the message body inserts a tabulated summary of Entitlements that will be granted or revoked during Enforcement.
Triggered by an Enforcement that meets any Thresholds. Not tied to a particular target system.
The {{SummaryHtml}} variable in the message body inserts a list of entitlement Grant and Revoke actions that were blocked during enforcement. This is the same information shown when you View blocked actions.
Triggered when Person lifecycle has been set up, and a relevant schedule runs. An onboarding email is sent for any person who is X days out from onboarding, where X is your configured Pre-onboarding value.
{{contract.}}
The {{contract.}} variable in the message body of a pre-onboarding or pre-offboarding notification event is the contract which triggered onboarding or offboarding, respectively. The onboarding contract is the contract with the earliest StartDate, and the offboarding contract is the contract with the latest EndDate.
This is often (but not necessarily) the person's Primary contract.
All fields in the Contract schema are available.
Triggered when Person lifecycle has been set up, and a relevant schedule runs. An offboarding email is sent for any person who is X days out from offboarding, where X is your configured Pre-offboarding value.
{{contract.}}
The {{contract.}} variable in the message body of a pre-onboarding or pre-offboarding notification event is the contract which triggered onboarding or offboarding, respectively. The onboarding contract is the contract with the earliest StartDate, and the offboarding contract is the contract with the latest EndDate.
This is often (but not necessarily) the person's Primary contract.
All fields in the Contract schema are available.