跳至主要內容
Adaptive Planning
上次更新時間 :2023-06-23
Concept: Permission Sets

Concept: Permission Sets

You assign permission sets to users to give them access to areas of Adaptive Planning. A permission set includes permissions that define what a user can see and do in Adaptive Planning. Example: An Administrative permission set generally has all or most of the available permissions. A budgeter might only need to access sheets and nothing else. That permission set may only contain a few permissions.
See Concept: Roles and Permissions and Reference: Available Permissions.
You can assign 1 permission set to several users, but each user can have only 1 permission set.
As an administrator, you can:
  • Create as many permission sets as you need.
  • Change existing permission sets.
  • Assign permission sets to users.
Every instance comes with predefined permission sets, depending on the license. Review the permission sets and update their permissions as needed, or create additional permission sets.

Permissions Versus Data Access

Permissions control the actions users can take, and the areas in Adaptive Planning users can see or access. This includes certain fields, sections, and services. Example: A user without the Admin Access permission can't get to the Administration pages.
Data access controls the data users can view. Example: you can select the levels and versions that users see and don't see. Manage data access with level, version, account, and sheet settings. If your instance uses access rules, the rules add a specific layer of control.
Level owners are set up in the user profile or in Administration > Associations. Version access is set up when you create or edit versions. Access rules are set up in Admin > Access Rules if you have access rules enabled.
See:

Permissions Templates

A permissions template preselects a set of permissions for you. The permissions templates are different for each instance. They generally include View Only and Full Seat. They can also include Contributor, Implementor, and Power User.
To see the permissions included in each template, create a new permission set and click the template. Remove and add permissions as you choose. See Reference: Available Permissions.
Permission Template
Description
View Only Permissions
Use the View Only template for users who should only have view access to data. It's also a good place to start for creating a limited permission set or for building a permission set from the beginning.
Contributor Permissions
Use the Contributor template for users who must enter and change data. The Contributor template doesn't include permissions suited for management, administrative, and modeling. Besides a few other advanced permissions, the Contributor template doesn't include:
  • Integration Operator
  • Model Management Access
  • Admin Access
Implementor Permissions
Use the Implementor template for users who manage the model for a limited time. Examples include:
  • Workday SAML SSO users who don't have specific permissions yet within Adaptive Planning.
  • Third-party implementers.
Permissions that aren’t selected in the Implementor template:
  • Integration Developer: allows the user to create data connectors using APIs.
  • Export Capabilities: allows the user to export.
  • Approve Levels: allows the user to approve levels within Workflow.
  • Process Tracker: allows the user to access and manage the Process Tracker.
Full Seat and Power User Permissions
The Full Seat and Power User templates have almost all the available permissions. Use these templates for administrative and management users. Permissions that aren't selected in the Full Seat and Power User template:
  • Integration Developer: allows the user to create data connectors using APIs.
  • Time: allows the user to update the calendar setup.
  • Structure Import: allows the user to import model structures, such as levels, accounts, and so on.