@elibrumbaugh, Certainly! Check out some of the recordings from above as well – it followed the idea of the toggle being front and center and also serving as the indicator which is something we discussed briefly on Friday.
## Toggling the Published Status of a Dashboard #### (The logged in user is "Admin User" in this example)  Note a few things: 1. This user has the "all_datasource_access" permission so they can see all of the dashboards in the system. 2. One can only change the publish status by putting the dashboard into edit mode. ## Not being able to toggle the status #### (The logged in user is "Gamma User" in this example)  Note a few things: 1. The user cannot see the dashboard titled "No datasources for gamma" from the previous image. This is because this user doesn't have access to any of the datasources backing the slices used in the dashboard. 2. The user can see the dashboard they do because it is published AND they have access to at least one slice. 3. The option for publishing a dashboard does not appear for this user Some of the design considerations we discussed are as follows: - Publishing a dashboard is essentially the same as putting a dashboard into production right now so we need to make sure the visual weight of the action is reflected appropriately in the design of the feature - This feature needs to be discoverable and have appropriate verbage that makes it clear how discoverable and visible the dashboard is. Perhaps public / private might be a more clear distinction for what this feature does. [ Full content available at: https://github.com/apache/incubator-superset/pull/4725 ] This message was relayed via gitbox.apache.org for [email protected]
