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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...

Enriching Signals with the OTel Lookup Processor

Introduction Raw telemetry is often incomplete. A log line might record an IP address, but what you really ...

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...