Dundas BI uses a concept of seats, designed to control the abilities and data access of users in the application. The three types of available seats are integrated with our licensing model and the application data flow:
2. Standard User
The standard user seat is targeted at users looking to consume or explore the available data. As an example, consider a business user. The user can view and interact with the dashboards that were created for him, but would like to see a visualization from one dashboard on a second dashboard. He can create a copy of a dashboard in his own project and add the visualization of interest by using a predefined metric set.
Users with the standard user seat can:
- View and interact with existing views, such as dashboards, reports, and scorecards.
- Collaborate by sharing data / images, adding notes to visualizations, and setting up notifications.
- Create and personalize views using existing business metrics definitions, such as metric sets, hierarchies, and time dimensions.
3. Power User
The power user seat is targeted at users looking to analyze the available data. As an example, consider a business analyst. The analyst would like to create a new visualization. She can create a new metric set based on existing data ETL, or an Excel file with the data by dragging it into the application, and customize it to meet branding requirements. The analyst can then add the metric set to a dashboard and set up filters for standard users to use.
Users with the power user seat can:
- Connect to data sources, such as Excel and flat files, or databases (if they have access to them).
- Create and modify business metrics definitions and views based on existing data sources and data ETL, such as data cubes, OLAP cubes, and cube perspectives.
- Design and modify the visual properties of business metric definitions and views.
- Add filters, formulas, and other analysis tools to business metrics definitions and views.
The developer seat is targeted at users looking to extend, integrate, and customize the application. As an example, consider a technical Business Intelligence (BI) professional. The BI professional would like to make sure users have access to real-time data. He can prepare data ETL using the company’s database as a data source, and make it available for the power user to use instead of Excel files. The BI professional can then embed the application into the company’s SharePoint intranet, and adjust the look and feel to help standard users find and interact with the data.
Users with the developer seat can:
- Connect to data and Create data ETL.
- Add scripts and customize all stages of the application data flow (data connectors, authentications, ETL transforms, formulas, visualizations, etc.).
- Integrate and embed the application into SharePoint, web applications, and OEMs.
- Customize the look and feel of the application.
You can assign the administrator role to any user in Dundas BI, regardless of their seat type. Administrator privileges do not integrate with our licensing model, and are not related to the data flow. Users with administrator privileges can:
- Manage user accounts, groups, sessions, and projects.
- View logs and change configuration settings.
- Manage licensing and multi-tenancy.
- Import, export, and manage deployment and version control.