Securing Custom Reports

A Custom Reports folder is available in the Public folder. Custom Reports must be used to store any custom reports that you create, because the core security permissions are also applied to this folder.

Securing reports in the Self Service Portal

When a system administrator enables reports for the Self Service Portal, these security settings in the Admin Portal also applies in the SSP.

Setting Description
Report visibility By default, the Reports menu in the SSP is available only to Infor Admins and System Admins. An administrator can enable reports for other security groups.

An individual report is shown only when Render in SSP is selected for that report and the user’s security group has access to it. A report can be shown in the SSP even when the security group does not have access to the report’s parent folder, provided the user has access to the individual report and Render in SSP is selected.

Report data Reports follow the employee and team security model when they are run in the SSP. Employees see only their own data. Supervisors see data for themselves and their own teams.
Proxy When a user acts as a proxy, only reports that have Hide when Proxy cleared are shown, and a report returns only the data that the proxied user is entitled to see.
Cognos privileges A user must have the necessary Cognos privileges to run reports in the SSP:
  • The user's security group must have access to the specific report, regardless of the permissions assigned to their parent folder.
  • The user's role assigned in Mingle or Infor OS must be WFMIR-Consumer at the minimum.
If the user does not have these privileges, a message is displayed stating that the user does not have the necessary privileges to run Cognos reports. Check with the System Administrator to obtain these privileges.