When a team member leaves your team you may want to transfer their work to another team member. This article provides some advice for managing this process.
​
The first thing to know is that ownership of an Essentials work item, deployment, or org cannot be transferred. This preserves the audit trail of who created an Essentials asset.

There are some options for to maintain process continuity:
​
1) Sharing--If a deployment or work item created by a departed team member has been shared using the "Deploy" permission with another team member, this second team member can deploy that deployment or work item.
​
If an asset has NOT been shared by the owner, Essentials Tech Support can activate an option that allow Essentials Team Owners the ability to log in as the departed user so that they can modify the sharing settings for the deployments and work items owned by the departed team member.
​
2) Cloning--Deployment and work items can be cloned by any user with access to the asset
​
3) Integration User--Organization connections owned by this person can be replaced with the credentials from a remaining team member. Alternatively, consider using an "integration user" for org connections. This will eliminate the need to recreate a connection when a team member leaves.
​