Workability Scope
Sets the highest organisational level where the user can actively work, update, manage and edit records.
Administrator question
How high should this person be allowed to actively work?
Hierarchical
Configuration.
License Type defines the user's broad access profile. Hierarchical Configuration defines their organisational reach: how high they can actively work through the Presto structure and how high they can see information through the hierarchy.
The two hierarchy controls
Workability and Visibility are not the same thing.
Presto separates the organisational level where a user can actively operate from the level where they may have wider read-only visibility.
Visibility Scope
Sets a higher read-only level, limited to activities where the user is included in the RACI matrix.
Administrator question
How high should this person be allowed to see?
Simple way to remember it
Workability = can do and edit. | Visibility = can view where included in RACI.
On-screen job aid
Where to configure hierarchical access.
Start from the Organisational Chart, select the relevant user or team, and open the Permissions workspace from the Team Details panel.
Keep the sequence simple
Open Permissions, then set the two hierarchy levels.
Hierarchical Configuration sits inside the user's Permissions workspace. Once the relevant user has been selected from the Org Chart, use the Permissions control to open the configuration panel and set the user's Workability and Visibility scopes.
Quick route
- Select the relevant user or team in the Org Chart.
- Review the Team Details panel on the right.
- Click Permissions.
- Set Workability Scope and Visibility Scope.
- Save the changes before closing.
Step 01
Open the Permissions workspace.
Select the appropriate user or team from the Org Chart and click Permissions in the Team Details panel.
Step 02
Set Workability and Visibility.
Select the highest organisational level where the user can actively work, then set the higher read-only level they may see where included in RACI.
Save before you close.
Permission changes do not take effect until they are saved. After reviewing both hierarchy settings, save the configuration before leaving the workspace.
Next: decide what the user can access.
With License Type and Hierarchical Configuration established, continue to Module & Dashboard Permissions Assignment to define the dashboards, modules and features available to the user.