Organization Name

University of Maryland Baltimore

Description

We would like to extend security access to the reporting panes within the module, specifically the ability to delete items from the list. As an alternative, the ability to remove the cog to directly edit the list from the panel would work. Even if the cog is removed, a user with access who should be able to edit the list can access it from setup and maintenance. Since this list is for all users and not specific to the users view of the environment, it is inconvenient for the person in charge of curating the list of reports for easy access in the module.

Use Case and Business Need

Currently, if a manager was to create a list of reports to be shown in the reporting panel within a module, the list can be edited by anyone. This means that a manager or curator of this list could have to constantly add and delete reports from the list they have created when a user deletes reports from the list (and any user has this ability whether they can access reports or not). The benefit would be improved efficiency and increased user friendliness for the managers and for the users who need to run module specific reports. The reporting panel gives users the ability to easily access what they need without have to go to the catalog and navigate through the folders.

More details

It isn't possible to change the security access level of low level workers specifically in the work area report panels (i.e. the billing module navigate to the right side of the screen and click the report icon). It seems that no matter the level of access a user has, if they can access a module with the reporting pane then they can go to the cog within the panel and delete reports from the list (not the catalog). This is true whether the user can see the reports in the catalog or not. They can even remove reports from the list that they cannot actually see in the list within the panel. These are reports that they cannot see, view, or edit within the catalog. The inverse of adding the reports back does not have this problem. The user can only add reports that they have access to within the catalog.

This is a security issue that is not limited to the Billing module. It can be found in any module that has a reporting panel available. This includes but is not limited to: Project Management, AR Billing, Contract Revenue, Inventory Management, Product Development, Payments, Fixed Assets: Assets, Purchase Orders, and anywhere else the modular reporting panel exists. As long as a user has access to the module, they have the ability to delete reports from the curated list, even if they cannot view or add the reports.

Original Idea Number: aa07d8c06b