Skip to main content

Hello everyone, 

 

We’re managing permissions for IFS Business Reporter and we’re starting to build more and more reports within the tool. As we’re training up more report designers, we’re running into a bottleneck around permissions management since each report (and each report unpublish / publish event) has to be managed separately. 

 

Thinking about how to solve this, if the report structure within Business Reporter could be an object to manage permissions, this would permit folders to be assigned to a permission set and the report projections underneath them would be inherited by the “folder” level security object. 

 

It seems to be inline with the direction laid out in the technical documentation where a practice recommended is to build a permission set for a given department and assign permissions. The folder structure we’ve built out has naturally fallen along organizational lines and it would simplify the management of report permissions. 

 

It could also remove the tedium of restoring permissions after unpublishing and republishing

Hi 

Based on the statement; permit folders to be assigned to a permission set and the report projections underneath them would be inherited by the “folder” level security object. 

Based on my opinion this can be concerning as the Report Designer has the access to all Information Sources and can publish any report design to any folder. 

Thank You
Best Regards
Shenali



 


I’m also interested in this as a solution. I’d like designers to be able to publish to and collaborate in a ‘report designer’ folder, and then move completed reports into another folder where end users can run the reports.


Reply