Opportunities & Pipelines

Opportunity Card – Fields & Folders (Needs Fixing Faster Than Two Rabbits in Mating Season)
Opportunities in GHL quickly become messy and unmanageable when using multiple Opportunity-type Custom Fields. Current folder behavior creates massive scroll bloat, forces irrelevant fields into every card, and slows down workflow for sales and service teams alike. This isn’t a small UX annoyance — it’s a structural flaw, and GHL should be red-flagging the fraq out of this issue with more intensity than two rabbits in mating season. Please fix ASAP. Related Idea: https://ideas.gohighlevel.com/opportunities/p/make-opportunities-make-sense-again GHL – Opportunity Custom Field UX Improvements MVP (Phase 1 – Quick Win) Collapsible Folder Section All Opportunity Custom Value Folders appear under a single collapsible “Custom Fields” section in the Opportunity Card. Default collapsed on load, with per-user remembered state (open or closed). “Expand All / Collapse All” button for fast toggling. Collapsing hides folder labels & all field rows from the DOM to improve scroll/load speed. Inline Field Search Search input at the top of the “Custom Fields” section. Filters live across all folders in that opportunity. Matches both field labels and values. Displays folder path in results (Folder > Subfolder > Field) so users know context. Pinned Fields Per-user ability to “pin” any Opportunity Custom Field. Pinned fields display in a “Quick Access” area above the main custom fields section in the Opp Card. Pins are user-specific and do not affect other users’ views. Core Improvements (Phase 2) Multi-Level Folder Support Support nested folders for Opportunity Custom Fields. Example: Job Assets > Photos > Final. Display as tree navigation or breadcrumb trail for clarity. Collapse/expand works at each level independently. Field & Folder Visibility Rules Admins can set folder/field visibility: Role-based (e.g., techs see only job site details, sales sees only pricing fields). Pipeline- or Stage-based (e.g., “Permit Number” shows only at “Pre-Install” stage). Hidden fields/folders do not render in the Opp Card but still retain stored values in the backend. Visibility rules editable in Settings > Custom Fields. Implementation Notes (Important for GHL Dev Team) This should only apply to “Opportunity” type custom fields — contact and company custom fields remain unchanged unless opted in. Folder structure & rules should be global, not per individual opportunity. Respect existing API behavior — any hidden field still returns via API unless explicitly filtered. Collapsible and pinned states should be stored in user preferences, not system-wide defaults.
0
Load More