Can I transfer ownership of a dataset/analysis/dashboard?

Question & Answer
1

Is it possible to change the primary owner of a dashboard and the associated analysis and data sets? I know that I can share these items and designate a user as a co-owner, but I am hoping for a complete transfer with all owner rights granted.

2

Hi,

There is no primary or secondary owner of an asset. A co-owner has same permissions as original creator of the dashboard and other assets. Are you trying to remove access for original creator of the assets?

3

I guess you could just remove yourself from the dashboard using the QuickSight API (CLI) once you’ve made someone else owner.

4

Removing access isn’t necessarily a requirement, I am trying to plan for a team member that has accepted an internal transfer so their dashboards don’t have an interruption of service

5

Hi Aaron,

In this case making the new person co-owner of the assets should suffice. If this new owner is going to modify that connected datasets, make sure to make this person owner of connected datasets as well.

Thanks
-Mayank

1 Like
6

Hi - i came across this (question) and it is relevant to what I wanted to ask…
as this is a 2 years old thread, I believe the interface in Quicksight may have changed too.

in the current view/interface of Quicksight, I am the creator of dataset (created using SQL), used the dataset to built Analysis and eventually published it as a Dashboard.

I am leaving the company and I would like to give full access to someone in the company. I would like the new person to be able to access the dataset and edit it as well. where should I click to ensure i give complete control and access?

7

Hi, QuickSight do provide option in admin console to transfer asset ownership to another user directly. So an admin can seamlessly transfer assets (dashboards, datasets, analysis, data sources) owned by that user, before removing user from QuickSight account subscription. It is explained in this QuickSight documentation link.

8

Hi,

Our team is facing issues in duplicating a dataset where we are the co-owners and the original creator has left the company.

Is it a limitation with quicksight datasets where only the main owner can duplicate it?

Thanks

9

Hi @aksbhard

For duplicating the dataset user should have access of the DataSource as well. e.g MYSQL, redshift or whatever you are using.

Its available in datasets>> new datasets and below there you have existing data sources.

10

Hi @Shahid_Muhammad ,

The data source in question is S3 , Data is being stored in a S3 folder which the whole team has access to and we are the co-owner of the dataset in quicksight. However, the duplicate button is still inactive for us.

We tried with multiple use cases and it seems to be the person who pushes the data in S3 and created the dataset has access to duplicate. However, for all others it is inactive even though they have the access to the S3 folder and co-ownership in the dataset.

This is acting as a huge blocker for our team.
This is the sample error popup on the duplicate button - You can’t duplicate this dataset because you don’t have access to the following QuickSight data sources: 82f47ab1-2889-42c3-8438-785de5839fb0.

When we try to search this datasource in quicksight, nothing shows up and we all have access to S3 folder to which it is linked to.

11

Hi

The error message you shared clearly depicts that you don’t have the access to Quicksight data source. Once you got that access after that you were able to duplicate the dataset.

12

Yes, but the issue is that when we search this code on quicksight search, nothing shows up and the S3 bucket where the data is being pulled, we do have access to it. So, we do not know what this data source is actually ?

13

Hi

Just go on the dataset and see there you were able to know about the source. please see the below SS.

image
image1655Ă—305 23 KB

1 Like
14

Got it and it seems like the issue with S3 and although our whole team can access the folder in S3, they are not treated as the owner -

In Amazon S3 (Simple Storage Service), the concept of “ownership” is distinct from having access permissions to an object or a folder (also known as a prefix or a directory). Even though your entire team can access a folder, the actual owner of that folder (or any object within it) is determined by the AWS account that created it.
Here’s how ownership and access permissions work in S3:

  1. Ownership: When an object is created in an S3 bucket, the AWS account that created the object is considered the owner of that object. The owner has full control over the object, including the ability to grant or revoke permissions.
  2. Access Permissions: Access permissions in S3 are managed through IAM (Identity and Access Management) policies, bucket policies, and access control lists (ACLs). These permissions determine which IAM users, groups, or roles have access to objects or folders within a bucket, and what actions they can perform (e.g., read, write, delete).

Thanks

1 Like