Panel | ||||
---|---|---|---|---|
| ||||
On this page:
|
Info | ||
---|---|---|
| ||
Dashboards provides at-a-glance views that organises and presents information in a way that is easy to read, showing a graphical presentation of the current and required statuses across several Lucidity Software applications. |
Tip | ||
---|---|---|
| ||
Shared Features: Dashboard Webinar Click the video below to view a 20 minute comprehensive training Webinar focusing on Dashboards. NOTE: This Webinar was recorded in September 2018. Any updates to the Dashboard tool since then will not be included. |
Dashboards are used to track key data points relevant to a business, department or specific process. Through the use of graphs, lists and tables, dashboards simplify complex data sets to provide users with at-a-glance awareness of current performance. Widgets are used to describe the variety of different items that can be added to a dashboard. Widgets display information that enables a user to perform a function or access a set of information and can be edited or filtered to only display certain information.
The dashboard and widgets functionality is available in several modules of Lucidity Software including:
- Lucidity Incident
- Lucidity InForm
- Lucidity Competency
- Lucidity Risk
Widgets can be shared between modules (excluding Lucidity Intranet) so Lucidity Incident details, for example, can be viewed from Lucidity Competency.
DASHBOARD ACCESS PRIVILEGES
In most system configurations, those with a manager access role are typically given access to Dashboards. Administrators will also have access to Dashboard templates. Permissions for all Lucidity modules are set via Lucidity Access and are generally configured by the administrator. Refer to the Access Roles page within the Lucidity Access user guide for more details.
Warning | ||
---|---|---|
| ||
Only the Dashboard Template Manager has the permission to manage Dashboard Templates. It is recommended that the number of Dashboard Template Managers per instance of Lucidity Software is kept to a minimum to retain integrity and consistency across the system configuration and to avoid duplication. It is a worthwhile exercise to create a standard set of guidelines that all new master data entered must follow. |
...