How to Customize Pipeline Stage Colors in Opportunities

Modified on: Thu, 23 Apr, 2026 at 4:29 AM

Pipeline stage colors in Opportunities make it faster to manage pipelines and easier to visually scan deals at a glance. This article shows how to create and edit pipelines directly from the Opportunities pipeline dropdown, customize stage colors, and control how those colors appear across Kanban, List, and record views.


TABLE OF CONTENTS


What is Pipeline Stage Colors in Opportunities?


Pipeline Stage Colors is an enhancement to the Opportunities area in HighLevel that streamlines how you access and manage pipelines, while adding powerful visual stage coloring. Instead of jumping into Settings to create or edit a pipeline, you can do it directly from the pipeline dropdown in Opportunities and you can assign colors to each stage that display consistently across views.


Stage colors can be configured per pipeline and then displayed as a small colored dot or as a full background tint, helping your team quickly identify where each deal sits in your process.

Key Benefits of Pipeline Stage Colors in Opportunities 

This feature is designed to reduce clicks and increase visual clarity so teams can work faster in Opportunities. Understanding these benefits helps you decide how best to configure your pipelines and standardize visual cues across your organization.

 

  • Faster pipeline management from Opportunities: Create or edit pipelines directly from the pipeline dropdown no need to leave the Opportunities view or navigate through Settings.


  • Consistent visual language across views: Stage colors appear in Kanban (board), List view, opportunity cards, and record details so stages look and feel the same everywhere.


  • Improved scan-ability of deals: Colored dots or background tints make it easier to quickly scan a column or list, spot priorities, and identify bottlenecks.


  • Shared configuration for the whole team: Colors are configured at the pipeline level, so everyone sees the same palette, keeping your CRM visually consistent.


  • Plays nicely with other visual tools: Stage colors layer alongside features like smart tags and custom opportunity card layouts, giving you richer visual context per deal.

Pipeline Dropdown Navigation in Opportunities

Streamlined pipeline navigation lets you create and edit pipelines from the same dropdown you already use to switch pipelines. This reduces context switching and makes on-the-fly pipeline adjustments much easier for admins and sales leaders.

 

When you’re working in Opportunities:

 

  • The pipeline dropdown at the top of the view now includes:


  • A “+ Create Pipeline” action to create a pipeline instantly


  • An edit option under three dots menu next to each pipeline to update its configuration 


  • These shortcuts mean you can refine your pipeline structure without leaving the page where you’re actively reviewing or managing opportunities.


  • Your ability to create or edit pipelines still depends on your user role and pipeline permissions, so some users may see the dropdown but not edit options.

Stage Color Customization

Stage color customization allows you to assign distinct colors to each stage within a pipeline, giving your team a shared visual code for different steps (e.g., new leads, hot deals, onboarding). Thoughtful color choices make pipeline reviews faster and more intuitive.

Key concepts:

 

  • Colors are assigned per pipeline: Each pipeline can have its own set of stage colors, matched to that pipeline’s purpose.


  • Every stage can be colored: You can choose colors for standard stages (including your own custom stages) to align with your sales or service process.


  • Color settings are shared: Once configured, all users who can see that pipeline will see the same colors, ensuring a unified visual experience across the team.

Stage Color Display Options

 

Display options control how your chosen colors appear in the UI, letting you balance subtle cues (dots) with stronger emphasis (background tints). Selecting the right style helps you avoid visual clutter while still making stages stand out.

 

You can choose between three display styles: 

 

  • Default (no color):
    • Uses the standard HighLevel look with no added stage colors.
    • Ideal if you prefer a minimalist UI or are just getting started with pipelines.


  • Colored dot:
    • Shows a small colored dot next to the stage label or opportunity, giving a subtle visual cue without changing the entire card or row.
    • Great when you want color indicators but maintain a neutral background.


  • Background tint:
    • Applies a soft background tint for the stage color on cards and/or rows.
    • Best for teams that want more vivid visual segmentation across stages and quick “at-a-glance” recognition.


You can adjust these styles at any time from the pipeline’s stage settings.



Where Stage Colors Appear in Opportunities

 

Stage colors are most effective when they appear consistently across your CRM views. This feature ensures that your color choices follow the opportunity wherever you’re viewing it, so your team can rely on the same visual meaning everywhere. 

 

Once configured, stage colors appear in:

 

  • Kanban (Board) view:
    • Cards in each stage column show either a colored dot or tinted background, helping you instantly read the flow of your pipeline.


  • List view for Opportunities:
    • Stage colors appear alongside opportunities in the tabular view, giving you both dense data and visual stage cues in the same screen.


  • Opportunity cards and record details:

Individual opportunity views and contact details surfaces will respect the stage’s color, helping you spot the deal’s position in the pipeline even when you’re away from the main Kanban. 

 

Because these visuals are pipeline-level settings, every user with access to that pipeline benefits from the same, consistent color scheme.



How To Setup Opportunities – Pipeline Navigation & Stage Colors

Proper setup ensures that your team can quickly adjust pipelines from Opportunities and use colors in a way that supports your actual workflow. The steps below walk through enabling navigation shortcuts and configuring stage colors for one or more pipelines.


Open Opportunities - Pipeline Menu


To get started, navigate to the Opportunities area from your sub-account by selecting Opportunities in the left-hand sidebar. Once you’re in, switch to the Pipelines tab at the top of the page. From here, you can easily create a new pipeline by clicking the + Create Pipeline button located in the top-right corner. 


This allows you to set up and manage your pipelines without leaving the Opportunities section, making the process faster and more streamlined.




Create Pipeline


Click the + Create Pipeline button to quickly set up a new pipeline without leaving the Opportunities view. Use this when you need to organize deals into a new process (e.g., a separate pipeline for renewals or onboarding) so your workflows stay structured and easy to manage.




Edit Existing Pipeline


If you don’t need to create a new pipeline, you can alternatively update an existing one by clicking the three-dot (⋮) menu next to the pipeline and selecting Edit. This is useful when your process already exists and you simply want to refine stages, update probabilities, or apply stage colors.



Pipeline Name


Enter a Pipeline Name that clearly reflects its purpose (e.g., “Sales Pipeline” or “Client Onboarding”) so your team can easily identify and switch between pipelines. 


Use the Opportunity-level probability toggle if you want each deal to have its own probability (useful for custom forecasting), or leave it off to follow stage-based probabilities for a more standardized approach. 


Stage Color


Stage Color Options let you control how visual cues appear across your pipeline, helping your team quickly understand deal progress and prioritize work. By selecting the right display style, you can balance clarity and simplicity based on how your team reviews and manages opportunities.


Assign a color to each stage to visually represent its meaning (e.g., green for won, red for risk, yellow for follow-up). 


Default (No Color)


This option keeps your pipeline clean with no visual color indicators applied to stages. Use this when your team relies more on filters, tags, or detailed data rather than visual cues. It works best in simple workflows where color is not needed to interpret deal progress.



Colored Dot


This option adds a small colored dot next to each stage to provide a subtle visual indicator. Use this when your team works with list-heavy views and needs quick stage identification without overwhelming the interface. It’s ideal for maintaining a clean layout while still adding a layer of visual context.



Background Tint


This option applies a soft color tint to the entire stage row or card, making stages highly visible. Use this when you need to quickly scan pipelines, identify priorities, or manage high volumes of deals. It’s especially useful for sales teams that rely on fast visual recognition during pipeline reviews.





Verify permissions and rollout to your team (optional but recommended)


If you’re an admin, review pipeline permissions so only the right users can modify pipeline structures and stage colors, while others still benefit from the visuals.


Communicate your color conventions (e.g., what each color means) so your team interprets the visuals consistently.

Refine over time.


Monitor how your team uses the colors and adjust as needed.

If you introduce new stages or processes, update colors to keep your visual language coherent.

 

For step-by-step guidance on broader pipeline configuration (beyond color and navigation), refer to “Step-by-Step Guide: Creating Pipelines” in the HighLevel knowledge base.

Frequently Asked Questions 

Q: Do stage colors change based on the user, or are they global?
Stage colors are configured at the pipeline level and apply to all users who have access to that pipeline. Individual users cannot override stage colors for themselves.


Q: Can I use different color schemes for different pipelines?
Yes. Each pipeline can have its own set of stage colors and display style, so your sales pipeline, onboarding pipeline, and support pipeline can all use distinct visual schemes. 


Q: How is this different from Smart Tags or other color-based indicators?
Stage colors are tied to where a deal sits in your pipeline (the stage). Smart Tags are rule-based labels that apply color to opportunities based on conditions like value, age, or activity. Many teams use both: stage colors for process steps, Smart Tags for urgency or health. 


Q: What if I don’t want color at all in my pipeline?
You can set stages to Default (no color), which removes added coloring while keeping your pipeline structure intact. This is useful if you prefer a simple UI or rely more on tags and filters than on color cues. 


Q: Can all users create or edit pipelines from the Opportunities dropdown?
No. The ability to create and edit pipelines—whether from the dropdown or the Pipelines page—depends on user roles and pipeline permissions. Admins can restrict who can view and modify specific pipelines. 


Q: Do stage colors affect automation or reporting?
Stage colors themselves are visual only and don’t change how automations trigger or how data is calculated. However, they can make it easier to read dashboards and reports that are already based on pipeline stages. 


Q: Will stage colors appear on exported data?
Exports include the stage names but not the visual color styling. Colors are applied within the HighLevel interface, not in CSV or external files. 


Q: What happens to stage colors if I rename or reorder stages?
If you rename or reorder stages within a pipeline, the associated colors move with those stages. The visual configuration remains attached to the stage itself, not its position on the screen. 






Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article