Why did you not create a separate group for analysis workspace (or public beta) access? You seem to have added it to the 'advanced reports' customization section for existing or new groups. However, because of issues with report builder Adobe Engineering has told us we must give everyone 'all report access' until engineering fixes a couple of bugs. See the attached images that show our report builder menu with and without all report access. So by not creating a group but by adding it to something that will fall into all report access by default you have given all my users access to analysis workspace and we don't want all of them using beta features.
What can be done about this?
Solved! Go to Solution.
Views
Replies
Total Likes
What a strange confluence of events. First, I'm very sorry that we inadvertently gave all of your users access to the tool. I agree that it seems a bit inconsistent that we have Ad Hoc Analysis and Report Builder as groups, but Analysis Workspace is a checkbox. There is probably not much that we can do about that in the very short term, but we are actively working toward a streamlined permissions model that will allow you to grant/restrict access much more easily across dimensions, metrics, and tools.
It sounds like the real problem here is the existence of bugs which require you to grant All Report Access to users who normally would not have it. If you don't mind supplying the support ticket numbers associated with those bugs I'm happy to follow up on them to see whether they will be taken care of soon.
Thanks,
Ben
Views
Replies
Total Likes
What a strange confluence of events. First, I'm very sorry that we inadvertently gave all of your users access to the tool. I agree that it seems a bit inconsistent that we have Ad Hoc Analysis and Report Builder as groups, but Analysis Workspace is a checkbox. There is probably not much that we can do about that in the very short term, but we are actively working toward a streamlined permissions model that will allow you to grant/restrict access much more easily across dimensions, metrics, and tools.
It sounds like the real problem here is the existence of bugs which require you to grant All Report Access to users who normally would not have it. If you don't mind supplying the support ticket numbers associated with those bugs I'm happy to follow up on them to see whether they will be taken care of soon.
Thanks,
Ben
Views
Replies
Total Likes
140619-000173 is one of them. It got fixed in 5.0 (and the ticket closed) and then re-broken in 5.1.23.0 but I noticed the 5.2.10 has re-fixed it.
So I can probably take away all report access from my users until someone finds something else that is missing.
But it still would have been better to have a special group for beta rather than a buried check which btw the documentation doesn’t tell you about. And I will assume that 90% or more of Analytics customers run with all report access and don’t have specialized groups for their users.
Views
Replies
Total Likes
The data we see on permissions is a little different than that, but we will be updating permissions in the near future to make all of this easier and more manageable. As I mentioned in my last note, I agree that this particular permission was handled a bit inconsistently.
Either way, I'm glad to hear that the more immediate problem should be resolved!
Views
Replies
Total Likes
so anyone interested. I created a new group called 'analysis workspace' (admin -> user management -> groups)
the only check box I did was in 'advanced reporting' (click customize)
check the 'analysis workspace' check box
move any of your users you want to have access to analysis workspace to having this group
save it.
Make sure they don't have 'all report access'
I verified this will give an 'access denied' message to those not in the 'analysis workspace' group
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies