Post

2 followers Follow
0
Avatar

Dashboard Widget shows "Access Restricted" for some data

Hi - I hope someone can help me.

I create a report with multiple tabs and then a dashboard, which works quite nicely and everything is displayedin the Dashboard itself.

But when I share the Dashboard as a widget, some of the charts are restricted ("You do not have permission to view this chart") although I am the owner of the reports and dashboard.

Can it be related to the type of field that is used to calculate the data? And how do I get the fields to be displayed in a widget?

Thank you!

Anneta Mitsopoulou Answered

Please sign in to leave a comment.

3 comments

0
Avatar

Hi Anneta,

Thank you for submitting your question! If you have any financial fields displayed in your dashboard the system will restrict them via widget. Since widget can be shared with public and we cannot protect the information - due to the security the access is restricted. Of course like with any feature.. we have customers with very strict sharing policy who love this functionality, however we have customers who would love to be able to share any information with some non-Clarizen users. We already have a request open for our Product team to add an ability for the admin to decide where the organization would like to share this information or not. If you would like to - I can definitely add your name to the requesters list. 

Hope this helps.

Bea Genthner 0 votes
Comment actions Permalink
0
Avatar

Hi Bea,

Ok, got it! We are fine for now, so no need to add me as requester.

Thank you very much for the explanation, it helped a lot!

Anneta Mitsopoulou 0 votes
Comment actions Permalink
1
Avatar

This post is old, but I was having the same issue.  But we also want to limit what we shared still, but expose a Total approved budget amount only.  So I just created a new custom field, calculated it against that value, and then changed the report to reference the view only version of the amount.   That way, all the other financials are still locked down.

Andy Johnston (AU) 1 vote
Comment actions Permalink