I have the following issue in AWS QuickSight: A user created a dataset through Athena. Everything worked fine. The user shared the dataset with another user granting him OWNER rights. Then the first user was deleted. Now the second user can't edit the dataset anymore. He can share it but the person it is shared to can't edit it either. The error message:
Hopefully this can be solved by the Quicksight account Admin using the Quicksight UI to add dataset editing permission to this user as shown here.
Or it may well be that the new Owner does not have the required IAM permissions such as quicksight:UpdateDataSet IAM permission, see the docs.
What does it say when you click the "Show details" link in the screenshot above?
This is quite a mess to be honest. The data sources in QuickSight are connected to the user who created it. They inherit their access roles from whoever created them. This is not accessible through the API though I think it is mentioned in the documentation somewhere. Thus it can't be changed.
So when we deleted the users who originally created the data sources they ceased working along with the data sets based on them.
Our solution for this was that we created "standard" data sources with a technical user - this was not such a big deal because we exclusively use Athena - and then recreated all the data sets and switched them to the new standard data sources - this was a big deal because analysts had to switch data sets in their analysis / dashboards.
To me this shows that QuickSight is not quite complete as a analytics platform in large companies. The API is not quite there.
Related
I have a dataset (SSAS) in workspace A, and a report in workspace A that was also copied in workspace B.
People in my organization can see the report in workspace B after I grant them access at report (from workspace B) and dataset (from workspace A). But people in other organization cannot see the report and get this error message:
You cannot see the content of this report because you do not have
permissions to the underlying dataset. Please contact the dataset
owner to request access.
What should I do to grant access to other people to the report?
Should I copy the dataset from workspace A to workspace B? This dataset is pointing to SSAS cube (so it's a live connection) and I have remarked the dataset was not copied when the report was copied (as it usually happens).
I don't have situation as your, but you can check permissions on dataset level -> direct access (without adding access to workspace).
None of the other solutions worked for me. However, I did add [BUILD] access to the user as well as [READ] only, and then it worked.
If RLS is enabled then see below details to provide users access:
https://learn.microsoft.com/en-us/power-bi/enterprise/service-admin-rls
To resolve this issue, you need to:
Remove the users from the dataset permissions and dashboard, and share it again from the dashboard UI, now the users will have the access
For more reference, you can review the reply from PowerBi forum on this.
If this doesn't resolve the issue, make sure to confirm that the granted permissions for users conform to references shared there. (as reports require same level of permissions as dashboards)
I need your help.
I create a dashboard for another sector of our company. The data for the dashboard is from google docs, and people from that sector edit it daily (sometimes changing the name of the columns or removing the column), which makes me manually check twice per week to make sure that the dashboard is okay.
After the dashboard was created that sector doesn't want me to continue accessing their data. Is there any solution that: 1/allow me to check the dashboard when it has problem(s) 2/minimize my access to their private data?
No, if you want to be able to check the report you will need access to the workspace. If you can't have access to the data, then a new report owner who does have access to it will have to take it over from you.
The only other way would be to create a copy of the google docs, with anonymised data, for column changes. You base a report on that, change the connection settings, then deploy it to the workspace. But if you can deploy it, you can technically access the live data in the work space.
I have a report from power bi, which has a direct connection to the server to obtain the data (analisys services). To access the data from my account I use the on premises data gateway, which works correctly and I can view the data in the web app. The problem appears when the report to another user (both having the pro account). From the account of the other user you can see that a report was shared, but when you open it the following error appears: "Error executing the query because the cube or some internal structures have not been processed (or do not exist)" .Also grant owner permissions to the cube to the user in question. Any clue where it might be failing?
I think you should Map usernames for this connection.
Go to settings -> Manage gateways
Under your gateway cluster you should have your data source (if not you can add a new one and it's quite straight forward to set up, just choose analysis services, write in database name of server and credentials) and then you should go to Users tab.
There you can see Map usernames where you need to Replace the account to which you want to share with an account that has permissions in SSMS.
For example you want to share to example#elpmaxe.com and you have granted permissions in SSMS to user named example.elpmaxe, so in map usernames you would replace example#elpmaxe.com with example.elpmaxe
The answer was easy but finding it was difficult. The issue was that even though you had assigned the role in the cube to the user who wanted to share the report, you had not given them read permission (assuming the role had already been assigned). It is a basic problem but if you are a beginner in analysis services it can get complicated.
I have been providing access to datasets in BigQuery using the Share Dataset option for some time now. No problem.
But now, I have a specific requirement: I need to provide access to specific people/account/group but I don't want inherited access to work on this dataset.
I mean, I really need to provide access only to specific people to this dataset, so that not even inherited access work.
Is that possible? And if so, how can I do that?
To add more context. There is a dataset which should be available only for one Service Account (the one populating it) and some specific consumer account (HR) as it will contain sensitive data.
Problem is that our project already contains a couple of BigQuery Admin accounts and they of course inherit permissions over the dataset.
I don't think it would be possible as Project level roles are inherited automatically. Making new project may be helpful.
I had created an App work-space, there is dashboard and a dataset inside.
If I add in some members inside, is there anyway that Do Not allow users to modify my dashboard while they still can use the dataset to build their own dashboard ?
You can share the dashboard and limit the user for read or so re-share:
Who has access to a dashboard or report you shared?
However one of the limitations of the datasets is that "No one can see or download the dataset."
Hope this can answer to your question. If not tell me please!