Give Admins more granular control over ViewerAnalytics permission bundle

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

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.

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 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.

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

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. 😀

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.

PLEASE make this possible, we want to test things as admins (in our live environment) before giving access to other users. Recent example: Co-Pilot. We can restrict access to our full users but we don’t have the same option for our Viewer Analytics so they just get things by default. 

Joining in here. Viewer+ users are typically basic Gainsight users; giving them access to unused modules or modules they don’t need just makes it harder for them to navigate the platform.