Permissions not working - Dashboard

[David Willoughby]

All,

I know this has been asked a hundred times (I've read all the posts) however my dashboard will not share. By that I mean I have added my entire org as editors and as viewers. All filters are set to My Org, and when anyone accesses it they get 'Dashboard is blank or you dont have permission to view' The only thing I can think of is that the dashboards are sharing created reports in the project, but reports don't have permissions, and more so my reports are using the report filters not the saved filters that are already shared anyway.

I've cut back some of the permissions and changes to more real life levels but still no one can access. 

Project Permissions (group specific IT-Support Ops TeamLeads) 

[Dexter de Vera · Accepted solution]

Hi @David Willoughby ,

To make you dashboard visible is the user is added in group/role indicated in your project permission , filter and dashboard? Also do you have any security  scheme in your project?

[David Willoughby]

I removed the Security Scheme. As for the group/role for testing purposes, I used a test account and gave it progressively more roles, only project admin worked. I am using the report view widget in the dashboard but reports don't have permissions, and all the filters that the reports use are set to 'All Org'

[Dexter de Vera]

You said User is in group added in browse permission in all the project included in your filter. And your filter use im dashboard is set org as viewers. How about the dashboard? Have you already set the viewiers? You need to set the viewers for both dashboard and filter. Can you show us some screenshot for this 3 (project permission, filter viewer and dashboard viewer).

you can share the dashboard by clicking (...) -> rename or share

If still does not work, you may raise a support ticket to Atlassian. - https://support.atlassian.com/contact/#/ 

[David Willoughby]

Yes I have, however I think it is working now. I added group permissions for the project Browse all project to include servicedesk-users and that resolved it. I think it was a mix of permissions being mixed on my end.

[Dexter de Vera]

great! thanks.