Dashboard

Italian Translate error in Sites part In the Bar: "Siti" ok "Imbuti" to "Funnel" it's the same in italian "Blog" ok "Wordpress" ok "Portale del cliente" ok "Forme" correct to "Moduli" the rest it's ok

Need Full integration Option within the Media Storage settings UI that allows the Admin to "Connect" and also "Disconnect" and do it not just at the Drive level but needs to be at the Google Drive folder level. BIG ISSUE!!! as it puts agencies in LEGAL Jeopardy when problems happen. Like right now for me! Not in a happy place with GHL at the moment. I am experiencing a bug with the Google Drive Integration and GHL needs to resolve all this ASAP. Somehow a single sub-account's Google Drive Integration has populated to ALL my sub-accounts and customer's. They don't know how it happened and can't fix it. The platform is exposing one of my customers private proprietary files and sharing them to the world and I cannot do anything to correct. It's been over 24 hours and GHL support has not been able to resolve. Within the Media Storage UI GHL developers need to provide the ability to "Connect" and then also "Disconnect" / "Manage" the Google Drive integration within the platform at the Sub-Account level. AGENCY Admin/owner needs the ability to override and Not just on the Google Drive side.

When notifications are cleared accidently, cant be recovered.

Cannot forecast revenue for contracts/invoices with payment schedules. Right now I have no way of knowing what invoices to be paid this month, next month, etc. Seems to be an issue for only contracts/invoices with payment schedules as it puts them in the partially paid stage.

The widget template "Opportunity Revenue Over Time" is supposed to sum up "revenue" but it actually sums up "lead value"...which is quite a different thing. This needs to be fixed to actually report revenue. Thanks. p.s. all the opportunity widgets that are tied to revenue have the same problem.

Hi, for some reason i don't see Google Ads as a KPI, though I re-integrated my account, and tried across different client subaccounts

Currently, dashboards in Go High Level are restricted by the “Assigned Data Only” setting. While this setting is essential for limiting a salesperson’s access to only their assigned contacts, it unintentionally blocks their ability to view key sales KPIs on dashboards. This creates two conflicting issues: 1. Data visibility control: Salespeople must only work within their assigned contact list (best practice). 2. Dashboard metrics access: Salespeople need visibility into overall team KPIs to track performance and benchmark against peers. At present, enabling dashboards requires giving salespeople full access to all contacts—something that undermines security and focus. Disabling it removes their access to critical KPIs entirely. Proposed Solution: Add a simple toggle option at the dashboard level: “Allow unassigned data for dashboard metrics only.” • Salespeople would see aggregated KPIs (team totals, leaderboards, conversion rates, etc.) without gaining access to individual unassigned contact records. • Clicking into restricted data would either be disabled or blocked. Impact: Without this option, sales teams cannot see where they stand relative to peers—an essential feature in any CRM. This limitation reduces transparency, hinders motivation, and forces managers to manually share KPIs that should be visible in real-time.

For some reason, it appears the appointment numbers are including appointments previously booked by the subaccount, rather than only those booked by the Voice AI agent. This makes the reporting difficult to rely on. For example, the report shows 33 appointments booked from 8 Voice AI booked appointments. Therefore the total appears to include appointments not generated by the Voice AI agent. As a result, the data isn’t actionable and can discourage customers from using the reporting at all, even though significant effort clearly went into building it. For example, one particular sub was extremely unhappy about this and called the reporting useless. Related to this, it would be extremely helpful to allow reporting to be customized on a per-subaccount basis. Many subaccounts don’t use all available features, so the reports they receive often include sections that aren’t relevant to them, which adds confusion rather than clarity. Addressing these two items would make the reporting far more useful and increase adoption across subaccounts. Thank you for taking the time to consider this feedback.

Custom Object Date fields display correctly in the object list (e.g., 2025-11-13), but appear one day earlier in Dashboard widgets when using Daily breakdown. This only happens with Custom Object Date fields — not with CreatedAt or UpdatedAt. How to Reproduce: Create a Custom Object with a Date field (date-only picker). Add records with any date (example: 2025-11-13). Build a Dashboard widget: Metric: any number field View By: Date Breakdown: Daily Date Property: the Custom Object’s Date field View the chart in a non-UTC timezone (ex: US/Central). The dashboard plots the record under 2025-11-12, one day earlier. Audit Log Proof: Audit log shows the Date field is stored exactly as: { "properties": { "date": "2025-11-13" } } There is no time component, so the Dashboard renderer should not be applying a timezone shift. Expected Behavior: A Custom Object Date field stored as YYYY-MM-DD should appear on that same date in Dashboard charts, especially when using the Daily view. Actual Behavior: Dashboard internally treats the date as midnight UTC, applies timezone offset, and shifts it to the previous day (e.g., US/Central: −6 hours). It does not seem to occur with CreatedAt/UpdatedAt dates. Impact: All dashboards relying on Custom Object Date fields show incorrect day buckets for anyone outside UTC.

Please see the screenshot. This is happening quite often, on all pages. Why did this happen? I remember previously don't have this issue.