Security

Navigation Menu Default.xml Default View Cascading for Permission Restricted View

fsolercasanova
Explorer

What is the expected behavior for setting multiple default views in the default.xml navigation menu?

<nav search_view="search">
    <collection label="DefaultViews">
        <view name="permission_restricted_d1" default='true' />
        <view name="unrestricted_d2" default='true' />
 </collection>

The documentation has a case where multiple defaults are set in the same app and collection implying some sort of expected behavior.

In practice, restricting a users access to permisson_restricted_d1 causes a 404 error and does not cascade to unrestricted_d2.

Is this a known issue and/or is there a workaround available that would not involve creating a new app with alternate navigation to the same resources?

0 Karma
Get Updates on the Splunk Community!

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...