Security

Splunk user access

vikas_gopal
Builder

Hello Everyone,

I have a situation , I have one app which has 10 dashboards, out of these 10 dashboards 5 are for Finance 2 for Wintel and 3 for network team.Client asks me to provide access to only respective users only .I mean user belongs to Finance can only see finance dashboards and Wintel user can only see wintel dashboard and so on.
Please suggest what to do..?

Thanks
Vikas

Tags (2)
0 Karma
1 Solution

araitz
Splunk Employee
Splunk Employee
  1. Create roles for Finance, Wintel, and Network teams
  2. Add appropriate users to roles, or map roles to AD/LDAP groups that contain appropriate users if you are using AD/LDAP
  3. Go to Settings > User Interface > Views
  4. Change app context to your app
  5. Next to each dashboard, click the Permissions link
  6. Set the appropriate permissions as required by the client

View solution in original post

araitz
Splunk Employee
Splunk Employee
  1. Create roles for Finance, Wintel, and Network teams
  2. Add appropriate users to roles, or map roles to AD/LDAP groups that contain appropriate users if you are using AD/LDAP
  3. Go to Settings > User Interface > Views
  4. Change app context to your app
  5. Next to each dashboard, click the Permissions link
  6. Set the appropriate permissions as required by the client

vikas_gopal
Builder

@araitz you are awesome ...Thanks for your time and help it works like magic

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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...