# Saelsforce leaver process deployment

**URL:** <https://developer.sailpoint.com/discuss/t/saelsforce-leaver-process-deployment/89012>\
**Category:** SHF Discussion and Questions\
**Tags:** connectors, identity-security-cloud\
**Created:** [November 8, 2024, 2:36pm UTC](https://developer.sailpoint.com/discuss/t/saelsforce-leaver-process-deployment/89012 "2024-11-08T14:36:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mcheek](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mcheek/32/23705_2.png) [@mcheek](https://developer.sailpoint.com/discuss/u/mcheek)\
**Post date:** [November 8, 2024, 2:56pm UTC](https://developer.sailpoint.com/discuss/t/saelsforce-leaver-process-deployment/89012/2 "2024-11-08T14:56:28Z")

</div>

I have linked an example below where someone has documented various workflows on how to remove ALL access from an identity on a leaver lifecycle state change.

In your case, you can take this example and adapt it to only remove entitlements for your SalesForce source

> [@Workflow to remove ALL leavers' standing access](https://developer.sailpoint.com/discuss/t/workflow-to-remove-all-leavers-standing-access/13025):
>
> Hi everyone, This workflow auto-revokes any standing access leavers have either through a micro targeted access certifications or by leveraging revoke access requests after being terminated. This should ensure that all leavers’ access is removed upon terminated and not just access assigned through birthright roles. Additionally, an audit trail is generated to document when and why the access was removed. This workflow was designed and built with the help and input of a multiple people! Thank…

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/saelsforce-leaver-process-deployment/89012)._