How to Deactivate and Remove Leavers via the API

Summary This article explains the current behavior for handling leavers via the API and describes practical steps you can take to ensure leavers are deactivated or removed from views.

Current behavior for leavers and the API

• Integrations (including the Bamboo integration used to sync users) do not automatically delete or automatically deactivate users.
• The leaver process is mostly manual: marking someone as a leaver and revoking access requires manual updates to fields in the user profile.
• Setting an end (leave) date in a user’s profile will disable their access and notify managers, but other profile fields still need manual updates for the full leaver process.
• Support can manually deactivate or delete leavers on request.

How to ensure leavers are removed from dashboard views and feeds

1. Set an end (leave) date in the user’s profile to disable their access.
2. For objectives to drop off dashboard views, either:
   • Delete open objectives for the leaver, or
   • Mark the objectives as complete.
3. If you expect automated deactivation but users remain active, request manual deactivation from support — you can provide a list of leavers and support can deactivate them.

Requesting automation changes

• You can ask support to escalate or discuss changes to integrations so they will auto-deactivate users in future. Support can make a request to the team to explore enabling auto-deactivation via the integration.

Practical steps to follow now

• When an employee leaves:
  1. Set their end (leave) date in their profile to disable access and notify managers.
  2. Review and either delete or mark open objectives complete so they no longer appear on dashboards.
  3. If you need the account deactivated immediately and it remains active, contact support and provide the employees to be deactivated; support can perform manual deactivations.
  4. If you want automated deactivation via your integration, request that support escalate this as an enhancement.

Troubleshooting tips

• If leavers still appear on feeds (for example, “Who’s Celebrating”) after setting them as leavers, check whether the account was actually deactivated; if not, request manual deactivation from support.
• If some leavers were removed and others were not, provide examples of affected users to support so they can investigate specific cases.

Conclusion Integrations do not currently auto-delete or auto-deactivate users. Use the profile end (leave) date, clean up objectives (delete or mark complete) to remove leavers from dashboards, and contact support to manually deactivate accounts or to request that auto-deactivation via the integration be considered.