Vote to Endorse an Easier Way to View Survey Collaborators! Follow-up from Meeting Today | XM Community
Skip to main content

Vote to Endorse an Easier Way to View Survey Collaborators! Follow-up from Meeting Today

  • October 16, 2024
  • 4 replies
  • 75 views

AHammell
Level 2 ●●
Forum|alt.badge.img+11

Hi all,

At the end of the higher education meeting today, we discuss some product feature requests, and I brought up a feature request I put in regarding easier ways to access survey collaboration information.
 

I found the request if you would like to upvote it! (Idea ID: EV-3387)

Overview:  The ability to export a list of all users a survey has been collaborated with, including collaborator’s specific permissions.

This was a description of one of our research center’s use cases, which I added to the product idea: “[Research Center] provides survey and experimental support to researchers across 32 departments. We consult and assist with development of surveys used in graduate student, staff, and faculty research projects. We also are the primary contacts for survey development for several large research centers that run dozens of survey instruments at a time. As a result, we own or have access to around 1000 surveys. When graduate students or research staff in labs we support transfer positions or leave the institution, we often need to remove or modify their access to surveys we own. We have also been asked to audit files for access in situations where there is research conflict or potential research misconduct. Right now, the process to audit and remove permissions requires manually sorting through surveys, determining the owner(s), and having those staff members individually click through each survey instrument to remove or evaluate permissions. We keep reports currently for large research projects about which students have which permissions, but those require manual updating each time a change is made to keep them in sync - this is an arduous task. Having the ability to pull permission reports for all surveys we own by specific collaborator would improve our ability to audit access to projects and to act quickly and thoroughly in situations where swift action to remove or replace permissions is necessary. It would also mirror other security procedures where routine audits of collaborator access are done to monitor and remove access when no longer needed.”

 

Best wishes,

Abbey

 



 

4 replies

Forum|alt.badge.img+8
  • Level 2 ●●
  • October 16, 2024

Hey, to your overview. This is technically possible so I wonder if the request should be “An easier way” in case they just come back and say you can? Here’s how it’s done… and it’s ridiculously complex and time consuming, requiring both the API and a script (I used python). With several API calls, you can get a list of surveys and owners. Then with more API calls, you can get a list of each survey’s collaborators - but this requires assigning an API token to every user at the institution, which is another API call, and then looping through  Then we can have separate lists - surveys, owners, collaborators, and have to cross them together.

Overall, it’s essentially not doable for most brand admins. Downloading an easy list of surveys, owners, collaborators, and permissions would be ideal - thanks for making this!!!


AHammell
Level 2 ●●
Forum|alt.badge.img+11
  • Author
  • Level 2 ●●
  • October 16, 2024

Thanks @riceball ! Yes, the goal would be to have this done without the use of the API. The API would be considerably time consuming for an institution as big as ours. However, I appreciate you pointing out this possibility!


Forum|alt.badge.img+8
  • Level 2 ●●
  • October 16, 2024

@AHammell  Oh yeah, it’s totally unfeasible. My main point was - Qualtrics might come back and say “This already exists via 6 different several hour each API calls”, so we might really have to stress to Qualtrics that it’s, well, impossible for basically anyone and we need a different way. I’m completely with you.


MichaelC
Administrator
Forum|alt.badge.img+41
  • Administrator
  • October 17, 2024

Hello, everyone! I love seeing this idea advocacy in action -- that is what the XM Community is here for! I wanted to let you know I have shared this thread/conversation with the Product leader so they are aware. Hope this helps!