Disable request access feature.
We would like to disable or hide the end user option/ button/ window where they can request access to a dashboard on which they landed after opening a url from a dashboard which is not shared with them.
All our corporate reports are shared via dashboards via dynamic updated universal (A)AD groups.
There is no need for end users to request access via the default powerbi request access button. Yet they are able to do so on dashboards which they don't have access to. These requests are sent to the workspaceowner, which doesn't have a emailbox. Endusers are waiting for an repsonse, but adminitrators only see this request after explicitly opening the dashboard sharing window.
We need this option be disable too. Requesting access to a PBI report is not like just requesting access to a sharepoint site, but it is treated like that. When we reject a request we cannot even send a message with it why we reject it. All requests we want to be done via a powerapps form and flow into aad groups but the option to 'just' push a request access button based on the url of the PBI report is distorting the real to-be-used process for requesting proper access via an authorization flow.
Need 2 options, disable or route to an email box that is not the owner.
Pat Richardson commented
Our end users are waiting to no avail, please disable this asap!
it is a necessity for enterprise app to be controlled through custom process for AD group update. Lack of customise access request creates lots of end user frustration
Andreea Sandu (Engineer, Power BI) commented
In the new workspaces (preview ones), you can set a list of contacts for the workspace, whoch would be used for all email communication by power bi. so the access requests will be directed to those users/groups.
request for not only dashboards but reports
Just to expand on this idea..it would be great to be able to customize the "request access" feature -- customize who receives the request or send the requestor a message with more details on how to request access through appropriate channels.
This is useful for enterprise apps where AD groups are used to control access and new users need to be approved by someone within the business before being added to the AD group.