# Succession Planning for Departing Users

**URL:** <https://forum.asana.com/t/succession-planning-for-departing-users/915017>\
**Category:** IT\
**Tags:** productivity\
**Created:** [10 September 2024 22:19 UTC](https://forum.asana.com/t/succession-planning-for-departing-users/915017 "2024-09-10T22:19:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zach\_Ciaburri](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/zach_ciaburri/32/119457_2.png) [@Zach\_Ciaburri](https://forum.asana.com/u/Zach_Ciaburri)\
**Post date:** [10 September 2024 22:19 UTC](https://forum.asana.com/t/succession-planning-for-departing-users/915017/1 "2024-09-10T22:19:46Z")

</div>

I have a lot of automated processes across our projects and I am wondering how to efficiently replace assignee’s when there is staff turnover. I am not talking about currently assigned tasks being reassigned, I mean when you have subtasks and assigness automatically assigned through rules and workflow. The way I think it SHOULD work is that these rules should be setup with project roles, then you can reassign the project role and everything follows suit. As far as I can see there is no way to do this without adjusting everything manually. This seems odd because I feel like succession planning should be a top concern for a productivity app? What am I missing? Thanks!

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [11 September 2024 05:22 UTC](https://forum.asana.com/t/succession-planning-for-departing-users/915017/2 "2024-09-11T05:22:42Z")

</div>

Hi @Zach_Ciaburri , I agree this would be incredibly useful.

Until if/when Asana decides to add this feature, you may find some tips in this useful thread:

> [@Remove/Offboard/Deprovision (or Pause) a User from an Organization, and what to do beforehand](https://forum.asana.com/t/remove-offboard-deprovision-or-pause-a-user-from-an-organization-and-what-to-do-beforehand/202645):
>
> Before you remove a user from your organization it’s good to take several steps to avoid possibly losing some item access (which could require Asana Support to restore). I couldn’t find this information in one place, and since it’s hard to remember when only periodically needed, I decided to create this as a reference. Before removing the user, consider carrying out these steps for any items you care about: Note: These steps are easiest to carry out if you log in with the credentials of the…

…which links also to this thread:

> [@Offboarding report: a tool to manage an employee leaving](https://forum.asana.com/t/offboarding-report-a-tool-to-manage-an-employee-leaving/238785):
>
> Hi, If you have been using Asana for a while and were confronted with a user leaving, you know it usually leaves a trail of problems: templates they owned can’t be edited anymore, custom fields they created were locked, nobody is notified to update goals they owned… At iDO, we like to create useful tools, and we created [Offboarding report](https://minimalist-work.com/asana/offboarding-report). The tool will generate a report of all objects owned by someone leaving. Word of warning: we suggest the employee runs the tool themselves because they m…

It seems like @Bastien_Siebman tool doesn’t support Rules, though. Perhaps he can confirm here.

---

<div class="post-metadata">

**Author:** ![Zach\_Ciaburri](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/zach_ciaburri/32/119457_2.png) [@Zach\_Ciaburri](https://forum.asana.com/u/Zach_Ciaburri)\
**Post date:** [11 September 2024 17:35 UTC](https://forum.asana.com/t/succession-planning-for-departing-users/915017/3 "2024-09-11T17:35:27Z")

</div>

Thank you Richard. I did see these before posting and they are definitely good steps to take. I am not seeing anywhere that helps address departing users that are tied to automation assignments.
