Skip to main content
New Idea

Give Admins more granular control over ViewerAnalytics permission bundle

Related products:CS Other Features
Ravinder Singh
kstim
revathimenon
nbelanger
Jagari Das
+2
  • Ravinder Singh
    Ravinder Singh
  • kstim
    kstim
  • revathimenon
    revathimenon
  • nbelanger
    nbelanger
  • Jagari Das
    Jagari Das
  • Cameron.Marijosius
    Cameron.Marijosius
  • SharonSalve

darkknight

Noticed today that Viewer Plus users by default have access to Adoption Explorer and Text Analytics, and there is no way for an admin to remove access to those two items.

 



This should be within an admins power to control. We aren’t currently using Text Analytics  (and have no imminent plans to) nor are we using Adoption Explorer so they’re just blank and useless.  

 

 

7 replies

darkknight
Forum|alt.badge.img+4
  • Author
  • Expert ⭐️
  • 1980 replies
  • January 18, 2024

...and makes it look like something just isn’t working correctly, when that is not the case.


Stuart
Forum|alt.badge.img+3
  • Helper ⭐️⭐️
  • 144 replies
  • January 18, 2024

also goes against the security principle of ‘least permissions to get the job done’.  If a viewer analytics license is provided for dashboard access, we shouldn’t have to grant access to other areas of the program by default, or switch up to a full license just for the sake of granular access control.


romihache
Forum|alt.badge.img+8
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 424 replies
  • January 18, 2024

I would like to add that this license should have a way to manage access to the OOTB Analytics.

A full license is an overkill as stated by Stuart ^ and considering the name itself is Analytics, shouldn’t it include also access (give the power to the admin to decide who/what) to all OOTB analytics of the platform like Surveys, Journey, NPS?
 


benwanlessmenlo
Forum|alt.badge.img+4
  • Contributor ⭐️⭐️⭐️⭐️⭐️
  • 115 replies
  • January 18, 2024

Yes, I agree,

It always seemed a little counter intuitive that the Viewer and Viewer+ licenses had preset permissions that could not be altered at all.

Use-Case: I don’t want to add more permissions, we need to remove some of the features that are not used.


alizee
Forum|alt.badge.img+11
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 655 replies
  • January 19, 2024
romihache wrote:

I would like to add that this license should have a way to manage access to the OOTB Analytics.

A full license is an overkill as stated by Stuart ^ and considering the name itself is Analytics, shouldn’t it include also access (give the power to the admin to decide who/what) to all OOTB analytics of the platform like Surveys, Journey, NPS?
 

YES. I thought had a post about the latter but yes yes and yes.


dayn.johnson
Forum|alt.badge.img+6
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 643 replies
  • January 19, 2024
Stuart wrote:

also goes against the security principle of ‘least permissions to get the job done’.  If a viewer analytics license is provided for dashboard access, we shouldn’t have to grant access to other areas of the program by default, or switch up to a full license just for the sake of granular access control.

 

100%!

I used to admin another system (not related) that had a VERY detailed user permission setup. IIRC, we were able to tweak the permissions each user level had, down to the exact items we wanted them to be able to view/edit.

This was awesome because some people who needed to be able to edit MOST things still didn’t need edit permissions on a lot of things. I can’t recall if we could adjust specific permissions for each individual user as needed, but that would be great as well. 😀


darkknight
Forum|alt.badge.img+4
  • Author
  • Expert ⭐️
  • 1980 replies
  • January 30, 2024

Support tells me that product and engineering has deemed this an enhancement request:

“Our team has added it to our future roadmap and will work on it accordingly to bring custom bundles even for viewer and viewer plus rather than default bundles.”

 I would argue this is at least in a gray area between bug and enhancement request, and I hope it can get prioritized quickly.  Just because this was an oversight on engineering’s party doesn’t mean it’s not a mistake.  And we shouldn’t have to wait for a full permission bundle overhaul to remedy an issue like this.

 

Things like this really put admins in a bind when we don’t have the necessary access control over these features.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings