Dashboard Customization

Choosing the Right Widgets

The widgets you place on your dashboard should directly support the questions you ask most frequently. Before customizing, take a moment to think about what you need to know at a glance when you open the platform each morning. That exercise will guide your widget selection.

For most users, a combination of room health summary, active alert count by severity, and a recent alerts list covers the essentials. These three widgets together give you a clear picture of your environment's current state and any issues that need attention. From there, you can add widgets that match your specific focus areas.

Avoid the temptation to add every available widget to your dashboard. A cluttered dashboard is harder to scan and slows down your ability to spot what matters. Choose a focused set of five to eight widgets that give you the information you need without overwhelming the view. You can always navigate to detailed sections for deeper data.

Role-Based Dashboards

Different roles in your organization have different monitoring priorities. A facilities manager cares about room availability and maintenance trends. An IT support lead focuses on device connectivity and alert response. An executive wants a high-level summary of operational health across all locations.

Consider creating separate dashboards tailored to each of these perspectives. Project Green may support multiple saved dashboard views, allowing each user to switch between layouts or have a default that matches their role. This ensures everyone sees the information most relevant to their responsibilities.

When designing role-based dashboards, involve the people who will use them. Ask what questions they need answered and what data they check most often. A dashboard built with user input is far more likely to be actively used than one designed in isolation based on assumptions.

Alert Summary Views

Alerts are one of the most important data points on any dashboard, and how you present them matters. A simple count of active alerts is useful, but a breakdown by severity is more actionable. Seeing that you have two critical alerts and ten informational ones tells a very different story than just seeing twelve alerts.

Consider adding a widget that shows alert trends over time. A chart displaying the number of alerts per day or per week helps you spot patterns and measure whether your environment is improving or deteriorating. Spikes in the trend might correlate with specific events, such as network changes or new device deployments.

If your team has alert response targets, such as acknowledging critical alerts within fifteen minutes, a widget showing time-to-acknowledge or resolution metrics can help track performance. These operational metrics turn the dashboard into a management tool as well as a monitoring tool.

Device Health at a Glance

A device health widget gives you a quick view of how your devices are performing across all rooms. This might show the percentage of devices online, a breakdown by device type, or a list of devices that have been offline the longest.

This view is especially useful for identifying chronic issues. A device that has been offline for days is a different problem than one that just went offline an hour ago. Sorting by duration of downtime helps you prioritize maintenance and follow-up, ensuring that long-standing issues do not get overlooked in favor of more recent ones.

You can also use device health widgets to track the rollout of new equipment or firmware updates. If you recently updated a batch of devices, a filtered widget showing their status helps you confirm the update was successful and catch any devices that did not come back online properly.

Sharing Dashboards

If you have built a dashboard layout that works well for your team, consider sharing it so others can benefit. Some platforms allow you to export a dashboard configuration or designate it as a template that other users can adopt. This saves time and promotes consistency across your organization.

When sharing dashboards, include a brief description of what the dashboard is designed for and who it is intended for. A label like "Facilities Daily Overview" or "IT Support Alert Dashboard" helps others understand the purpose and decide whether it is relevant to them.

Shared dashboards also serve as a useful starting point for new team members. Instead of building a dashboard from scratch, a new user can adopt a proven layout and customize it incrementally as they learn what works best for their own workflow.