Employee immediate access revocation
Triggered when a termination flow completes, including all required approvals, with Revoke access immediately selected. If no approvals are required, it triggers when the flow completes—you don't wait until the employee's future termination date.
This option must be enabled in the termination flow's Additional steps settings and is available only for termination dates that are today or in the future. It is hidden for past-dated terminations, where access is already removed immediately.
The feature also revokes access to Bob itself. Once all approvals are complete, access to Bob is revoked.
The termination effective date and lifecycle timing remain unchanged. Lifecycle events such as <a href="https://apidocs.hibob.com/reference/post_webhook_employee-left" target="_blank">employee.left</a> and <a href="https://apidocs.hibob.com/reference/post_webhook_employee-inactivated" target="_blank">employee.inactivated</a> still fire on the effective date as usual.
In the Bob UI this event appears as Employee immediate access revocation. Available for Webhooks v2 only. The payload includes employeeId only.
In the right panel, open Examples and select Payload Example to see a real payload.
Headers
Base64-encoded signature sent with each webhook request. Use it to verify that the request came from Bob. To verify webhook authenticity, see <a href="https://apidocs.hibob.com/reference/getting-started-webhooks#how-does-bob-calculate-the-signature" target="_blank">How does Bob calculate the signature</a>.
Payload
Response
Webhook received successfully
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.