Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Controlling access to reports

Updated on July 1, 2021

Ensure that only senior executives can run reports in the HRApp application, because these reports include confidential information related to hiring and compensation.

Before you begin:

Assume that these steps have already been done:

  1. An access group is defined for senior executives (HRApp:SeniorExec).
  2. A role is defined for running reports in this application (HRApp:RunAllReports).
  3. The HRApp:RunAllReports role has been assigned to the HRApp:SeniorExec access group.
Do these steps to ensure that only operators with the HRApp:SeniorExec access group have permission to run all reports in the HRApp application.
  1. In Dev Studio, go to the Tools tab of the Access Manager landing page by clicking Configure Org & SecurityAccess ManagerTools.
  2. In the Access group field, enter HRApp:SeniorExec. The table lists common tools that can be conditionally available in all applications and the roles that have access in the HRApp:SeniorExec access group.
  3. In the table, expand User & managerReports and find the value for Provide criteria on reports that is listed for the HRApp:RunAllReports role. Ensure that a green check mark is shown, which means that access is granted. You can change the value by clicking the icon.
  4. For access groups that should not be able to run reports, repeat the above steps, but ensure that the HRApp:RunAllReports role is not listed and that any other roles show a red X icon, which means that access is not granted. You can change the value by clicking the icon.
  • Previous topic Controlling access to sections, buttons, and other UI controls
  • Next topic Validating user input and preventing invalid values

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us