Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

What are the minimum required permission to see dashboards of a project.

jeroen_wilmes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 16, 2025

I have created dashboard to present progress on a project to stakeholders.

Some stakeholders are customers and we gave them access to the project with a role 'customer" having permission to browse projects, but no Issue permissions.

 

Is that sufficient to give them the view of the dashboard?

2 answers

2 accepted

4 votes
Answer accepted
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 16, 2025

Hi @jeroen_wilmes 

As @Trudy Claspill mentions, is correct.

A Jira dashboard can only be seen by licensed users. Just customers (JSM terminology) can see the help center (portal) to raise requests, that's all then can see.

For issue details on any type of project a license is required.

Or you can look at 3rd party apps that have the option to provide details to non-licensed users.

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 16, 2025

Hi @jeroen_wilmes 

As you mentioned to @Trudy Claspill 

Are the users having a Jira license, yes, if being granted the right permissions they can now see issue information.

If you have created a dashboard and this dashboard uses Jira filters, make sure that the filters are visible for these users.

If the issues are from multiple projects, make sure all permission schemes have been applied with these settings or make use of the same permission scheme.

jeroen_wilmes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 16, 2025

@Marc - Devoteam  and @Trudy Claspill . Thanks for your help.

I gave the project access to the used filters, so that should be OK.

 

Good suggestion to double check if I have issues from other projects, because then I need to make sure the permission are OK as well for those projects.

 

1 vote
Answer accepted
Trudy Claspill
Community Champion
April 16, 2025

Hello @jeroen_wilmes 

What type of project is being referenced? Get that information from the Type column on the View All Projects page under the Projects menu.

I ask because you said you gave the user the role of "customer". "Customers" is a term used with Jira Service Management projects, generally, and users that are customers are not fully licensed for Jira. They generally only have access to Jira information through the Customer Portal, and they would not be able to see dashboards there.

But if you are using a Software project and created a custom Project Role named "customer", that would take the conversation down a different path.

jeroen_wilmes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 16, 2025

It is your second option. A software project. Customers are licensed on our Jira instance, we give them access to the required projects with the Project role named "customer" (from the dropdown menu under project roles).

 

The role "customer" has no permission under the header "issue permission" (except for adding/editing and deleting own comments.

They do have browse permissions.

Should that work?

Trudy Claspill
Community Champion
April 16, 2025

The "customer" Role will need the Browse Projects permissions in all projects that are referenced by the Dashboard either directly or indirectly.

Which means that role will have to be used in all the relevant projects and the users added to that role in all relevant projects.

As @Marc - Devoteam mentioned, if any of the gadgets are using Filters, then those filters need to be Shared with the related Projects; either for all Roles in the project or at least the "customer" role. That sharing is set up in the Filter Details, under Permissions, not by using the Share button in the upper right corner.

Screenshot 2025-04-16 at 9.28.42 AM.png

 

And you need to share the dashboard itself.

Screenshot 2025-04-16 at 9.31.07 AM.png

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events