Access Rules on Data Entry Columns in Modeled Sheets

This provides:

Improved ability to safeguard confidential information by enabling you to secure sensitive data within the same modeled sheet, eliminating the need for separate, duplicate sheets for different user groups. This helps to ensure compliance with data privacy standards.
Improved data management efficiency by consolidating workforce planning into 1 modeled sheet, reducing complexities associated with integrations and ensuring that data is up-to-date.
Streamlined workforce planning by enabling planners to collaborate on the same modeled sheet while only seeing data relevant to their roles, improving efficiency and data accuracy.
Enhanced system performance by reducing reliance on initial balance columns as workarounds for noninitial balance data.

On the

Access Rules

page of the

Administration

area, we add a new

Manage Sheet Columns

button on the toolbar that enables you to search for and make these column types available for use in access rules:

Check box.
Date.
Number.
Text.

When you secure at least 1 modeled sheet column, we now display an info icon next to the

Account

column header in these areas:

Access Rules
overview page.
Import and export files.

When you hover over this icon, we display a tooltip informing you that the columns are included in the

Account

section of access rules.

We update the access rules export file to include rules for modeled sheet data entry columns under the

Account

column structure.

When you secure modeled sheet columns and users don’t have access to those columns, we now hide the columns when they:

View the sheet.
Access the
Display Options
menu of the sheet and search for columns to filter or hide.

We now prevent users from editing secured modeled sheet columns when they have either:

Limited View permission in the access rule.
Full View without Edits permission in the access rule.

We recommend that you avoid creating critical validation rules that reference secured columns. If users don't have access to a required column, they can add new rows but won't be able to save them since they can't complete the required column.

We update these XML and JSON APIs to respect the access rule permissions configured for secured modeled sheet columns:

importConfigurableModelData
exportConfigurableModelData

To secure data entry columns in a modeled sheet:

Go to
Administration
Access Rules
.
Select
Manage
on the toolbar.
Ensure
Account
is selected. Account must be enabled for use in access rules to secure sheet columns.
Select
Manage Sheet Columns
on the toolbar.
In the dialog, select the sheet and the specific columns (Number, Date, Text, or Check box) you want to secure, then select
Save
.
Update your access rules by importing a rules file. You define access to these columns using the account (Grant) or account (Grant All Except) columns, using the syntax SheetCode.ColumnCode (Example: Personnel.Bonus).

If you don’t explicitly select columns to secure using the

Manage Sheet Columns

settings, all users with access to the modeled sheet will continue to see all data entry columns, consistent with previous behavior. Your existing access rules won’t be impacted.

If you use this feature with the headcount planning feature, ensure that you align your users’ HCM security access with their Adaptive Planning level access. If a user has higher level access in HCM than Adaptive Planning, they can still create or move positions to levels they don’t have access to in your access rules. Example: Your workforce planner has HCM access to levels 2100 and 2500.1, but in your access rules they can only access 2100.1. They can still use the headcount planning feature to create or move positions to 2100.2.

These examples describe some existing access rule setups, actions you take, and behavior to expect. We recommend that you review your existing access rules and identify if your access rules match these examples.

This example describes the most common expected scenario that results in behavior changes:

Existing Setup: Grant All on specific accounts, where 1 or more account is from Sheet A
Action: Secure column for Sheet A.
Behavior: That user will no longer have access to the secured column for Sheet A because access to that secured column wasn’t explicitly specified in their access rules.

These examples describe the most common expected scenarios that don’t result in behavior changes:

Example 1:

Existing Setup: Grant and Grant All Except is blank for Account, meaning users have access to all accounts.
Action: Secure column for Sheet A.
Behavior: Users will continue having access to all accounts, which now includes the secured column.

Example 2:

Existing Setup: Grant All on Account includes Sheet Name A, meaning users have access to All Accounts for Sheet A.
Action: Secure column for Sheet A.
Behavior: Users will continue having access to all accounts in Sheet A, which now includes the secured column.

Example 3:

Existing Setup: Grant All Except on Account includes Sheet A, meaning users have access to all accounts except for in Sheet A.
Action: Secure column for Sheet A.
Behavior: Users will continue to not have access to accounts in Sheet A, which now includes the secured column.