How-To Create and Customize a Dashboard Using Keypup Development Intelligence Solution

This step by step tutorial describes the steps to create and customize a software engineering dashboard using Keypup.

Thomas Williams
Thomas Williams LinkedIn
• 4 min read
How-To Create and Customize a Dashboard Using Keypup Development Intelligence Solution

A dashboard is a user interface that provides a summary of key information populated from datasets. In Keypup, the dashboard is composed of multiple visualizations based on the user's needs. These visualizations can take the form of charts, KPIs, tables (reports), cards and boards.

Keypup's flexible interface allows you to customize, modify and enhance any existing tried-and-true template or to create your own dashboards starting from a blank canvas.

In this step-by-step tutorial, we will show you how to:

  • Create a new dashboard
  • Customize your dashboard

We will also:

  • Define a few concepts allowing you to better understand the dashboard’s interface, components and properties.
  • Introduce a graphical representation of the dashboard structure

Let’s get started!

How to create a new dashboard

To create a new dashboard, click on the (+) button located on the top left corner of the screen in the navigation bar. Give your dashboard a name and click on the “Create” button to save it.

Once created, your new dashboard is automatically pinned on your navigation bar on the left hand side of the screen, sorted by alphabetical order and you are automatically redirected to it.

Image

Now that you’ve created your dashboard, by default, you will access it in “viewer mode”.

How to customize your dashboard

To bring your dashboard to life, you will need to add a few components (insight widgets) and organize them onto the layout (canvas).

Components

To add an insight widget to your dashboard, click on the “Add chart” drop-down menu and select the visualization you would like to configure. You can add a chart, table, KPI, board or card. Your insight widgets are placed by default after the previously created one, but we will show you later on how you can easily organize them in the canvas. All insight widgets can be modified, resized or removed as needed.

Image

‍

Canvas

The “designer mode” helps you organize your insight widgets onto the canvas. You can access it by clicking on the “Edit dashboard” button placed on the top right corner of your screen, next to the “Add chart” button.

Image

The canvas is made of 16 cells, on which any insight widget can be placed and resized. Even though we do not limit its height, we recommend to consider narrower screens and avoid creating a dashboard longer than 12 cells.

Image

Dashboard properties

To further personalize your dashboard, you can customize the following elements:

  • The description (optional): you can add a description of your dashboard in “Designer mode” just below the title. While it’s optional, we recommend you to add a meaningful description for other users’ readability purposes.
  • The dedicated icon and its color (optional): next to the title, you can also modify the icon image (25 options) and its color (33 options).

Image

‍

Once you are happy with your dashboard press the Save button located on the top right corner of your screen.

‍

Any suggestion? Email us at [email protected] or ping us via the chat.

Ready to Transform Your Analytics?

Join teams already using AI to make data-driven decisions faster than ever.

Most Recent Articles

Pre-Production Environment Contention and Staging Drift: Why "Time to Release" Is Lying to You

Pre-Production Environment Contention and Staging Drift: Why "Time to Release" Is Lying to You

Enterprise releases don't move straight from commit to production — they queue through Integration, QA, UAT, Staging, and Pre-Prod, shared environments too expensive to replicate per team. Contention creates massive queues while staging drift causes builds to fail for reasons that have nothing to do with code quality. Standard SDLC analytics blame engineering for the resulting spike in Time to Release. Discover how Keypup MCP separates real code defects from environment queue wait and configuration drift, so leadership stops penalizing teams for infrastructure problems.

Arnaud Lachaume
The Multi-Service "Release Train" Problem: Ending Distributed Blame Attribution

The Multi-Service "Release Train" Problem: Ending Distributed Blame Attribution

Enterprises with tightly coupled systems can't release one microservice at a time — dozens of teams get bundled onto synchronized "release trains" across shared databases and legacy message buses. When a train fails, standard SDLC dashboards flag every participating team with a Change Failure, even the ones whose code was completely stable. When one team's late pull request delays the whole train, nobody's metrics capture it. Discover how Keypup MCP performs root-cause attribution across repository boundaries, ending the finger-pointing that per-team dashboards can't resolve.

Thomas Williams
ITIL and CAB Governance Bottlenecks Are Distorting Your Lead Time for Changes Telemetry

ITIL and CAB Governance Bottlenecks Are Distorting Your Lead Time for Changes Telemetry

In regulated enterprises — finance, healthcare, telecom — code can be written, tested, and merged in three hours, then sit for two to three weeks waiting on a Change Advisory Board slot. DORA's Lead Time for Changes can't tell the difference between active engineering work and passive bureaucratic wait, so executive dashboards flag a "velocity problem" that doesn't exist. Discover how Keypup MCP decomposes Lead Time into engineering-controlled time versus CAB queue wait, exposes SLA-breaching change categories, and gives engineering leadership the receipts to stop absorbing blame for a compliance calendar.

Arnaud Lachaume