kibana
kibana copied to clipboard
elastic
[Dashboard] Link to editors in read-only mode
Problems: We want to solve two different problems in this issue:
- When users have read-only access to dashboards they cannot manipulate visualizations to run their investigations or even see their configuration (dataviews and fields used, formulas, etc.). This is always the case with "Managed" dashboards.
- When users have edit access but the dashboard is in view mode, they need to first realize they are in view mode, then click "edit" on the dashboard, open the visualization menu and click "edit" again, making sure they don't forget to cancel any accidental changes. This is a lot of clicks and cognitive overload.
Solutions:
-
When users have read-only access, we will allow them to view and configure visualizations, but they won't be able to save these changes.
-
When users have edit access, we will allow them to configure visualizations just by clicking in the panel menu in order to save clicks and cognitive overload.
Out of scope We are not solving for now the need of users that just want to see the configuration of a visualization in view mode without entering in edit mode. We consider this is a minor use case and addressing it can do more harm than good. We assume that most users will want to save their changes so not allowing this can cause confusion and frustration.
This should be fairly easy to implement at the Dashboard side, but on the editor side, what should the user have access to in a view-only mode of the editors. Do we allow them full access to the editor (within their user privileges) but block them from saving any changes made and only return to the dashboard? So instead of Save and Return, we'd have only Return to dashboard.
This would require changes in all the editors to allow a return only workflow. Is this worth exploring?
I would also like to click on a visualisation in a managed dashboard. Open the Lens editor, as I know it. This would allow me to understand what fields are used, what calculation type. I don't need to edit it there. Since I am already in Lens I could also copy the visualisation to my own custom dashboard.
Agreed. This is particularly useful for managed dashboards where I just want to know how a panel was created (maybe so I can make something like it elsewhere) but I'm not ready to do a full: clone > edit > inspect > delete the copy workflow. Some way to just view the panel configuration would be great. That could be in Lens or elsewhere even.
To make the scope more manageable, what about just solving this for the managed dashboard case and Lens visualization panels?
The latest design mockups for this issue have been crafted and are ready for handoff to engineering. Some key screenshots from the mockups can be found below. Please view the full Figma document for all mockups and developer notes.
After initial draft I realized this is heavily conflicting with embeddable refactor for Lens, so we'll wait with working on this issue till https://github.com/elastic/kibana/pull/186642 is merged.
