# Boto3 API quicksight: user deletion and orphaned resources **URL:** \ **Category:** Q&A\ **Tags:** api, feature-request, developer, quick-sight\ **Created:** [July 26, 2022, 6:20am UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942 "2022-07-26T06:20:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Shivani\_Gupta](https://avatars.discourse-cdn.com/v4/letter/s/e9bcb4/32.png) [@Shivani\_Gupta](https://community.amazonquick.com/u/Shivani_Gupta)\ **Post date:** [July 26, 2022, 6:20am UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942/1 "2022-07-26T06:20:00Z")
When deleting a Quick Sight user from AWS web console I am given two options in regards to user-created resources that will be orphaned: - transfer ownership to a different user - delete all orphaned resources. But when using Python boto3 [QuickSight - Boto3 1.40.46 documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/quicksight.html#Quick) Sight.Client.delete\_user it merely removes the user, leaving all orphaned resources. Is there a way to support both of the choices from the AWS boto3 API? ---
**Author:** ![agmayan](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/agmayan/32/300_2.png) [@agmayan](https://community.amazonquick.com/u/agmayan)\ **Post date:** [September 12, 2022, 5:57pm UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942/2 "2022-09-12T17:57:45Z")
Hi, Currently there is no direct API to transfer resources from one user to another. You can however use combination of APIs to achieve this. For e.g. dashboards: - [ListDashboards](https://docs.aws.amazon.com/quicksight/latest/APIReference/API_ListDashboards.html) - [DescribeDashboardPermissions](https://docs.aws.amazon.com/quicksight/latest/APIReference/API_DescribeDashboardPermissions.html) - [UpdateDashboardPermissions](https://docs.aws.amazon.com/quicksight/latest/APIReference/API_UpdateDashboardPermissions.html) ---
**Author:** ![Kristin](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/kristin/32/2470_2.png) [@Kristin](https://community.amazonquick.com/u/Kristin)\ **Post date:** [September 18, 2022, 2:39am UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942/3 "2022-09-18T02:39:19Z")
Hi, @Shivani_Gupta. We hope that Koushik’s solution worked for you. I am marking his reply as, “Solution,” but let us know if this is not resolved. ---
**Author:** ![khushalt5](https://avatars.discourse-cdn.com/v4/letter/k/4da419/32.png) [@khushalt5](https://community.amazonquick.com/u/khushalt5)\ **Post date:** [September 28, 2022, 7:22am UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942/4 "2022-09-28T07:22:21Z")
@Kristin QS behavior should be consistent whether you are using from UI or API calls so can you make a feature request for this since what @agmayan suggested is a very long route to achieve the objective Hope to see this feature in boto3 API soon ---
**Author:** ![Colin\_Lindley](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@Colin\_Lindley](https://community.amazonquick.com/u/Colin_Lindley)\ **Post date:** [October 6, 2022, 1:27pm UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942/5 "2022-10-06T13:27:07Z")
Our team would benefit from being able to specify the transfer of orphaned users, as we need to migrate 200+ users to new usernames. The above proposed solution is not ideal as there are multiple components to consider with more opportunities to mess something up, which is not what you want when dealing with deleting users. ---
**Author:** ![agmayan](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/agmayan/32/300_2.png) [@agmayan](https://community.amazonquick.com/u/agmayan)\ **Post date:** [October 9, 2022, 5:02am UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942/6 "2022-10-09T05:02:01Z")
I will take this new feature request and include in the roadmap. In the meantime please lookout for new launches in this community or Quick Sight’s main website. [Business Intelligence Service – Amazon QuickSight – AWS](https://aws.amazon.com/quicksight/) ---
**Author:** ![Colin\_Lindley](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@Colin\_Lindley](https://community.amazonquick.com/u/Colin_Lindley)\ **Post date:** [November 21, 2022, 5:37pm UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942/7 "2022-11-21T17:37:52Z")
I would appreciate if someone could reach out internally with the SIM information for this PFR. I’ve reached out twice, as I would like to track this, but have received no response. ---
**Author:** ![isis\_oliveira](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/isis_oliveira/32/14660_2.png) [@isis\_oliveira](https://community.amazonquick.com/u/isis_oliveira)\ **Post date:** [April 22, 2024, 9:04pm UTC](https://community.amazonquick.com/t/boto3-api-quicksight-user-deletion-and-orphaned-resources/4942/8 "2024-04-22T21:04:19Z")
Hello, I would also like to make a suggestion regarding the transfer of resources when deleting a Quicksight user. But this is within the console itself and not the API. It would be very interesting if there was the option to create a folder or something so that the old user’s resources would all be organized somewhere for the user who inherited them to explore, instead of being loose and dispersed. Thank you.