Feature Ideas

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

Currently if you have a new code version, you need to go in and re-publish each Embeddable individually. It would be super useful to be able to do this in bulk

Queries against your database (especially warehouses like BigQuery and Snowflake) are expensive, and so, if a dashboard can perform a single query to get the data needed to populate multiple charts, this would significantly reduce the cost of a dashboard. Note: This is different to pre-aggregations, which load data pre-emptively and keep them refreshed. This is instead about requesting data from the database on-demand, but reducing the number of necessary queries to do so.

When a dataset is pre-selected in a template component, filter/sort/limit options become unavailable after the template is used. If the dataset is left unselected, filtering is available - but this adds an unnecessary step for end users. The request is to support both: pre-selecting a dataset in the template AND allowing users to filter on it post-use.

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.

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