1. Dashboards and Visualization
  2. Dashboards
  3. Design Dashboards
  4. Information for Dashboard Builders

As a Dashboard Builder, you’ll be adding elements to dashboards, formatting them, and adjusting them when alterations are required.

Most of your time will be spent in the Dashboard Designer. This provides a canvas where you can add and manipulate elements to present the data required by a particular type of user.

Dashboards are powerful and flexible methods of presenting data. Their main focus is automating and streamlining processes. Successful dashboards need to offer a consistent and intuitive user experience and provide meaningful information and cues for activity. As a dashboard builder, you create that experience.

To help you with this process, have a look at Design Dashboards, Dashboard Layout, and Types of Dashboards — they contain lots of advice about designing and creating dashboards. Consider the guidelines here, as well, before you embark on building a dashboard. Adopting some of these ideas will improve dashboard usability.

Dashboards and Data

In Contents, end-users see only modules and dashboards they’ve been given access to. Functional Areas organize modules and dashboards into meaningful groups that are easy to navigate.

Assigning a user to a role, and giving that role access to certain modules and dashboards, ensures that your users see only the data you want them to see.

To make this process robust:

  • When creating roles, employ a need-to-know approach to data access. This ensures that the roles realistically represent the activities of user groups.
  • Build dashboards that are targeted directly to the requirements of the role. It's better to have three simple dashboards, directed to three different roles, instead of one dashboard that displays data that is inappropriate for some users.

Contents fully supports this model of data access. Don’t be tempted to avoid Contents and add navigation buttons to dashboards.

Using navigation buttons does have implications for data access. For example, when you’re creating navigation buttons on dashboards, even though you may not have access to all dashboards, you can select any dashboard as a target for an Open Dashboard action. Similarly, you might see a small yellow warning triangle when a dashboard tries to display data from a module you don’t have access to. These are indications of poor data protection — using Contents protects against this.