Getting Data In

Search Filters (srchFilter) when a user is in multiple groups/roles

gkanapathy
Splunk Employee
Splunk Employee

When a user is in multiple Splunk roles (possibly because they are assigned to multiple LDAP/AD groups that are mapped to Splunk roles), what search filter is applied to that user's searches? Is one just selected, and if so which one? Or are all the filters OR'ed together?

Is there some way to select or specify one, or define a precedence? Or some way to define an overriding filter for a particular user or set of users?

Tags (2)
1 Solution

Stephen_Sorkin
Splunk Employee
Splunk Employee

All filters are ORed together to form the composite search filter. There is no precedence or override. The user is able to search any data that any of his or her roles can.

View solution in original post

Stephen_Sorkin
Splunk Employee
Splunk Employee

All filters are ORed together to form the composite search filter. There is no precedence or override. The user is able to search any data that any of his or her roles can.

twinspop
Influencer

And what about when you're setting values to capability parameters? Which one wins? Example, srchMaxTime. 2 roles. One at 300 and one at 600. Which wins?

0 Karma

jadamsplunk
Path Finder

1.5 years later, but... the most permissive

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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...