Feature Ideas

End-users can ask questions about data in natural language, and edit self-serve analytics dashboard with the help of AI.

It would be great to be able to have a 'bulk export' button that could pull the underlying csv for all the charts on a particular dashboard and export that

Problem Statement: Dashboards with extensive filtering capabilities currently require all filter components to be permanently visible, creating cluttered interfaces that can overwhelm end users. There's no native way to show/hide filters based on user interaction or dashboard state. Use Case: I'm building analytics dashboards with 10+ filter options. Primary filters (date range, main category) need immediate visibility, while secondary filters (sub-categories, advanced options) are only relevant after initial selections are made or for power users. Displaying all filters simultaneously creates a poor user experience, especially on smaller screens. Requested Feature: Add conditional visibility controls for components in the no-code builder, specifically: Toggle-based visibility - Show/hide components via button/link interactions (e.g., "Show advanced filters" button) Variable-driven visibility - Show/hide components based on variable values or states Collapsible sections - Group related filters into expandable/collapsible containers Default state configuration - Set whether components are initially visible or hidden Expected Benefits: Cleaner, more intuitive dashboard interfaces Better mobile/responsive experience with progressive disclosure of options Reduced cognitive load for casual users while maintaining power-user functionality More flexible dashboard layouts without requiring custom component development

Wouldn't it be amazing if there was a copy/clone button close to the Edit and Delete ones 🥺

Sometimes a part of a dashboard only makes sense to show once the user has selected an input.

End users can download their dashboard as a PDF

To make building dashboards in the no-code builder easier, we'll introduce the concept of 'containers' to layout components on the canvas

Something to ease a component prop migration, or to create a template in case we go into the hundreds of dashboards. E.g. a basic import/export JSON endpoint to configure an Embeddable

Currently dataset filters all use simple AND across each filter. It is, however, common that you might want to use OR instead, or a nesting thereof.

Make it easier for Embeddable builders to organise their Embeddables using folders.

It would be useful to be able to clone a dashboard from the live workspace to local dev preview so that it could be worked on locally

Enable users to schedule Embeddable delivery via email/Slack/Teams etc.

An API for retrieving the metadata for a published Embeddable dashboard: The canvas layout (position and size of each widget)The component values (input values and types for each of the component inputs)etc. E.g. GET https://api.embeddable.com/api/v1/embeddables/{embeddableId}

Be able to manage your user permissions within your team on Embeddable, for example limit who is able to publish a dashboard, who is able to push code to Embeddable. Also called RBAC (role-based access control).

Like this (https://restpack.io/html2pdf) but specifically for your embeddable dashboards