Best practice on Dashboard Deployment to Users

[lehrfeld]

Hello fellow Splunkers!

I am curious about how all of you make your dashboards available to a wide range of users? This is not really a question about permissions (we currently have authentication via AD) or limiting what data users see in a dashboard... but the process that you go through to publish a dashboard.

Right now, our users login Splunk and we direct them to the Search App -> Dashboards. They then see ALL of my dashboards - most of which are in various stages of development.

What I would like to do is have a user log into Splunk and have them only see the dashboards they need.

Any discussion would greatly benefit me and hopefully others.

Thanks!

Mike

[splunker12er · Accepted solution]

Answers to all your doubts fall under setting up permissions:

If you want the users not to view some of the dashboards that are yet to be desiged, select the view -> Remove READ & WRITE permission for that user role.

If you wanted , you may also create a separate app and develop all the views (dashboards) that you wanted to design, simple don't allow the other USER ROLES to view that app. (which is better idea)