Feature Ideas

Currently the table size is set based on the size of the container for the table component, which works when there are more rows than the size of the table container, but if there are fewer rows, the container is not responsive - i.e. doesn't shrink to fit the number of rows being shown.

Add version visibility to the main Embeddables (Dashboards) list view by displaying the selected: Model version Components version Cube version for each dashboard directly in the list screen. Currently, users must drill into each dashboard individually to determine which versions it is pointing to. This creates friction when managing multiple dashboards, validating deployments, debugging inconsistencies, or preparing releases.

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

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

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 the custom canvas in Embeddable can be enabled to give end users the ability to build their own dashboards. However currently it's not possible to provide a 'starter canvas' or template for end users to clone / customise for themselves. This would be a really helpful addition so users don't start from a blank canvas.

Currently in custom canvas, when you enable users to select measures/dimensions for their charts, they will have access to all measures and dimensions are available via joins to the data model used. It would be great to have functionality in the UI to allow you to manage which are visible to the end users.

Specifically, it would be great to support translation for buttons like 'Add a chart' and anywhere there is text in the end-user custom canvas flow.

You may want to ensure that your Embeddables are only being embedded on your own website. This ticket is to prevent use of a tokens on domains not whitelisted by you. Note: this is quite difficult for an attacker to do anyway, as they won't have your API key, so would need to take generated tokens, which will be linked to them, and then embed them in their website before the token expires. And the embedded dashboard will only have access to data that the attacker themselves has access to anyway.

Currently security tokens are valid until they expire. Sometimes you want to add a "logout" flow or "invalidate all tokens" flow to your app, and so an API in Embeddable to invalidate tokens would be super useful

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.

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

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.