All ideas

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.

Interaction between data access and row level security permissions is unclear, feels very technical.

The menu items accessible from the top right menu is different depending on if the user is in Preset manager or Superset. Actions available from this menu position (global) should remain persistent throughout the entire experience.

Example from Google Data Studio:

Ability to focus elements using keyboard (TAB, SHIFT+TAB, etc.) is inconsistent throughout the application.This is an accessibility issue that makes our product unusable for those unable to use a mouse to interact with the interface. It is also a ...

Some links open screens in same tab (refreshes page with new content), and others open screens in new tab. Need an understanding of user flows and guidelines around how to open links.

Title case (The Quick Brown Fox Jumps Over the Lazy Dog) vs. sentence case (The quick brown fox jumps over the lazy dog) in menu items, field labels, etc. is inconsistent throughout the product. Capitalization guidelines exist for the product: htt...

Some menus include icons next to menu labels (first attachment) and some do not (second attachment). Icon usage in a menu should be intentional (draw the eye to commonly accessed menu items when a menu is long).