Profiles

Profiles provide a convenient mechanism for admins to control the different authoring work flows and apps pro users can access. Different profiles are defined and then applied at either the role level or user level.

  • 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.

Note: User Profiles are not applicable to Viewer Licensed users, since all feature options related to viewers are set as runtime settings in the content itself.

Add a Profile

  • 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.

Profile Settings

Each profile definition has a master switch for each of the apps in the application - Model, Discover, Illustrate, Formulate, Present and Publish - determining whether the Pro user can open these applications and create the associated content. Under these main switches are several sub-switches:

Model

  • Add Data Server: this will allow the user to add new data source servers without admin approval or oversight. This switch affects both the modeling tool as well as the "add server" feature i the start-up of Discovery
  • Use Machine Learning: this will allow the user to access the ML function panel in the data flow application and its associated ML algorithms
  • Create Scripts (r, Python): this will allow the user to access the scripting function panel, create and run various scripting tools (R, Python and SAS)
  • Create Custom SQL Scripts (SQL target): allows the user to execute a custom SQL script when the ETL is run
  • Execute Process: allows the user to configure and use the "command" node option int he master flow.

Discover

  • Discover Lite: the user will have access to Discover Lite interface only. If unchecked they will have access to the full Discover Pro module.
  • Advanced Analytics: this will allow the user to access the advanced analytic options (under Analysis in the Query ribbon) throughout the discovery app - like forecasting, Pareto analysis and trending.
  • Save Shareable Content: allow the user to share content in the workgroup and public folders
  • Auto Discovery: the user will have access to Auto Discovery.

Formulate

  • Create Formulas, KPI's and Parameters: this will allow the user to build new shared formulas, lists, KPI's and parameters for Discovery
  • Create Scripts (R, Python): this will allow the user to build new shared scripts in Python, R and SAS
  • Custom Visuals: allows the user to build, share, and see custom visuals

Publish

  • Smart Publish: allow the user to open the Smart Reporting tool from Publish.
  • Select Multiple Items: allows the user to select and run the Multiple option, in order to select multiple slices when scheduling publications

  • Scheduling: allow the user to schedule publications.

Present

  • Smart Present: allows the user to open the Smart Reporting tool from Present.
  • Present Lite: the user will have access to Present Lite only. In unchecked they will instead have access to the full Present Pro module.

Illustrate

  • Determine whether the user should have access to Illustrate or not.

General

  • Advanced Options: enables advanced functionality across the all the applications, including: the "More" options in drop down menus; Analysis tools, N-of-N, Variable List, Time Intelligence, and Cache Options in Discover; Open Related Content, Copy Link, Embed, Save as New Version, Save & Close from the CMS.

Example

Profiles and Licensing combinations offer a large variety of combination for user deployment. The examples below demonstrate this.

ClosedProfile and Licensing Example

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 a role without access to Modeling, Formulations or Illustrations. Further, advanced analytics in Discovery is disabled as well. His system access provides him with enough capabilities to build his own visuals and design his own presentations and publications. 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.