Dashboards & Visualizations

Is the default=true in the xml definition for views valid for all users in Splunk?

skender27
Contributor

Hi,

I have this xml view for my Splunk:

<nav search_view="search">
    <view name="flashtimeline"  />
    <view name="monitor" />  
    <view name="details"  />
    <view name="tickets" default='true' />
    <view name="approvers"  />
    <view name="cr" />
    <view name="incidents" />
 </nav>

Is the default='true' value valid for ALL users who have access to the dashboard?
I am asking because I need to know how can I set different default (I mean like landing pages) dashboards for SPECIFIC users when they log-in in Splunk?

Thanks for any suggestions,
Skender

0 Karma
1 Solution

Raghav2384
Motivator

Hello @skender27,

First: App access/permissions has higher precedence (Example: If i have an app called XYZ which has permissions as read: admin, write: admin only) Though there are dashboards in that app with Read:, Write: , Folks who are not admins cannot get to the dashboard as it's not visible to them in the first place.

Second: default = true is nothing but when they click on that app, that's view/dashboard is what displayed right away. It doesn't mean that even if folks do not have access to that view can see it. If they do not have access to the view name="abc" and it that's the default view for that app, they would see an error (Page/View not found)

When you say different landing pages/views for different users, are you talking about same app with a different landing/view for different roles? I am not sure if that's even possible. It comes down to this, either you can see it or not see it.

Hope this helps!

Thanks,
Raghav

View solution in original post

Raghav2384
Motivator

Hello @skender27,

First: App access/permissions has higher precedence (Example: If i have an app called XYZ which has permissions as read: admin, write: admin only) Though there are dashboards in that app with Read:, Write: , Folks who are not admins cannot get to the dashboard as it's not visible to them in the first place.

Second: default = true is nothing but when they click on that app, that's view/dashboard is what displayed right away. It doesn't mean that even if folks do not have access to that view can see it. If they do not have access to the view name="abc" and it that's the default view for that app, they would see an error (Page/View not found)

When you say different landing pages/views for different users, are you talking about same app with a different landing/view for different roles? I am not sure if that's even possible. It comes down to this, either you can see it or not see it.

Hope this helps!

Thanks,
Raghav

skender27
Contributor

Thanks a lot!

Yes, I mean in the same app in Splunk.
I resolved it by removing the default tag at all and so users land on search when they access the app.

Thanks again,
Skender

0 Karma
Get Updates on the Splunk Community!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...