Giving someone access to Presto is more than selecting a license type. Effective administration requires three connected decisions: choosing the right user license, defining how far that person can see and work through the organisational hierarchy, and deciding which modules, dashboards and features they are permitted to use.
The objective of license administration is not to give every user the same experience. It is to give each person the right level of access for the work they are expected to perform while protecting information, reducing unnecessary complexity and keeping accountability clear.
Think of each user as having three connected settings: their license type, their position and reach within the hierarchy, and their functional permissions. The combination of those settings determines their practical Presto experience.
Treat these as three separate controls. A user's license type does not, by itself, determine everything they can see, everything they can work on, or every feature available to them.
Select the license that best reflects how the person will use Presto. This establishes the broad user profile and the type of interaction expected from that person.
Define how far the user can move through the organisational hierarchy when using the Presto Dashboard - both what they are permitted to see and where they are permitted to work.
Decide which Presto modules, dashboards and specific capabilities should be available to the user through the Permissions configuration panel.
A person can have an appropriate license type but still have the wrong hierarchical reach or unnecessary module access. Good administration means reviewing all three control layers together.
The Permissions workspace makes these controls practical. Administrators can define organisational scope separately from the modules, dashboards and features made available to the user.
Presto separates the level at which a user can actively operate from the level at which they may have wider read-only visibility. This allows administrators to support management oversight without unnecessarily extending editing or management rights.
The highest organisational level where the user can actively work, update, manage and edit records.
A higher read-only level, limited to activities where the user is included in the RACI matrix.
The same Permissions workspace is also used to determine which common features, dashboards, filters, widgets and reports are available to the user. Hierarchical reach and functional permission therefore need to be considered together, but configured as separate decisions.
License Type is the first decision because it establishes the broad relationship the person will have with Presto. The detailed configuration steps are covered next in the License Type Configuration job aid.
Using the same three questions every time creates a repeatable access-management discipline and makes future license reviews much easier.
Choose the appropriate license type based on the person's role and how they are expected to participate in Presto.
Configure the person's hierarchical visibility and workability so their dashboard reach matches their organisational responsibility.
Assign the modules, dashboards and specific features required for their job - and avoid providing unnecessary access.
User responsibilities change. Teams move, managers take on broader remits and people leave roles. License administration should therefore be treated as an ongoing governance activity, not a one-time setup task.
Start from what the person is accountable for, then configure the minimum access needed to perform that responsibility effectively.
Revisit user configurations when roles, reporting lines, team ownership or governance responsibilities change.
The learning path now follows the same sequence an administrator should use in practice: configure the License Type first, then Hierarchical Visibility & Workability, then Module & Dashboard Permissions. Password administration follows once the user's access profile has been configured.
