Multiple 'default.xml' Navs - specify which user gets what

[ARothman]

In the Splunk environment I am setting up, I have a group of AD users in an AD group called SplunkAdmins and SplunkUsers, using LDAP binding. What I want to have is two navigation menus for the same application, one that contains menus which the SplunkAdmins see and separate one which the SplunkUsers see. The purpose of this is to segregate what information/dashboards/saved searches are available to which group.

The original default.xml is being used for the SplunkAdmins and I have already set up a second default.xml that would be a base template for the SplunkUsers. When creating the second default.xml, it is saved under my user account in C:\Program Files\Splunk\etc\users\%user%\%app%\local\data\ui\nav.

Is there a way to set it up so that every new user that is created has this nav folder / default.xml added to their profile? I'm basically trying to accomplish what Windows OS does in the default user profile.

The hard way around this would be to make sure the administrators of Splunk always copy/paste this folder structure / file into the newly created profiles, but that isn't ideal. Ultimately, it would be best if I could make it so that, when a profile is made for a new user specifically in the SplunkUsers AD Group that, they will receive this secondary default.xml.

[Drainy · Accepted solution]

WOuldn't an easier solution simply be to set the permissions per view instead?
Only the views which a user/group has access to will be displayed in the nav, then you just have an all encompassing nav for all dashboards.

http://docs.splunk.com/Documentation/Splunk/4.3/User/CreateSimpleDashboards#Change_dashboard_permiss...

[Drainy]

Definitely 🙂

[ARothman]

Ah, okay... you're right. What was keeping the navigation menus was the in my default.xml.

With those dividers, the problem still exists though. What I'm playing around with right now is creating a new nav and making it readable only to the group I want to use it.

Edit: After trying to accomplish ^this and reading http://splunk-base.splunk.com/answers/37926/multiple-defaultxml-navs-specify-which-user-gets-what & http://splunk-base.splunk.com/answers/8037/can-an-app-use-multiple-navigation-menus I've decided to just dump the dividers in my navs. Functionality > formatting

[Drainy]

Not quite. if a user does not have access to a view it also prohibits it from displaying on the navigation xml as well.

[ARothman]

Unfortunately, this is not a solution. The "SplunkUser" group would still be able to see all of the drop-down menu items due to the default.xml nav, but the drop-down menus would be empty. Granted, this removes their access to it, but the purpose of this is to streamline their navigation view in the application. I may not have made this clear in my original post.