Dashboards & Visualizations

What are the options for dashboard permissions?

ddrillic
Ultra Champion

When setting the Edit Permissions for a dashboard, our users see the Everyone option and the roles they belong to. Is there a way to customize it beyond this way?

Interestingly, we have in <app>/metadata/local.meta -

[]
access = read : [ admin,<user role> ], write : [ admin …]
export = none

And the user who is part of the user role could not see anything unless we assigned the permissions to EVERYONE – Read.

Tags (2)
0 Karma
1 Solution

somesoni2
Revered Legend

What you want your Edit Permissions options to be?

View solution in original post

somesoni2
Revered Legend

What you want your Edit Permissions options to be?

ddrillic
Ultra Champion

A certain user role, because we ended up having separate roles for power and user. So, the power user can't assign permissions to the corresponding user role of this specific app.

0 Karma

somesoni2
Revered Legend

You'd probably have to nest/inherit your 'power' user role from 'user' role to do that. As you've already identified"our users see the Everyone option and the roles they belong to/inherit from."

ddrillic
Ultra Champion

Makes perfect sense @somesoni2.

What's the relation between this dashboard setting and the settings in <app>/metadata/local.meta because here at the app level 'user' does have read access?

0 Karma

somesoni2
Revered Legend

The default app level (one with [] or no stanza name) defines the access permissions on the app. A user has read permissions on the app means user can see the app in the app dropdown/tile on side bar and can launch the app. Sharing permissions on artifacts are handled explicitly.

ddrillic
Ultra Champion

@somesoni2 - gorgeous as usual - much appreciated.

0 Karma

ddrillic
Ultra Champion

What does EVERYONE mean @somesoni2?

0 Karma

somesoni2
Revered Legend

Everyone is denoted by * in the .meta files, which means any authenticated user in Splunk. So if your local.meta/default.meta says access = read : [ * ].., it means the specified artifact can be read by all Splunk users, unless permissions are overridden at app level.

ddrillic
Ultra Champion

But the funny thing is that the user who assigns the permissions to the dashboard, can't see the access = read : [ * ].. settings.

0 Karma

ddrillic
Ultra Champion

I also wonder if we can simply go and modify $SPLUNK_HOME/etc/apps/<app name>/metadata/local.meta for the specific artifact. Meaning, apply the desired changes behind the scenes.

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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...