GoHighLevel Pipeline Customization: Brand Your Deal Board

Your client’s sales team lives on the pipeline. They open HighLevel (also called GoHighLevel or GHL) in the morning, go straight to Opportunities and spend the day dragging cards between columns. Yet that board is the least branded screen in most agency setups: every column header looks the same, every card is a white box, and the menu calls the work “Opportunities” even when the client sells roofs, houses or legal services. GoHighLevel pipeline customization is how you fix that, and most agencies only do half of it.

This guide covers the whole job. It explains what HighLevel’s own pipeline settings change (stages, stage colors, card fields and layouts), what needs custom code (the board’s look and the menu wording), how to choose stage colors that stay readable, how to set up a branded board step by step, how to show a pipeline on a call without exposing deal values, and what a theme cannot fix. Where GHL Dashboard Builder helps, we say which plan includes it. We are independent and not affiliated with HighLevel, and we name the limits along with the options.

What is GoHighLevel pipeline customization?

GoHighLevel pipeline customization means shaping the Opportunities board so a client’s team can read it at a glance and recognizes it as their own tool. It has three layers: the pipeline’s structure and display settings inside HighLevel, the board’s visual design through custom CSS, and the menu wording through custom JavaScript.

A few terms first, because HighLevel uses them precisely:

• Pipeline: a sequence of stages that a deal moves through, such as New lead, Contacted, Quote sent, Won. A sub-account can have several pipelines, for example one for sales and one for onboarding.
• Stage: one column on the board.
• Opportunity: one deal, job or case, shown as a card in a stage. Each opportunity also has a status (open, won, lost or abandoned) that is separate from its stage.
• Board view: the column layout, also called a Kanban board. HighLevel also offers a list view of the same opportunities.

The three layers do different jobs and do not replace each other:

1. HighLevel’s own settings decide what the board contains: which stages exist and in what order, which color each stage carries, and which fields and counters appear on each card. These are free, supported by HighLevel and safe to change.
2. Custom CSS decides how the board looks: the shape and color of stage headers, the background behind the columns, the style, corners and shadow of each card, and the accent color for values and hover icons. HighLevel provides the place for this code but does not offer these options as settings.
3. Custom JavaScript decides what the board is called: the Opportunities menu item renamed to Deals, Jobs, Listings or Matters, in the client’s language.

Most agencies stop after the first layer. That is a good start, and this guide walks through it properly, but clients still see the standard HighLevel board around their stage colors. If you are new to the wider picture, our map of GoHighLevel dashboard customization explains the same three layers for every part of the interface, not just the pipeline.

What can you change in GoHighLevel’s own pipeline settings?

HighLevel’s own settings let you create pipelines and stages, color each stage, and choose which fields, counters and layout appear on opportunity cards. At the time of writing these cover the board’s content and stage color, but not the shape of headers, the style of cards or the name of the Opportunities menu item.

Pipelines and stages

According to HighLevel’s help article on pipelines, you open Opportunities in the sidebar and choose Pipelines from the top menu to create a pipeline, add, reorder and delete stages, and control whether the pipeline appears in the Dashboard’s funnel and pie chart widgets. The same article notes that pipeline names must be unique within a sub-account and that a newer Pipelines page can be switched on from the sub-account’s Labs settings, so your screen may look different depending on that choice.

Stage names are the first and cheapest branding decision you make. “Quote sent” tells a roofing crew more than “Stage 3”, and a stage list in the client’s own vocabulary does half the work a renamed menu does.

Stage colors

HighLevel now lets you give each stage a color. HighLevel’s article on pipeline stage colors explains that colors are set per pipeline on the pipeline’s Stages tab, can be shown as a colored dot or a background tint (or not at all), and appear in the board and list views, on opportunity cards and in the contact’s details. Everyone who can see the pipeline sees the same colors.

This is the most important built-in option for readability, and you should use it. It is also a functional color, not a brand system: it marks stages, but it does not change the header shape, the board background or the card design around it.

Opportunity cards

HighLevel’s guide to customizing opportunity cards describes the Manage Fields button at the top right of the board. There you can:

• choose up to 7 fields for each card, from standard fields such as opportunity name, value, owner, source and status, and from your opportunity custom fields;
• choose which quick-action counters show at the bottom of the card: conversations with unread messages, tasks, notes, tags, calls and the next appointment;
• pick a Default layout that shows each field’s label and value, or a Compact layout that shows values only, with labels on hover;
• apply the setup to one pipeline or to all pipelines in the sub-account.

One detail matters for agencies. HighLevel’s article describes these card settings as user-specific, and users on HighLevel’s ideas board ask for card and list columns to be saved at account level because they reset in a new browser. Treat the card setup as part of each user’s onboarding, not as something you configure once for the whole team.

At a glance: what lives where

The pattern is clear: HighLevel gives you the structure and a functional color per stage; the brand look and the client’s vocabulary need code. Menu paths in HighLevel move from time to time, so if a name in this section has changed, search the help center for the setting’s name.

How does GHL Dashboard Builder brand the opportunities board?

GHL Dashboard Builder is an independent design service that turns the standard HighLevel (GoHighLevel) dashboard into a branded platform: your colors, menu, login design, privacy mode and your clients’ language, installed with two lines of code. For the pipeline, it adds a branded opportunities board on top of HighLevel’s own stage and card settings.

You set the board up visually in the builder, along with the rest of the theme, and preview it on desktop, tablet and phone before anything touches your account. The board options are:

• Stage header shape: a rounded bar, a square bar, a pill, or a white header with a brand-colored line on top.
• Header colors: the header background and the header text, in your brand colors or the design’s defaults.
• Board background: the color behind the columns.
• Card style: an accent edge in the brand color, a plain card with a border only, or a soft brand tint.
• Card details: card background, border, title color (the opportunity’s name) and text color (labels and details).
• Corners and depth: a card corner radius from square to 20 pixels, and a shadow on or off.
• Accent color: used for the card edge, the deal value and the action icons on hover.

Turn the board option off and HighLevel’s own plain board shows, with your other theme settings still applied. The board is part of the buttons, cards and forms options, which are in every plan.

The table lists the features that matter most for a pipeline-heavy client, what each does for the client’s team, and the first plan that includes it. All 18 features are described on our features page.

Installing takes about five minutes: one CSS line and one JavaScript line go into Settings, Company, Whitelabel, Custom Code in the agency view. The two lines stay the same when you change the design later; you edit it, press Deploy to live, and HighLevel picks up the new version. On Pro and Agency, we install it for you.

What the client’s team sees afterwards: the same pipeline, the same stages and the same cards they configured, now in the agency’s or the client’s colors, with headers they can tell apart from across the room and, from Pro, a menu item that uses their own word for the work. HighLevel’s data, permissions and automations are unchanged.

How do you choose pipeline stage colors that stay readable?

Choose stage colors as a scale that runs from early stages to won, check that the text on each colored header passes contrast, and never let color be the only signal. The W3C asks for at least 4.5 to 1 contrast for normal text, and many bright stage colors fail with white text.

Use a scale, not a rainbow

A board with seven unrelated colors looks lively in a screenshot and tiring after an hour. A better system has a clear logic:

• Early stages in a neutral or light brand shade.
• Middle stages in stronger shades of the brand color, getting darker as the deal progresses.
• Late stages such as Contract sent in the strongest brand shade.
• Won in green, and red reserved for lost, stalled or overdue, so red keeps its meaning.

If you use HighLevel’s stage colors for meaning, keep the theme’s header color neutral or brand-colored and let HighLevel’s dot or tint carry the stage signal. If you color the theme’s headers by brand, consider HighLevel’s dot rather than the full tint, so the two do not compete. Whichever you pick, check the combination on the live board, because a background tint and a colored header can make each other harder to read.

Check the contrast of every header

The W3C’s guidance on minimum contrast sets 4.5 to 1 for normal text and 3 to 1 for large text. Stage header text is usually small and bold, so plan for 4.5 to 1. We calculated the contrast of white header text on common stage colors with the W3C’s formula:

Violet5.70

Teal5.47

Blue5.17

Dark green5.02

Red4.83

Mid green3.30

Bright green2.28

Amber2.15

Hex codes: blue #2563EB, violet #7C3AED, teal #0F766E, red #DC2626, dark green #15803D, mid green #16A34A, bright green #22C55E, amber #F59E0B. Source: Calculated with the W3C WCAG 2.2 relative-luminance formula, October 2026. Normal text needs at least 4.5 to 1.

The pattern is the useful part: the greens and ambers people reach for to mean “won” and “needs attention” are exactly the ones that fail with white text. You have two fixes. Use a darker shade, such as the dark green above, or keep the bright color and switch the header text to near-black: the same amber scores 8.26 to 1 with dark text (#111827), by the same formula.

Don’t rely on color alone

The W3C’s guidance on use of color says color should not be the only way information is shown. On a pipeline that means the stage name stays visible on every header, won and lost deals keep their status, and overdue items get a word or icon as well as a red edge. Some of your client’s team will not see the difference between two similar colors, and a shared screen across the room makes it worse, so the words on the board carry the meaning and the colors only speed it up.

The thinner parts of a board need contrast too. The non-text contrast criterion asks for at least 3 to 1 for the visual parts of controls and graphics people need to understand, which includes a card’s accent edge if it carries meaning and the icons a user clicks.

A sample color plan

Status colors such as won and lost should stay recognizable in any brand. Our guide to HighLevel custom CSS explains how to define these colors once so the board, buttons and tags stay consistent.

Can you rename Opportunities and Pipelines in GoHighLevel?

You can name every pipeline and stage in HighLevel’s own settings, but you cannot rename the Opportunities menu item there at the time of writing. Renaming it to Deals, Jobs, Listings or Matters takes custom JavaScript that changes the label in the browser, which is what a menu editor generates.

Why the menu word matters on the pipeline

The pipeline is where industry vocabulary hurts most. A roofing office does not have opportunities; it has jobs. A real estate team has listings, a law firm has matters, a car dealership has deals. When the menu says Opportunities, every new hire asks what that means, and every training video needs a sentence of translation. Renaming the menu item removes that friction for the whole team.

What renaming does and doesn’t change

• Changes: the label in the sidebar or top navigation, in the words and language you choose.
• Doesn’t change: HighLevel’s page titles, filters, workflow action names, reports or help articles, which still say opportunity. Tell clients this once, so a workflow step called “Create/Update Opportunity” does not confuse them.
• Doesn’t change: permissions. Hiding a menu item does not block access; use HighLevel’s user roles for that.

Doing it by hand

1. Decide the client’s word and the word in each language their users work in.
2. Write JavaScript that finds the Opportunities menu item by a stable attribute rather than by its visible text, because the text changes with HighLevel’s platform language.
3. Re-apply the label whenever HighLevel switches screens, since it does not reload the whole page.
4. Check every user role and both the sidebar and any top navigation.

In GHL Dashboard Builder, the menu editor in the Pro plan renames, reorders and hides any of HighLevel’s 19 menu items, adds New and Beta labels, and adds favourites, so a sales manager can pin a specific pipeline to the top of the menu. Several templates come with the pipeline already renamed: Estate calls it Listings, Counsel calls it Matters, Torque calls it Deals, Roofline calls it Jobs and Shine calls it Bookings.

Which pipeline setup fits each industry?

Each industry needs different stages, a different word for the deal and different fields on the card. A good pipeline mirrors the client’s real process in five to eight stages, uses their vocabulary for the menu and stages, and shows the two or three facts their team checks first on every card.

The table gives starting points. The stage lists are examples to adapt, not HighLevel defaults; the menu words are the ones our industry templates use.

Practical rules for any industry

1. Keep it short. If a stage never holds a card for more than a day, merge it with the next one.
2. One pipeline per process. Sales and onboarding belong in separate pipelines, so the board does not mix leads with paying customers.
3. Show the money only where it helps. Value on the card is useful for the owner and distracting for a front-desk team; HighLevel’s per-user card settings let different people see different fields.
4. Name stages as actions completed, such as Quote sent, not as vague states such as Pending.

Industry clients also need the rest of the dashboard to match. Our setup guide for dental and medical practices and our GoHighLevel guide for gyms and fitness studios show how the pipeline, menu and calendar fit together for two very different businesses.

Seeing a board in your colors usually settles the color debate faster than any discussion, so try it before you decide.

How do you set up a branded GoHighLevel pipeline, step by step?

Set up the structure in HighLevel first, then the cards, then the brand layer, and test with a real user before rolling out. The whole sequence takes an afternoon for one client, most of it spent agreeing the stages with the client rather than clicking.

Part 1: structure in HighLevel

1. In the client’s sub-account, open Opportunities and choose Pipelines from the top menu (or use the edit icon next to a pipeline in the pipeline dropdown).
2. Create the pipeline with a clear name, such as “Sales” or “Roof replacement”. Names must be unique within the sub-account.
3. Add the stages in order, named as completed actions. Five to eight is a sensible range for most small businesses.
4. In the pipeline settings, decide whether the pipeline should appear in the Dashboard’s funnel and pie chart widgets.
5. On the Stages tab, choose a color for each stage and the display style: colored dot or background tint.

Part 2: cards for each role

1. On the board, click Manage Fields at the top right.
2. Choose up to 7 fields. Start with the three the team checks first, then add only what saves a click.
3. Choose the counters: conversations and next appointment are the most useful for most service businesses.
4. Pick Default or Compact. Compact suits long pipelines on smaller screens; Default is easier for new users.
5. Apply to this pipeline or all pipelines, then write the setup down for each role, because each user’s card settings are their own.

Part 3: the brand layer

1. Open the builder, choose a template or start from scratch, and set the brand colors.
2. In the board options, pick the header shape, header and text colors, board background, card style, corner radius, shadow and accent color.
3. If you are on Pro or Agency, rename Opportunities in the menu editor and pin the main pipeline as a favourite.
4. Preview on desktop, tablet and phone, and check each header’s contrast against the chart above.
5. Install the two lines under Settings, Company, Whitelabel, Custom Code in the agency view, after saving a copy of any code already there.

Part 4: test before the client sees it

1. Open the sub-account in a new tab and hard-refresh the board.
2. Load a pipeline with at least ten stages and fifty cards, and scroll sideways to the last column.
3. Drag a card between stages and open one, to confirm nothing in the theme gets in the way.
4. Log in as a user with limited permissions and check the menu and the board.
5. Narrow the window to phone width and check that headers and card text still fit.

HighLevel’s own card and color options are worth knowing as numbers, because they set the limits of the built-in layer before any theme is involved.

Fields per card (maximum)7 options

Quick-action counters6 options

Stage color styles3 options

Card layouts2 options

Stage color styles: default (none), colored dot, background tint. Card layouts: Default and Compact. Source: HighLevel Help Center: Customize Opportunity Cards in Board View, and How to Customize Pipeline Stage Colors in Opportunities (October 2026).

Seven fields is a ceiling, not a target. Most teams read three or four fields at a glance; the rest belong on the opportunity’s detail screen. Most complaints about branded boards come from a long pipeline nobody tried, or from a role that sees a different menu, so give testing as much attention as building.

How do you show a GoHighLevel pipeline to clients without exposing deal values?

Use a demo sub-account with sample deals for every sales call, training video and screenshot, and blur client data whenever you must show a live account. The opportunities board is the screen that shows the most sensitive numbers at once: names, phone numbers and the value of every deal.

Why the pipeline is the riskiest screen to share

Agencies show the pipeline more than any other screen: in sales demos (“this is where your leads will land”), in weekly reviews with clients, in support calls and in recorded training. A single shared board can show dozens of client names and deal values to someone who should not see them, and a recording keeps them long after the call.

A safe routine

1. Build a demo sub-account with a realistic pipeline and invented deals. Use it for every demo, screenshot and video.
2. Share a tab, not the whole screen, so notifications from other clients do not appear.
3. Hide values on the card for demo users with HighLevel’s Manage Fields, if the value is not what you are showing.
4. Blur before you share a live board. When a client’s real pipeline must be shown, blur names, phone numbers and deal values first.
5. Check recordings before you publish them, pausing on every frame where the board is visible.

In GHL Dashboard Builder, privacy mode is an eye button in HighLevel’s header, in every plan. While it is on, contact names, email addresses and phone numbers, the conversation list and opportunity values are blurred, and you choose how strong the blur is. It is a screen-sharing tool, not a security control: anyone with access to the account can still turn it off or open the records.

Can one client’s pipeline board look different from the rest?

Yes. Custom code is installed once at agency level and loads for every sub-account, but JavaScript can check which sub-account is open by its Location ID and apply a design only there. That lets you give one client a branded board while your other sub-accounts keep their current look.

When per-client branding makes sense

• A premium client pays for a platform that looks like their own sales tool.
• A pilot: you test a branded board with one friendly client before rolling it out.
• A sales-heavy client with a large team on the board all day, where readability pays off fastest.
• A different language: one client’s team works in Arabic or Spanish while the rest of your clients work in English.

How it works in GHL Dashboard Builder

Choose “Only these sub-accounts” in the builder and add each sub-account by its link or Location ID. Those sub-accounts get the design, including the branded board; the agency view and every other sub-account stay plain HighLevel. You still paste one install, and you can add or remove sub-accounts at any time. This is available in every plan.

Be clear about one limit: one design is shown in the chosen sub-accounts. If you want different looks for different clients, such as Estate for one and Roofline for another, talk to us about your setup before you buy, so we can recommend the right approach. Pro includes up to 3 designs and Agency up to 100.

If that client’s team works in another language, the menu and navigation can follow: 15 languages are available from Pro, with right-to-left layout for Arabic, Urdu and Hebrew. Text inside HighLevel’s own pages, including the opportunity detail screens, follows HighLevel’s language settings.

What can go wrong, and what doesn’t a pipeline theme solve?

A theme changes how the board looks and what the menu is called. It does not change HighLevel’s pipeline logic, mobile apps, reports or the card fields each user picks, and it may need a refresh after HighLevel changes the board. Knowing these limits up front avoids promising a client something no theme delivers.

The update risk deserves a plain sentence. HighLevel changes its interface often, and the opportunities board is an active area: card layouts and stage colors are both recent additions documented in HighLevel’s help center. When a screen’s structure changes, styling that depended on the old structure may stop applying, and the board falls back to HighLevel’s standard look until the theme is refreshed. Your data is never affected, but clients notice. That is why Starter and Pro include 12 months of updates (optional afterwards at $99 a year) and Agency includes lifetime updates, and why any theme you build yourself needs someone who checks it after releases.

If HighLevel’s own white-label basics are not done yet (your domain, logo and legal links), do those first; our guide on how to white-label HighLevel walks through them.

Should you build a pipeline theme yourself or use a builder?

Build it yourself if you know CSS and JavaScript, need one look for the whole agency and have someone to maintain it after HighLevel updates. Hire a developer for unusual requirements. Use a builder when you want a tested board, industry menu wording and a preview before you install, without maintaining code.

A word on doing it yourself: board styling is a reasonable first project for someone learning CSS, because it is contained to one screen. The hard parts are the selectors, which must survive HighLevel’s updates, and the testing across long pipelines, narrow screens and roles. The custom CSS guide covers both.

If you go with GHL Dashboard Builder, the plans are one-time payments with no monthly fees. Upgrading later costs the difference between plans.

Starter (1 design)$180

Pro (up to 3 designs)$280

Agency (up to 100 designs)$880

Source: GHL Dashboard Builder pricing, October 2026 (config/site.ts). One-time payments, no monthly fees.

For a pipeline-focused client, Starter covers the branded board, colors, privacy mode and a design limited to chosen sub-accounts. Pro adds the menu editor that renames Opportunities, favourites, live menu counts, 15 languages, the login page and installation by our team. Agency adds a look designed from scratch by our team, your own custom CSS and JavaScript, up to 100 designs and lifetime updates. The pricing page lists the full contents of each plan, and questions about revisions, installs and updates are answered in our FAQ.

What to do next

1. Agree the stages with one client. Five to eight, named as completed actions, in their vocabulary. Write down the word they use instead of Opportunities.
2. Set up HighLevel’s layer. Create the pipeline, choose stage colors as a scale, and set the card fields and counters for each role with Manage Fields.
3. Check contrast for every stage header and switch to darker shades or dark text where white text falls below 4.5 to 1.
4. Preview the brand layer in the free builder: header shape, card style, accent color and, if you need it, a renamed menu item.
5. Install on one sub-account first, test a long pipeline with a limited-permission user, then roll out to the rest of your clients.