All ideas

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

Some dropdown menus appear when hovering on the target button and others appear on click. Dropdown menus appearing on click is the standard pattern.

When used together, some primary buttons appear to the left of the secondary button, others appear to the right. Primary button should be placed to the right of the secondary button.

Modal usage inconsistent. Sometimes forms open as new screens (e.g. add data access role) and sometimes in modals (e.g. add report).