Apply security for a scenario
You can restrict a user from accessing the scenario plan data. Based on the data security rules and the specified scenario security, you can determine a user's access to the cycles, cycle periods, modules, scenarios, items, and location hierarchy nodes.
To access the plan data for a scenario:
- The user's ID or the primary role must be specified in the scenario.
- The user must have the required data security permissions for the selected cycle period and module.
Based on the security settings, the user's access to data is restricted in these areas:
| Area | Restriction |
|---|---|
| Worksheets | The user's access to data context fields and toolbars of the worksheet is restricted. |
| Scenario Details (module) | The user's access to dynamic options, for a module, available on the menu bar is restricted. Access to the additional details of a scenario is also restricted. |
| Cycle Period Details | The user's access to linked scenarios is
restricted.
For example, user "jdoe" can access the Demand-Baseline scenario. "jdoe" can view the Demand-Baseline scenario and the linked Finance-Baseline and Supply-Baseline scenario in the scenario list for each cycle period. However, the upside demand is not listed and the user can only view the additional details of the Demand-Baseline scenario. |
| Import, Export, and Execute macros | Users can execute these macros only for scenarios to which the access is provided. |
| Mapping | For mapping, the user must have the required
permission to execute the macros.
Note: The user only requires access to the Destination scenario
as specified in the mapping; access to the Source scenario is not required.
|
| Copy Scenario | Users can only copy a scenario, and the related permissions, for which access is provided. |
| Audit Log, Notes, Events, and Scenario History | Based on the data security settings, the user's access to the search option, for audit log, events, notes, and scenario history is restricted. |