Profiles
- If a user has one or more role profiles, the composite is derived across the profiles, giving the user as much access as provided (the "optimistic" approach).
- If a user has a user profile defined, it overrides any role profiles set otherwise for that user.
Add a Profile
To add a profile, click on the tab of the desired user type (Pro, Analyst, or Viewer), then click on the Add Profile button on the top right hand of the screen.
- Name: Each profile should be given a simple name
- Description: provide a light description of the profile for management purposes
- Tenant Security: Each profile is attached to a specific tenant in a multi-tenant environment, ensuring each tenancy can set up its users according to its own needs.
Select the Access and Features required for each app.
Profile Settings for User Types
- The Pro user profile provides access to all features available in Pyramid, while allowing access to be limited for each app in the application. The pro user profile is normally given to advanced users (Admin users, BI developers, and data workers).
- Click here to view Pro User Profile settings.
- The Analyst user profile provides access to lite version of Discover, Tabulate, Present, and Publish, while allowing access to be individually switched on or off for each app in the application. The analyst user profile is ideal for non-technical users who want to create content, but require a more simplified interface with less options available for the apps.
- Click here to view Analyst User Profile Settings.
- The Viewer user profile provides view-only access to the Pyramid apps, with the option of defining the level of interactivity for the different viewer user profiles. The viewer user profile is ideal for non-technical users who do not want to create content, but nevertheless require access to created content.
- Click here to view Viewer User Profile Settings.
Example
Profiles and Licensing combinations offer a large variety of combination for user deployment. The examples below demonstrate this.
An organizations wants to create 4 core types of users:
'Bob' - an advanced BI developer and data scientist; 'Daisy' - a proficient data worker; 'Casey' - an avid data consumer; and 'Nicole' - the non-technical light user. These roles are in addition to the administrative functions run by 'Alex'.
Using a mix of licensing and profiles, the admin can build the right user profile for his target customers:
- Bob, the advanced BI developer and data scientist is given complete access to the application (the default profile), but without administrative rights. Using all the tools he can create data sources and models, run advanced machine learning and scripts, build visualizations and design presentations. He often is asked to build smart data presentations and publications for Nicole and Casey.
- Daisy, the proficient data worker is given a role without machine learning and scripting options in the Modeling and Formulations work-flows / apps. The Illustrations app may also be turned off for her, since she prefers to do data analysis rather than spend time displaying it with fancy infographics. Working for the CFO, she is a serious number cruncher and creates her own calculations and her own models, even though she has limited knowledge of complex data science.
- Casey,the avid data consumer is given an analyst role. His system access provides him with enough capabilities to build his own visuals and design his own presentations and publications using the lite versions of the apps. As a line manager in consumer services, he often needs to tweak the visuals and build his own simple visuals but prefers to reuse the calculations made by others.
- Nicole, the non-technical, light user - and also the CEO - is given a viewer license which simply enables her to open existing discoveries and presentations, interact with them and print them out as needed. Without technical skill, she is not interested in creating new models or visualizations from scratch. And with limited time, she is only interested in seeing her corporate KPI dashboards rather than building them. She is also typically the recipient of numerous published reports of different analyses.
- Alex, the admin, has full application rights together with administrative access to control the data servers, content management system, logs and overall system state.