Open rayafratkina opened 3 years ago
Pinging @elastic/kibana-presentation (Team:Presentation)
Pinging @elastic/kibana-app (Team:KibanaApp)
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.
Problems: We want to solve two different problems in this issue:
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 --> solution definition WIP and it will be a separate issue.