Separate dashboards for customers and technical users

This article explains how to implement two distinct dashboards: a detailed view designed for and accessible only to technical users, and a high-level overview for customers.

Overview

In some projects, technical users need to be able to view all available dashboard information, while a customer should only be able to see a limited selection of information. This can be resolved by:

1. providing a full technical dashboard;

2. creating a separate, limited customer dashboard;

3. setting the customer dashboard as the default dashboard for the customer;

4. granting technical users the Asset Management permission;

5. and not granting this permission to customers.

As a result, a customer will open the simplified dashboard by default, while a technical user can switch to the full dashboard if necessary.

1. The challenge

An asset may contain a lot of technical information that is useful to installers, administrators, or other technical users. For an end customer, that same information may:

• be too technical;

• be irrelevant;

• cause confusion;

• contain information that the customer does not need to see.

The question, therefore, is:

How do I ensure that a customer sees only a limited dashboard, while a technical user retains access to the full dashboard?

Important principle

Do not use a single dashboard that is the same for everyone.
Use at least two dashboards:

2. The solution

The solution consists of three components that must be used together:

1. Different dashboards
   You create a dashboard for technical users and a separate dashboard for the customer.

2. Set the default dashboard
   Through the project group, you determine which dashboard opens by default for assets within that group. For clients, configure the client dashboard here.

3. Configure permissions
   Technical users are granted the following permission: Asset Management.
   The client is not granted this permission. This difference in permissions determines whether a user can switch from the default dashboard to other asset dashboards.

3. Dashboard 1: the technical dashboard

The first dashboard contains the asset’s complete technical information. This can be set up in two ways.

Option A — Use the asset type’s default dashboard

When we have shared an asset type and set up a default dashboard for it, that dashboard can be used as the technical dashboard. This is especially useful when the same technical dashboard structure is used for multiple clients or projects.

Option B — Create a custom technical dashboard

You can also create a separate dashboard specific to the project or client. Use this option when, for example:

• the client has a non-standard installation;

• different metrics are relevant;

• the default template does not contain enough information;

• technical users need a project-specific dashboard layout.

4. Dashboard 2: the customer dashboard

Next, create a second dashboard. This dashboard is specifically intended for the customer, so only include information that is relevant to the customer. For example:

• current status;

• key KPIs;

• energy consumption;

• comfort levels;

• fault status;

• simple graphs;

• summary information.

Omit internal or highly technical information if the customer does not need it. Examples include:

• internal control parameters;

• diagnostic data;

• technical setpoints;

• detailed measurements;

• configuration information;

• technical troubleshooting information.

The customer dashboard is therefore not necessarily a simplified copy of the technical dashboard. It is better designed based on the question:

What information does this user need to perform their task?

5. Setting the customer dashboard as the default

Once both dashboards have been created, you need to determine which dashboard opens automatically. This is done through the project group. Set the customer dashboard as the default dashboard there.

What does “default dashboard” mean?

When a user opens the dashboard for an asset in that group, the configured default dashboard is automatically displayed. If the customer dashboard is set as the default, the customer will immediately see the restricted customer view. The customer does not need to select anything themselves.

6. Custom default dashboard for a single asset

The dashboard configured for the project group generally applies to all assets covered by that setting. However, sometimes a specific asset needs to display a different dashboard. For this reason, a custom default dashboard can also be set for an individual asset. This is useful, for example, when:

• one installation differs from the rest;

• one asset needs to display additional information;

• there are different types of installations within the same project group;

• a project-specific dashboard view is required for a single asset.

In such cases, the asset-level setting can be used to deviate from the group’s default dashboard.

7. Setting permissions correctly

Simply setting up a default dashboard is not enough. User permissions must also be set up correctly.

Technical user

A technical user is granted the following permission:

Asset Management

With this permission, the following button appears in the top-right corner of the dashboard, next to the date picker:

Asset Dashboard

Using this button, the technical user can switch to another available dashboard for the asset. This allows them, for example, to open the full technical dashboard, even when the customer dashboard is displayed by default.

Customer

The customer is NOT granted the Asset Management permission. Because the customer does not have this permission, they will not see the Asset Dashboard button. As a result, the customer remains on the dashboard that was set as their default dashboard.

8. Use case: customer has limited view, technician has full view

Use the guide below when a customer is only allowed to see limited information, but a technical user must be able to view all dashboard information.

Situation

For this example, we have an asset:

Heat Pump 01

There is a comprehensive technical dashboard for this asset, including:

• temperatures;

• pressures;

• setpoints;

• compressor status;

• control parameters;

• error codes.

The customer only needs to see:

• whether the system is operational;

• energy consumption;

• the desired and current temperature;

• any active faults.

Step 1: Keep or create the technical dashboard

For example:

Heat Pump - Technical

This contains all the information a technical user needs.

Step 2: Create a customer dashboard

For example:

Heat Pump - Customer

Include only the information that is useful to the customer. For example:

• Status: OK / Malfunction

• Current temperature

• Desired temperature

• Energy consumption

• Any alarm notifications

Step 3: Set the customer dashboard as the default

Open the configuration for the relevant project group. Set the following there:

Default dashboard → Heat Pump - Customer

From that point on, this dashboard will open by default for the assets within that group.

Step 4: Grant the technician asset management permissions

Check the technical user’s permissions. Ensure this user has the Asset Management permission. This will cause the Asset Dashboard button to appear in the top-right corner for the technician.

Step 5: Do not grant the customer asset management permissions

Next, check the customer’s permissions. Ensure that Asset Management is not enabled. This prevents the customer from switching to the technician’s dashboard via the Asset Dashboard button.

Result

9. Use case: different dashboards for different assets

Situation

A project group contains ten assets. The same customer dashboard works for nine of the assets. However, one asset has a different setup and needs to display a different dashboard.

Approach

Set the general customer dashboard as the default for the project group. For example:

Default project group dashboard → Customer - Standard

For the asset with the different setup, set a specific default dashboard. For example:

Asset 10 → Customer - Special Setup

This way, you don’t have to create a separate group or dashboard structure for the entire project.

10. Use case: combining a default technical template with a customer dashboard

Situation

A technical dashboard already exists for the shared asset type. You want to continue using this technical dashboard, but the customer should not be directed to this technical view by default.

Approach

Use the existing dashboard for the asset type as the technical dashboard. In addition, create a customer dashboard. For example:

Existing template → Boiler - Technical

New dashboard → Boiler - Customer

Next, use the project group to set Boiler - Customer as the default dashboard. Technical users retain access to asset management and can switch to the technical dashboard if necessary. The customer does not have access to asset management and therefore remains in the customer view.

11. Common mistake: changing only the default dashboard

A common misconception is:

“If I set the customer dashboard as the default, the customer will no longer be able to see the technical dashboard.”

That is not necessarily sufficient. A default dashboard determines which dashboard opens first. User permissions then determine what else a user can do. That’s why both settings must be combined:

Default Dashboard → determines “What does the user see first?”

Asset Management → determines “Can the user switch to other asset dashboards via the dashboard interface?”

Therefore, always check both the dashboard and the permissions.

12. Post-configuration check

Ideally, test the configuration using both user profiles.

Check as a Customer

• Open an asset.

• Verify that the customer dashboard opens automatically.

• Verify that only the desired customer information is visible.

• Verify that the Asset Dashboard button is not visible.

• Verify that the customer cannot switch to the technical dashboard using this dashboard switcher.

Verification as a technical user

• Open the same asset.

• Check which default dashboard opens.

• Verify that the Asset Dashboard button is visible in the upper-right corner.

• Use this button to open the technical dashboard.

• Verify that all necessary technical information is available.

13. Decision tree

Want to determine which configuration you need? Use the decision tree below.

Should the customer see the same information as the technical user?

→ Yes: a single dashboard may be sufficient.

→ No: create a separate customer dashboard.

Should the customer dashboard open by default?

→ Yes: set the customer dashboard as the default via the project group.

Does a single asset require a different dashboard view?

→ Yes: set a different default dashboard for that asset.

Should the technical user be able to switch to other dashboards?

→ Yes: grant this user Asset Management rights.

Should the customer be able to switch to other asset dashboards?

→ No: do not grant the customer Asset Management rights.

14. Recommended structure

For a clear and maintainable configuration, we recommend the following structure:

• Technical Dashboard

  Contains all information for technical users.

• Customer Dashboard

  Contains only information relevant to the end customer.

• Project Group

  Set the customer dashboard as the default.

• Technical Users

  Asset management → allowed

• Customers

  Asset management → not allowed

The result:

The customer automatically sees a simplified dashboard view, while technical users retain access to the more comprehensive dashboards via the Asset Dashboard.