User Access/Security Overview
- 2 Minutes to read
- Print
- DarkLight
- PDF
User Access/Security Overview
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The table below provides high-level information on all the types of user security / access available, what the purpose of each is, and additional information.
Security/Access Type | Purpose | Additional Information |
User (Individual) Security/Access | There are two types of users you can set up:
| |
User Group Security/Access | Set up User Groups so that you can place multiple users into a group with the same security privileges. | |
Navigation Role | Navigation roles allow users to access specific navigation paths, which provides them with access to certain application pages and associated functionality. For example, a regular planning user might have Budget Input and Reporting access permissions, while a Planning Administrator might have access to Maintenance pages, Budget Input, and Reporting. | Required to be created prior to adding users. Applies to entire application. |
Navigation Access | Goes hand-in-hand with Navigation Role. Select applications pages you want the navigation role defined to access. You'll assign users/user groups with a navigation role with defined navigation access. | Required to be defined. Applies to entire application. |
Dimension Security | Secure dimension members (financial segments) based on reporting area. You must first configure your dimension security before you can add and configure users. | Once dimension security is configured, you can assign users to selected reporting areas and dimensions. |
Approval Role | Specifies users' actions based on their responsibilities during the planning process. It assigns specific privileges to ensure that only authorized users can perform certain tasks. | Required to create before the entity permission for the Planning module. |
Approval Role Setup (Approval Access) | Configures user permissions for specific entities based on their assigned approval role. | Required for the Planning module. |
Scenario Access | Users must have access to the scenarios to enter template data for a scenarios budget entity, for example. | Required for the Planning module. |
Data Integration Security | Provide users with access to Data Load processes, select to allow users to edit or view processes. | |
Report Access | Provide users and user groups with access to generated reports. | |
Workforce Reporting | Provide users with access to Workforce Reporting. | Applicable to Workforce Planning. |
Consolidation Security | Assign centralized and decentralized security, which means you can provide a user access to a company and all related members or to a specific member or members within the hierarchy. | Applicable to Consolidation |
Add-In Security | Provide users with access to Planful Add-Ins such as Offline Planning. | Using these add-ins is optional. |
Was this article helpful?