All ideas

There's a hierarchy among databases, datasets, saved queries, and query histories but they all display as flat within the data CRUD views – consider adding additional layers of navigation to communicate hierarchy and relationship.

When launching Explorer from dataset, there's no indication that the user has launched Explorer and is now creating a chart. User may expect dataset options to open instead of Explorer.

Dataset schema not defined in product or documentation. Unclear what to do when creating dataset.

In CRUD table views, some row actions appear on hover, some appear when inactive (saved SQL queries). Additionally, revealing actions on hover may not be the most discoverable pattern.

Might be useful to display number of results and pagination at the top of the CRUD list in addition to the bottom, will let user understand and navigate results set faster.

Currently, the filter options in the CRUD table views are not dependent on the objects in the table. This allows users to apply irrelevant filters and get into a null data set. Filter options should only be available to the user if a relevant tabl...

CRUD views are missing the ability to clear all applied filters.

The add report modal that's accessible from the global settings menu is confusing – layout, fields, and selections are unclear and overly complex. Could reconfigure the layout and hide some options under an "advanced" section.

The add alert modal that's accessible from the global settings menu is confusing – layout, fields, and selections are unclear and overly complex. Could reconfigure the layout and hide some options under an "advanced" section.

Data access role and row level security crud views are different than the rest of the CRUD views in the app. Update to new CRUD views for greater functionality and consistency.