70 posts tagged with "new-feature"

Organization-level AI Memory will let admins promote useful insights from individual users' AI memory up to the organization level — surfacing suggestions to improve the semantic layer and dashboards based on real usage patterns.

Today, AI memory is per-user: what one analyst teaches the AI stays with that analyst. Promoting it org-wide means the whole team benefits. Over time, AI gets smarter for everyone, grounded in how your organization actually analyzes data.

AI Usage Analytics will give admins visibility into AI adoption across the organization: who is using AI, what types of questions get asked, and how usage trends over time.

This helps you measure ROI, identify training opportunities, and understand which teams get the most out of AI — so you can double down where it's working and unblock teams where it isn't.

Custom embedded app theme is planned for the Embedded Portal. Admins will be able to fully customize how Holistics looks inside their host app, matching brand colors, dark mode, and visual identity across the entire embedded experience.

Previously, embedded Holistics always rendered in light mode regardless of the host app's theme or brand colors. Now you can pass visual context via the embed payload and Holistics will adapt accordingly.

What's included:

• App theme: Configure colors for UI elements inside the iframe (navigation bar, dashboard header, AI panel, etc.) via embed payload
• Dashboard theme: Dynamically apply a pre-configured dashboard theme to all embedded dashboards via embed payload

Data apps are coming to Holistics. Build tools a dashboard can't, like a purchase-planning calculator or a what-if view, with full control over the layout, interactions and logic, while every number stays governed.

Why this matters​

Some needs go beyond what dashboards are built for. Data apps give you the freedom of custom code with the same trusted numbers and permissions as the rest of Holistics.

What's coming​

• Fully custom: design any layout, interaction or logic with HTML, CSS and JavaScript.
• Build with code or AI agents: write it in the editor with a live preview, or let an AI agent build it.
• Governed numbers: every query goes through your semantic layer, and builders can inspect the AQL and SQL behind it.
• Governed access: share an app like a dashboard, and every query runs as the viewer, with their dataset access and row-level permissions.

Learn more about data apps.

Timeline​

The first version of data apps is expected in November 2026.

Ask Claude to export a dashboard you built on Holistics data through the Holistics MCP server, and it's imported into Holistics as a data app. Your team can open and share it like other reporting, and every query runs live with each viewer's permissions.

Learn more about importing Claude dashboards.

Timeline​

Importing Claude dashboards is expected in November 2026.

Localization for embedded analytics is coming to Holistics. You build a dashboard once, add translations for each language, and each embedded viewer sees it in their own language.

Why this matters​

If your customers speak different languages, they expect their dashboards in their language. Today, the only way to do that is to build and maintain a copy of each dashboard per language, which breaks down as you add languages.

What's coming​

• System texts: buttons, menus, and error messages are translated by Holistics.
• Dashboard texts: titles, text blocks, and field labels are translated from translation files you keep in your AML project (settings/locales/fr-FR.json).
• Data values: H.current_locale lets you pick the right translated column from your database in AQL.
• One setting per viewer: pass settings.locale in the embed payload, and Holistics applies the right translations for that viewer.

Learn more in Localization for embedded analytics.

Timeline​

Localization for embedded analytics is expected in November 2026.

Period-over-period comparison is now in the Analyze menu on dashboard charts. It sits alongside reference lines and trend lines.

How it works​

Open the Analyze menu on a dashboard chart and select Time comparison:

• Use Quick mode to apply the comparison across the whole chart in one click.
• Use Advanced mode if you want a different time comparison for each metric, or to change the date field.

Every analysis in the Analyze menu works the same way:

• Temporary and only for you: Like filters, analyses you add apply only to your view and aren't saved to the chart.
• Included in widget exports: Widget exports include the analyses you added. Dashboard exports don't.
• Continue in Explore: If you open Explore, your analyses come with you so you can keep refining them.

Supported charts​

Time comparison needs a date to compare by. It can come from the chart itself or from a date filter (a dashboard filter or the chart's own condition).

Charts with a date field:

• Line, area, column, combination, and bar charts
• Tables and pivot tables
• Metric sheets

Charts without a date field, when a date filter is applied:

• Radar charts
• Bar and column charts with a categorical axis, like revenue by country
• Tables and pivot tables

KPI metrics aren't supported yet and will come in a later release.

AI chat notifications are now available in Holistics AI. You get notified when a conversation needs your attention, so you can work on something else while long tasks run.

Why this matters​

Some AI tasks take a few minutes to run. Switch to another tab and you won't know when AI is done, or that it has been waiting on your answer the whole time.

What's included​

• Three triggers: you get notified when AI chat needs your input, finishes, or fails.
• Two notification channels:
  • Tab indicator: the Holistics tab title shows a marker when a conversation needs your attention. On by default.
  • Browser notifications: get a popup even when you're in another app. Off by default.

Get started​

Turn on browser notifications from the banner above the AI chat input, or go to User settings > Browser notifications > AI chat.

Learn more in Manage browser notifications.

Admins can now customize Home for everyone in their organization. Show your most important dashboard in full view right on Home, pin others as buttons, and choose which sections appear, in the order you want.

Why this matters​

Many teams build a "start here" dashboard, like a KPI overview, a report glossary, or an onboarding page. But it sits one click away from Home, so occasional users rarely find it. Custom homepage puts it where everyone lands.

What's included​

• Pinned dashboards, in full view or as buttons: Show one Canvas dashboard in full view, so users can filter, drill, and explore it without leaving Home. Pin any others as buttons that open them in one click. Dashboards you've already pinned stay as buttons.
• Section control: Show, hide, and reorder Home's sections: Pinned dashboards, Recents and favorites, and Browse.
• Permissions apply: Everyone sees pinned dashboards with their own permissions and row-level access. Users who don't have access to a dashboard won't see it on Home.

Get started​

Go to Admin settings → Custom homepage to set up your sections and pinned dashboards. Pinned dashboards need to be in the Public Workspace.

Learn more in Custom homepage.

Dashboard viewers can now hover over a column header in a table or pivot table and see a viewer-facing description of the field. This includes viewers on shareable and embed links.

🔍 Why this matters​

Previously, field descriptions were only visible in Explore's field selector. Business users rarely opened it, and users on shareable or embed links couldn't open it at all, so the context analysts wrote never reached the people reading the dashboard.

Showing semantic-layer descriptions as-is isn't always safe either. The same description is often written for several audiences at once (AI, other analysts, business users), and can contain technical details or internal notes that aren't meant for clients.

💡 What's new: viewer-facing descriptions​

To solve this, we've introduced the viewer-facing description: a description on each field in a table or pivot table, written for the people reading your dashboards and kept separate from the semantic-layer description:

• Semantic-layer description: written in your models, visible only to users with dataset access, same as today.
• Viewer-facing description: what dashboard viewers see in the tooltip. Always visible to anyone who can view the dashboard.

💼 What analysts can do​

You decide where each viewer-facing description gets its content from:

• Inherit from the semantic layer: if your semantic-layer descriptions are already written for business users and are safe to show to external viewers, turn on "Inherit field descriptions" in Project Settings. Every viewer-facing description then inherits its content from the field's semantic-layer description, so you don't have to write them again for viewers. You can also make exceptions for specific fields:
  • Force inherit: if only a few descriptions are ready for viewers, keep the project setting off and turn on inheritance for just those fields.
  • Don't inherit: if a few descriptions contain internal notes or technical details, keep the project setting on and turn off inheritance for just those fields.
• Write a custom description: when a field shouldn't inherit, write business-friendly text for it on the visualization instead. The semantic-layer description stays untouched.

✏️ Good to know​

• Default setting: for existing projects, "Inherit field descriptions" is off, so your dashboards look the same until you turn it on or add custom descriptions. New projects start with it on.
• Configuration: the project setting is available in Project Settings. Field-level overrides and custom descriptions are configured in AML.
• Empty descriptions: if a field has no inherited or custom content, no tooltip is shown.

Learn more: Viewer-facing field descriptions