How to Create a Custom Dashboard in GoHighLevel

What a GoHighLevel custom dashboard should do

A dashboard should reduce the time needed to understand a business state. It should not force a manager to open several reports, reconcile different filters, or interpret unclear pipeline stages before taking action.

Before creating one, define the audience and the decision. A sales manager may need to know which opportunities require attention this week. An agency owner may need a view across accounts. A user responsible for lead handling may need to see new leads, response activity, and unassigned records. These are different reporting jobs and usually deserve different dashboards.

GoHighLevel dashboards commonly contain widgets for single-value metrics, charts, tables, and breakdowns of records such as leads or opportunities. The exact set of available widgets depends on the account configuration. The design principle remains the same: use a small number of clearly named views that help a defined user decide what to do next.

How to create a custom dashboard in GoHighLevel

GoHighLevel may use slightly different labels for these controls as the interface changes. If you cannot see the dashboards area or a creation option, check your user permissions and account context before assuming the feature is unavailable.

Choose the dashboard purpose before adding widgets

The most common dashboard mistake is starting with charts instead of questions. Write down the business questions first. For example:

• How many new leads entered the CRM during the selected period?
• How many opportunities are currently open in each pipeline stage?
• Which records have had no recent activity?
• How much potential revenue is associated with open opportunities?
• Which users or teams own the work that needs attention?

These questions describe different kinds of information. A total lead count shows volume, but it does not show whether leads were contacted. A pipeline chart shows distribution, but it does not necessarily show which records are stalled. A dashboard becomes more useful when each widget has a defined role in the operating process.

Add and configure widgets

Open the new dashboard and select the control used to add a widget. Depending on the account and current GoHighLevel interface, this may be labelled Add Widget or use a plus icon. Select the report or widget type, choose its data source, configure the relevant filters, and save it to the dashboard.

Common widget categories include:

• Single-value metrics: useful for totals such as new leads, open opportunities, or won value.
• Charts: useful for showing change over time, distribution by stage, or comparison between categories.
• Tables and lists: useful when a user needs to identify individual records and follow up on them.
• Breakdowns: useful for grouping records by pipeline, stage, user, source, status, or another available field.

Configure the widget around one question rather than trying to make one chart answer several unrelated questions. Give it a specific name. For example, Open Opportunities by Stage is clearer than Pipeline Chart, and Unassigned New Leads is more useful than Lead Report.

Use filters carefully

Filters determine what a dashboard actually means. Typical filters include date range, pipeline, opportunity status, assigned user, team, source, or stage. A widget showing open opportunities for all time is not equivalent to a widget showing new opportunities in the last 30 days.

For each widget, document or clearly name the important scope. Consider:

• Time period: Does the metric cover today, the current month, a rolling period, or the full available history?
• Record population: Does it include all contacts, only leads, or only opportunities in a specific pipeline?
• Ownership: Is the view filtered to one user, a team, or the whole account?
• Status: Are closed, lost, archived, or inactive records included?
• Comparison: Is the metric meant to be compared with a previous period or target?

Inconsistent filters are a common source of disagreement in reporting. If one widget uses all pipelines and another uses only the sales pipeline, placing them side by side can create a misleading comparison even when both widgets are technically correct.

Organize the dashboard for fast interpretation

After adding widgets, arrange them in the order a user should read them. Put high-level indicators near the top, followed by the views that explain movement, then the record-level detail needed for action.

A practical layout might place current lead and opportunity totals in the first row, pipeline distribution and trend information in the next row, and an actionable table of unassigned or inactive records below. The right arrangement depends on the reporting job, but the sequence should move from situation to explanation to action.

Keep the number of widgets controlled. More widgets can make a dashboard look comprehensive while making it harder to distinguish signal from noise. If a metric is rarely reviewed or does not change a decision, it may belong in a separate detailed report rather than the primary dashboard.

Example: a weekly sales pipeline dashboard

Consider a hypothetical sales team using GoHighLevel to manage inbound leads and opportunities. Its manager needs a dashboard for a weekly pipeline review. Instead of adding every available report, the team could define the following views:

1. A single-value widget for new leads during the selected week.
2. A pipeline breakdown showing open opportunities by stage.
3. A table of opportunities with no recent activity.
4. A view of unassigned leads that still need an owner.
5. A value metric for open pipeline, with its pipeline and status filters clearly defined.

This dashboard does not prove that the sales process is healthy. It gives the manager a starting point for asking better questions. If unassigned leads are increasing, ownership needs attention. If opportunities accumulate in one stage, the stage definition or handoff may need review. If open pipeline value rises while activity falls, the team may be carrying stale records.

Those conclusions require operational judgment. The dashboard supports the conversation, but it cannot fix unclear stages, missing ownership, or inconsistent data entry.

Dashboard data quality depends on CRM design

A dashboard is only as dependable as the records and business rules behind it. If users skip required fields, apply stages inconsistently, or leave opportunities assigned to former team members, the resulting charts may be visually polished but operationally weak.

Before relying on a dashboard, check the underlying CRM model:

A CRM stage should describe where a record is in the process, not merely the last activity someone performed. For example, a stage called Email Sent may describe an action, while a stage such as Qualified for Discovery may describe a business state. The latter is usually more useful for forecasting and handoff reporting.

If the underlying pipeline needs redesign, reporting changes alone will not solve the problem. ConsultEvo’s CRM consulting services cover pipeline architecture, lead management, integrations, and reporting design.

Manage, share, and review custom dashboards

Once a dashboard is in use, review whether it still supports the decisions it was created for. A dashboard can become misleading when a pipeline changes, a team structure changes, or a metric is retained after its process has been replaced.

Depending on the permissions and interface available in your account, you may be able to rename, edit, duplicate, pin, set as default, or delete a dashboard. Use clear naming conventions that indicate purpose and scope. Examples include:

• Sales Manager – Weekly Pipeline
• Lead Operations – New and Unassigned
• Account Overview – Monthly Performance
• Rep View – Active Opportunities

Before deleting a dashboard, confirm that no team routine depends on it. If a dashboard is shared, explain changes to filters or definitions so users do not compare old and new numbers without context. Access should also follow the principle of least visibility: users need the information required for their role, not necessarily every account-level metric.

For broader systems work involving CRM structure, reporting, automation, and connected tools, see ConsultEvo’s systems, CRM, automation and AI implementation services.

Use the dashboard as part of an operating rhythm

A dashboard becomes valuable when it is connected to a recurring action. Decide who reviews it, when they review it, and what happens when a number falls outside the expected range. Without that operating rhythm, the dashboard may become a passive display that nobody maintains.

A simple sequence is:

1. Review the high-level metrics for unexpected movement.
2. Open the breakdown that explains the movement.
3. Identify the records, owner, or stage responsible for the exception.
4. Agree on an action and record any required CRM updates.
5. Review the same metric in the next reporting period.

This approach keeps reporting connected to ownership and follow-through. It also makes it easier to remove widgets that do not contribute to a real meeting, review, or decision.

What a well-designed GoHighLevel dashboard achieves

Creating a custom dashboard in GoHighLevel is the configuration part of the work. The higher-value task is designing a reliable view of the process the CRM is meant to support. Start with a decision, define the relevant business state, choose only the widgets that explain it, and make filters and ownership visible.

GoHighLevel can provide a useful reporting layer for sales and lead operations, but it is not a substitute for process clarity. Automation should follow clear rules, and AI should only be introduced when it has a defined job, such as helping classify records or surface exceptions. More widgets, tools, or automation do not automatically create a better operating system.

For an example of a connected platform that brings together operations, reporting, and business data, see this ConsultEvoCommerce and Operations Intelligence PlatformAn example of connected operational reporting across finance, sales, procurement, supply chain, and business data.→