1. User clicks on "More Info" (Delete my Account)
2. Dialog explaining the implications and a link to the documentation (for more details) is displayed
3. The list of child packages is displayed along with the language which conveys that by proceeding the user understands that he/she will be relinquishing ownership of these packages.
4. User fills out the form and clicks "Yes, delete this Account"
5. An email notification is sent to the account owner stating that an Account deletion request has been received. This is a safety check to ensure that this request was initiated by the authorized account owner.
6. Admin team reviews the request
7. The account can be immediately deleted if one of the following conditions is met

• No child packages exist
• Child packages if any have co-owners (packages won't be orphaned when the account is deleted)

8. If the account has child packages at risk of being orphaned, the Admin team will work with the account owner to transfer the ownership of the package.

• The admin team would have the SLA time-frame to affect the transfer of ownership
• At the end of the SLA time-frame, if ownership has not be transferred, the packages must be re-parented under "Deleted Account"

9. After receiving the request to delete an account, the account must be deleted within SLA time-frame
10. The SLA time-frame is 60 days
11. After the request is approved, an email notification is sent to the account owner with this information along with date on which the account deletion will actually happen.
12. A final email notification is sent after the account has been deleted.

UI Mocks

User Facing

Admin Facing

Account Deletion Workflow