Securing Scenarios
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Securing Scenarios

  • Dark
    Light
  • PDF

Article summary

Why Secure Scenarios?

To provide users with access to specific scenarios.

When to Secure Scenarios?

When you want users to have access to specific data only.

Securing Scenarios

How to Setup Scenario Security by Scenario for Users?  

To setup scenario security by scenario for users, complete the following steps:

  1. Access the Scenario List page by navigating to Maintenance > Administration > Scenario Setup.
  2. Select a scenario and click the three vertical dots.
  3. Select User Access under Other Actions.
  4. Select the checkbox for the user(s) you want to give access to the selected scenario.
  5. Click Save to complete the setup.

Scenario access can also be configured through User & Role Management by the user. To learn more about setting up scenario security by user, click here.

How to Set Up Scenario Security for Reporting Purposes?

To apply scenario security (defined on the Scenario Access page) to report security so that each user has access to view specific scenarios only in the Reporting module, complete the following steps:

  1. Access the Dimension Security Configuration page by navigating to Maintenance > Report Administration > Dimension Security.
  2. Click the Dimension Security Configuration tab.
  3. Select the Copy Scenario Security to Report Security checkbox.
  4. Click Save.
  5. Access the Scenario Access page by navigating to Maintenance > Administration > User & Role Management.
  6. Select a user and click the Security icon next to the user name.
  7. Click Scenario Access.
  8. Select the scenarios you want the user to have access to. The user will only have access to the selected scenarios and members for Reporting purposes. For example, when a user runs a report that includes a scenario the user doesn’t have access to, that scenario will not be available in the report. Similarly, if a user has permission to view a scenario when a report was created and later the permissions are revoked, the report is run for only those scenarios for which the user currently has permissions for. Data will not be displayed for the scenarios for which permissions are revoked.
  9. Click Save.

Point of View Example

Within the Reporting module, if the Copy Scenario Security to Report Security checkbox is selected, scenarios for Financial and Sales are affected. For example, on the Point of View page (accessed by navigating to Maintenance > Reports > Point of View ), only the scenarios for which a user has permission are displayed and selectable for the Scenario Reporting Area.

Dynamic Report Example

Lets say a scenario is mapped to Budget. Assuming the Copy Scenario Security to Report Security checkbox is selected on the Dimension Security Configuration page when a user creates a report, the available value (Budget) is displayed as a Mapped Member. Actual is also displayed because the Actual scenario is not subject to this type of security.

Note:
If a user does not have permissions for a scenario member used in Reporting on the page axis, the report will run against the Default scenario. If no permissions exist for the Scenario dimension, no data will be displayed in the report.

When Scenario Access is modified and saved, the reporting cube is automatically processed to reflect the latest security updates.


Was this article helpful?