Hierarchy permission? | XM Community
Skip to main content

Hierarchy permission?

  • September 12, 2022
  • 6 replies
  • 540 views

JoycaV
QPN Level 4 ●●●●
Forum|alt.badge.img+27
  • QPN Level 4 ●●●●
  • 236 replies

Hi,
I see the following message on my EX dashboard:
image.png
I am a brand admin, and I am assigned to a Role without any restrictions on this dashboard:
image.png
What am I still missing to be able to solve the error?
I am not a respondent on this project, and I am not in the hierarchy.

6 replies

SimQualtrics
QPN Level 2 ●●
Forum|alt.badge.img+11
  • QPN Level 2 ●●
  • 23 replies
  • September 29, 2022

image.pngif you restrict the data by including a variable, for example city as embedded data in the users' files..


Forum|alt.badge.img
  • 3 replies
  • December 24, 2022

Hi JoycaV, Have you been able to solve the problem? I am experiencing the same issue.


JoycaV
QPN Level 4 ●●●●
Forum|alt.badge.img+27
  • Author
  • QPN Level 4 ●●●●
  • 236 replies
  • December 26, 2022

https://community.qualtrics.com/XMcommunity/discussion/comment/53443#Comment_53443Hai1904, yes. It was because on the dashboard, we had multiple datasources. The hierarchies of the multiple projects had to be mapped to eachther, AND in the second/third/etc survey, we need to regularly push the button "update responses with current metadata". This updates some auto-genrated fields labeled "timestamp of last medatada update", "org hierarcy direct report units". That "org hierarchy direct report units" you will notice on your surveys that they appear multiple times within the field list. This is linked to the mapped hierarchies, each appearance of this field reflects the org hierarchy id's of those linked hierarchies. As long as those fields are empty (if you did not refresh the metadata), the dashboard is unable to check for those responses who is allowed to see them in the linked hierarchy.
Because the dashboard is built on the "first" survey and has authorisations based on the hierarchy of the "first" survey only, so the hierarchies of the "second/third" survey etc need the mapping to the "first" survey's hierarchy for the roles to be evaluated.

I do hope the explanation makes sense, because it's quite complicated and took us quite some time to figure out what the actual problem was.


Forum|alt.badge.img
  • 3 replies
  • December 27, 2022

Hi JoycaV, thank you very much for your explanation. It is really good to know the problem you experienced, however, in my case, I only have one data source.


Forum|alt.badge.img
  • 3 replies
  • December 27, 2022

Hi JoycaV, the problem has been solved when I was granted Admin right for the instance I was working on, before I am a standard Qualtrics user.


Forum|alt.badge.img+1
  • 3 replies
  • September 27, 2024
JoycaV wrote:

https://community.qualtrics.com/XMcommunity/discussion/comment/53443#Comment_53443Hai1904, yes. It was because on the dashboard, we had multiple datasources. The hierarchies of the multiple projects had to be mapped to eachther, AND in the second/third/etc survey, we need to regularly push the button "update responses with current metadata". This updates some auto-genrated fields labeled "timestamp of last medatada update", "org hierarcy direct report units". That "org hierarchy direct report units" you will notice on your surveys that they appear multiple times within the field list. This is linked to the mapped hierarchies, each appearance of this field reflects the org hierarchy id's of those linked hierarchies. As long as those fields are empty (if you did not refresh the metadata), the dashboard is unable to check for those responses who is allowed to see them in the linked hierarchy.
Because the dashboard is built on the "first" survey and has authorisations based on the hierarchy of the "first" survey only, so the hierarchies of the "second/third" survey etc need the mapping to the "first" survey's hierarchy for the roles to be evaluated.

I do hope the explanation makes sense, because it's quite complicated and took us quite some time to figure out what the actual problem was.

This was very helpful. Thank you!


Leave a Reply