Unable to approve access request to Power BI Dashboard.

[pparekh]

I have created a dashboard for my company where tenants can request access which I usually approve. I have couple of users for whichc the "Approve" button is being greyed out. I found that users with type "Pending invitation" are the ones that I am not able to give access. I have already sent them invite but not sure how to approve them.

 

[Chith_123]

Hi, hope you are well, can you please let me know the status of this, if it is resolved can you please let me know of how?

[nenadpekec]

Please check if users with "Pending invitation" have tried to open the report and if they have completed MFA (Multi-Factor Authentication) setup for their account.

[powerBI-novice1]

Hi Facing same issue! Its greyed out for some people. I am unable to give them direct access. Even if I try, it take me to the pending status. Any help is appreciated

[skygold16]

I think you do not have member or higher level of access to be able to approve the user access request. You are receiving an approval email because you are in the data set owner or in a workspace conact list. 

Check with the workspace admin team and they should be able to guide. 

[pparekh]

Hi @skygold16 , I am the admin of workspace as well as the owner of dataset.

[KatieC]

Hi, did you ever figure this out? I'm having a similar issue where the approve/decline buttons are grayed out.

[Chris0404]

I have the same issue.

It is my dataset and my report. and I can't approve nor decline.

[skygold164]

Hi, did you check if someone else from the workspace admin has already approved the request?

[KatieC]

Yes, no one else has approved from what I can tell. I've refreshed and they're still there hours later. Neither of the pending people are in the list of people with existing access.

[ajerovich]

Did you try rejecting the request and giving direct access to the report (read-only)?

[KatieC]

Hi, as you can see in the screenshot, both the approve and decline buttons are grayed out and cannot be clicked. At this point, someone else on the team has resolved the issue for me. I haven't seen this issue again since then, so I'm hoping it was a bug that has since been sorted out.