Dynamic Themes - admin and UX challenges | XM Community
Skip to main content
Michael_Cooksey
Administrator
1 month ago
Question

Dynamic Themes - admin and UX challenges

M
We are a large organization with many divisions and many admins. Somehow we've ended up with dynamic themes with the same names as our static themes and they are available in all of our divisions! There is no way to make a dynamic theme available only to a single division on creation. Instead, the admin must edit EACH division where you don't want the theme available and deselect the theme you just made. This is a ridiculously labor intensive task for an admin. Additionally, with many admins in our org, the possibility of themes being created and published in the wrong division is multiplied. Furthermore, dynamic themes are given precedence over static themes in the look and feel selection list, when they should be listed last. There has got to be a better way to manage dynamic themes.

2 replies

K
Level 5 ●●●●●
Forum|alt.badge.img+19
  • Kate
  • Level 5 ●●●●●
  • 543 replies
  • January 8, 2020
You can't manage the way the look and feel options present itself to survey creators. Are you trying to institute a standard across divisions? Maybe you could create a standard look and feel on a project for each division, and host the blank project in the Library. Share it with only the right divisions. A bit more work on the part of the survey creator to locate the right survey. Either way I suspect that the dynamic theme was made automatically for you when Qualtrics made the switch. You could at least reach out to support or your client success rep and request they change the name.
M
1 person likes this
  • M
    Melinda
K
Forum|alt.badge.img+1
  • K_Essex
  • 2 replies
  • March 26, 2025
Melinda wrote:

We are a large organization with many divisions and many admins. Somehow we've ended up with dynamic themes with the same names as our static themes and they are available in all of our divisions! There is no way to make a dynamic theme available only to a single division on creation. Instead, the admin must edit EACH division where you don't want the theme available and deselect the theme you just made. This is a ridiculously labor intensive task for an admin. Additionally, with many admins in our org, the possibility of themes being created and published in the wrong division is multiplied. Furthermore, dynamic themes are given precedence over static themes in the look and feel selection list, when they should be listed last. There has got to be a better way to manage dynamic themes.

I’m not sure why this post has been marked as solved - as the same issue still persists; that a theme is available to all divisions by default when you create it.

Leave a Reply


Terms & Conditions