Unable to hide edit button for certain group of users.

[anandcognos]

Hello

I want to hide edit button for certain group of users, who are not admins. I followed steps mentioned in knowledgecenter https://www.ibm.com/support/knowledgecenter/SSFUEU_8.0.0/op_grc_admin/t_com_restrict_end_usr_from_studios_but_run_op_rpts.html

, but still edit button is shown for all users. I want to know if there is anyway to hide edit button for certain group of users at all ? I have attached two images :

1. user1.jpg : edit button for admins. We want edit button for admins.
2.user2.jpg : edit button for business users, we don't want edit button for them.

Please let me know if there is any way to hide edit button for business users, and if anything else is required from my side. I will appreciate your help.

Thanks and regards,
Anand

[saikumar_naani]

Probably, share/ give access the views for those who don't have to see the edit option and normal report for those who want to edit the reports.

[SGUNNA]

We had an issue in the prod environment where users can edit the report.
Here is the issue: 1) Click on the three dots next to the report, then the popup window you can see the edit report option for the users.
When users have Query studio access, then this problem occurs.

Solution: Logon as Administrator > Manage People > Capabilities (Search for Report Studio) Report studio properties - Access > Remove "Everyone.
Now users will have Query studio access and Repoirt studio reports can't edit.

[MFGF]

We had an issue in the prod environment where users can edit the report.
Here is the issue: 1) Click on the three dots next to the report, then the popup window you can see the edit report option for the users.
When users have Query studio access, then this problem occurs.

Solution: Logon as Administrator > Manage People > Capabilities (Search for Report Studio) Report studio properties - Access > Remove "Everyone.
Now users will have Query studio access and Repoirt studio reports can't edit.

Thanks for posting - tips like this are really helpful.

One of the things I always recommend when setting up security is that the memberships of all of the groups and roles are examined, removing the 'Everyone" group wherever it exists as a member and replacing with the appropriate group(s)/roles(s). Then do the same for each of the capabilities. This way, there are no nasty surprises, plus it also means you are more likely to be safe if/when IBM comes in to do a Software License Review (basically an audit to make sure you are keeping within your purchased licensed user count and not granting capabilities to a user beyond their license).

Cheers!

MF.

[sdf]

role based customization can also be used to remove capabilities for users.


sdf