Great minds think alike

I’m submitting this as an accessibility issue, not a cosmetic preference. Recent UI changes in the internal agent web interface (Tickets / Help Desk / Conversations) introduced blue/teal text on a white background. This creates a health-related accessibility barrier, as it triggers migraines and significant eye strain and affects my ability to work safely for extended periods. Important context: System-level blue-light filters (e.g., Night Shift / Night Light) do not help and actually worsen eye strain by reducing clarity and increasing visual fatigue. The only effective solution for my light sensitivity and migraines is a true dark interface (black or near-black background with light text), which I use successfully across other tools. Text color itself is a major trigger — certain hues (including blue/teal on white) significantly increase eye strain. Mobile app dark mode is not a viable workaround due to high ticket volume and the need for full web-based workflows. Currently, the internal agent web UI does not offer: A dark mode or high-contrast theme User control over background color User control over text/letter color The ability to adjust contrast in a way that accommodates light sensitivity and migraine triggers This creates an accessibility barrier for agents with light sensitivity, migraines, and visual processing conditions. While contrast ratios may technically meet minimum guidelines, accessibility also includes user-adjustable presentation, especially when specific color combinations cause adverse physical effects. Request: Please add one or more of the following for the internal agent web interface (Tickets / Help Desk / Conversations): A true dark mode A high-contrast or low-glare theme User-controlled theming, including the ability to adjust: Background color Text/letter color Overall contrast Providing control over both background and text colors would allow agents with different accessibility needs to configure a workspace that does not cause physical harm or limit their ability to work. This would align HubSpot with modern accessibility practices and with other enterprise tools that support agents with light sensitivity and migraine-related accessibility needs. Thank you for considering this from an accessibility and health-impact perspective. ...read more

HubSpot should provide a way to customize category slugs so users have proper control over language switching. Alternatively, they should offer a mechanism—similar to language_variants('localized') for standard pages—that allows developers to retrieve localized category URLs for multilingual implementations. Because currently, implementing a language-switch to a KB is a hastle. ...read more

We need the ability to append custom single-line and multi-line text values when merging records or in a workflow (where the "append" option is missing).   As an agency, we use the a custom text property to house Partner IDs for our brands inside different PRMs, but we often run into the case where major publishers, such as SoftwareAdvice, have multiple IDs; since we use it as a unique identifier, this creates duplicates that, when merged, remove the alternative IDs that we need to see.   Our publishers sometimes have dozens of Parner IDs that we need to keep track of and see inside of one company record. Reviewing the property history and manually adding them just isn't feasible.   Currently, the only solution is to download our duplicate companies every week or two and append the values in a spreadsheet, then import them back into the system and proceed to merge the duplicate records.   Neither of these "solutions" are what you'd expect from a professional CRM like HubSpot, and we need a better way.   It would also be nice if there was a possibility to retrive and append values from a properties history in a workflow as well. ...read more

Summary Please add support for filter logic on dashboards that allows a property to be “one of these values OR is unknown/empty,” consistent with what’s possible in report and list filters. Right now, dashboard-level filters only let us choose a single operator per property (for example, is any of or is unknown), and they’re combined with report filters using AND logic. There’s no way at the dashboard level to express: Property is any of [Value A, Value B, Value C] OR Property is unknown Why this matters This limitation forces us to choose between: Excluding empty values entirely (by using is any of), or Including only empty values (by using is unknown), or Building extra report variants with custom OR logic and avoiding dashboard filters for that property altogether. In reports and lists, we can build this logic using advanced filters and OR groups (for example, one group for “Property is any of [X, Y, Z]” and another group for “Property is unknown”). We’d like dashboards to behave the same way so: Filters are consistent across lists, reports, and dashboards. We don’t have to maintain multiple copies of the same report just to work around dashboard filter limitations. Non-technical users can safely use dashboard filters without accidentally changing the underlying logic of what’s included. Concrete use cases Some examples where we need “Value OR empty” on dashboards: Show deals where a custom segmentation/region field is one of our focus regions, plus deals where that field hasn’t been filled in yet. Show contacts where a custom lifecycle/fit field is one of certain tiers, plus contacts where the field is still blank (treated as “unclassified” but still in scope). Show tickets where a classification field is in a selected subset, or has not yet been classified (blank) so we can monitor items still needing triage. Requested behavior Ideally, dashboard filters would allow one or more of the following: An option on value-based operators like is any of / is none of to “include records where this property is unknown/empty.” The ability to create multiple filter groups with AND/OR logic at the dashboard level (mirroring the advanced filter builder in reports), so we can explicitly define: group 1 = “Property is any of [X, Y, Z]”, group 2 = “Property is unknown”, joined with OR. Quick filters that respect and expose this same logic in a user-friendly way. Impact This change would: Make filter behavior consistent across lists, reports, and dashboards. Reduce report duplication and maintenance overhead. Help ensure that users looking at the “same” filter logic in different places actually see the same data. Thank you for considering this—having consistent “OR is unknown/empty” logic at the dashboard level would make reporting more reliable and much easier to manage across the whole portal.     ...read more

Currently the deal split amount properties are not readable publicly. I'd like to use the deal split amounts in calulated properties but cant currently do this.  ...read more

Currently, HubSpot’s “Connect your LLM to custom workflow actions” feature supports OpenAI, Anthropic, Gemini, Cohere, and xAI. I’d like to propose adding Microsoft Copilot as an additional supported LLM provider. Many companies are deeply invested in the Microsoft ecosystem (Microsoft 365, Azure, Copilot) and cannot use external LLM providers due to compliance, data residency, or security requirements. ...read more

In the Breeze REcord summary it identies the owner by their numeric ID. Can it not identify them by Name? This would help clarity ...read more

I’d like the ability to set one of my existing record layouts as the default view for unassigned teams and users, instead of having to manually rebuild that layout under the “Default view” entry. Context: I’m using Record Customization for Deals. I have multiple layouts, for example: Generic view, Commercial, CC/FAS, etc. I want Generic view to be the layout that unassigned teams and users see by default. Right now, the only way to achieve this is to open Default view and manually copy all the tabs, cards, sections, and field order from Generic view. This is: Time‑consuming and error‑prone Hard to maintain if we later improve Generic view and want those improvements reflected in the default Requested improvement Please add a way to: Promote an existing layout (e.g. “Generic view”) to be the Default view, or Change which layout the “Default view” row points to, or Clone an existing layout into Default view with one click (preserving structure, tabs, cards, and field order). This would make it much easier to manage consistent record layouts across teams and for unassigned users, without duplicating work or risking misalignment between views. ...read more

Now that I am a Partner Admin to some of our clients, I realized that I am not able to do "high-risk" actions like CRM Manual Data Back Up and Knowledge Base Migration.  I checked with Support and these actions can be done only by a Super Admin.  I normally have to do this work for clients, now I have to request for a paid Super Admin seat to be able to do this. I believe the expectation is that a Super Admin is meant to action on more "high-risk" actions (like migrating the KB) since it's irreversible.   I think a good middle ground would be something like a Partner-requested, Admin-approved setup so there doesn't need to be a change or permissions. Tagging Product team cause I can see how this would make things a lot smoother. ...read more