<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: What are the options for dashboard permissions? in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404495#M26514</link>
    <description>&lt;P&gt;What does EVERYONE mean @somesoni2?&lt;/P&gt;</description>
    <pubDate>Thu, 21 Feb 2019 20:21:46 GMT</pubDate>
    <dc:creator>ddrillic</dc:creator>
    <dc:date>2019-02-21T20:21:46Z</dc:date>
    <item>
      <title>What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404488#M26507</link>
      <description>&lt;P&gt;When setting the &lt;STRONG&gt;Edit Permissions&lt;/STRONG&gt; for a dashboard, our users see the &lt;STRONG&gt;Everyone&lt;/STRONG&gt; option and the roles they belong to. Is there a way to customize it beyond this way? &lt;/P&gt;

&lt;P&gt;Interestingly, we have in &lt;CODE&gt;&amp;lt;app&amp;gt;/metadata/local.meta&lt;/CODE&gt; -&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[]
access = read : [ admin,&amp;lt;user role&amp;gt; ], write : [ admin …]
export = none
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And the user who is part of  the &lt;STRONG&gt;user role&lt;/STRONG&gt; could not see anything unless we assigned the permissions to EVERYONE – Read.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 16:06:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404488#M26507</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-02-21T16:06:08Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404489#M26508</link>
      <description>&lt;P&gt;What you want your Edit Permissions options to be?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 17:24:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404489#M26508</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-02-21T17:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404490#M26509</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 17:28:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404490#M26509</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-02-21T17:28:39Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404491#M26510</link>
      <description>&lt;P&gt;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."&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 17:33:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404491#M26510</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-02-21T17:33:45Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404492#M26511</link>
      <description>&lt;P&gt;Makes perfect sense @somesoni2. &lt;/P&gt;

&lt;P&gt;What's the relation between this dashboard setting and the settings in &lt;CODE&gt;&amp;lt;app&amp;gt;/metadata/local.meta&lt;/CODE&gt; because here at the app level 'user' does have read access?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 18:00:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404492#M26511</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-02-21T18:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404493#M26512</link>
      <description>&lt;P&gt;The default app level (one with &lt;CODE&gt;[]&lt;/CODE&gt; 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.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 19:34:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404493#M26512</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-02-21T19:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404494#M26513</link>
      <description>&lt;P&gt;@somesoni2 - gorgeous as usual - much appreciated. &lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 20:00:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404494#M26513</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-02-21T20:00:13Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404495#M26514</link>
      <description>&lt;P&gt;What does EVERYONE mean @somesoni2?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 20:21:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404495#M26514</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-02-21T20:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404496#M26515</link>
      <description>&lt;P&gt;Everyone is denoted by &lt;CODE&gt;*&lt;/CODE&gt; in the .meta files, which means any authenticated user in Splunk. So if your local.meta/default.meta says &lt;CODE&gt;access = read : [ * ]..&lt;/CODE&gt;, it means the specified artifact can be read by all Splunk users, unless permissions are overridden at app level.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 20:41:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404496#M26515</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-02-21T20:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404497#M26516</link>
      <description>&lt;P&gt;But the funny thing is that the user who assigns the permissions to the dashboard, can't see the &lt;CODE&gt;access = read : [ * ]..&lt;/CODE&gt; settings. &lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 20:59:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404497#M26516</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-02-21T20:59:16Z</dc:date>
    </item>
    <item>
      <title>Re: What are the options for dashboard permissions?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404498#M26517</link>
      <description>&lt;P&gt;I also wonder if we can &lt;EM&gt;simply&lt;/EM&gt; go and modify &lt;CODE&gt;$SPLUNK_HOME/etc/apps/&amp;lt;app name&amp;gt;/metadata/local.meta&lt;/CODE&gt; for the specific artifact. Meaning, apply the desired changes behind the scenes.  &lt;/P&gt;</description>
      <pubDate>Fri, 22 Feb 2019 20:32:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/What-are-the-options-for-dashboard-permissions/m-p/404498#M26517</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-02-22T20:32:45Z</dc:date>
    </item>
  </channel>
</rss>

