02-17-2012 12:38 AM
I have published an Information Map in SAS Web Report Studio.
I want the users to be able to filter the report (using the Filter and Rank option, I don't believe there is another way), but I don't want them to be able to see the Edit tab.
Ultimately, I don't want them to be able to edit the report that I have setup. I don't mind if they save it elsewhere though (for now).
I followed the instructions in this link:
To remove the Edit tab, and that worked, but only when I had the Web Report Studio: Report Viewing role applied. As a consequence the user was not able to use the Filter and Rank option.
I changed the role of the group that a test user was in to Web Report Studio: Report Creation with the hope of allowing the user to filter the data. This was successful, but the Edit tab returned.
So, can I allow the user to use the Filter and Rank option but have the Edit tab hidden from them? Or am I going to have to think about editing the roles such that they cannot save reports (I'm not even sure if this solution would work)?
02-17-2012 08:10 AM
Give your users the Basic Edit capability. That should enable the context menu that pops up when you right-click on an object. This menu includes the Filter & Rank option.
You also might want to take a look at this sample: http://support.sas.com/kb/42/890.html
03-21-2012 06:26 PM
Thanks BIC_USER_3, after a lot of chasing up I finally got IT to add basic edit to the role (created a new role based on Web Report Studio: Report Viewing, and then added Basic Edit). It's a shame that even though I'm a SAS Administrator, IT had to use the sasadm account, I cannot edit Roles or create new ones relating to Web Report Studio.
The user was able to apply Filter and Rank whilst the Edit tab was hidden, however, they were still able to Save the report such that everyone would see their filters. Not ideal.
I haven't attempted to find out where I can set permissions for who can save the reports yet, I'll get to that shortly.
Message was edited by: John Tay Yesterday I tried Access Control Templates, and that did the trick. I forgot about using ACTs, so what I will do is delete the role I created, assign the users one of the existing roles and leave my ACT which denys write member metadata.