Feature Ideas

Drilldowns are super helpful for end users, so being able to add them within the no-code builder is really important - e.g. by opening a sub-embeddable via a modal.

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).

Currently in custom canvas, your end-users can customise and define the charts they want to see on their dashboard, but they cannot define filters. It would be nice if they could do the full dashboard-build process including building and selecting filters and linking them to the relevant charts that they want to filter within their custom dashboard.

It would be great to be able to add tooltips to the Remarkable components so that, from the builder UI, guidance could be added for end users.

E.g. Sometimes you have analysts who work on customer dashboards, but somebody else should have responsibility to review/approve and publish the dashboard to customers

It would be nice to be able to add a variable to the limit functionality. Then you could have a number input or similar so that end users could type in '5', '10' and then it would update the limit, and showing them the 'top 5' or 'top 10' results

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

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

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.

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}