<?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: summary index &amp; permissions in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/summary-index-permissions/m-p/94371#M964</link>
    <description>&lt;P&gt;also related to... &lt;A href="http://answers.splunk.com/questions/6154/permission-question"&gt;http://answers.splunk.com/questions/6154/permission-question&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Nov 2010 02:59:13 GMT</pubDate>
    <dc:creator>ives</dc:creator>
    <dc:date>2010-11-25T02:59:13Z</dc:date>
    <item>
      <title>summary index &amp; permissions</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/summary-index-permissions/m-p/94370#M963</link>
      <description>&lt;P&gt;I've created a scheduled report that runs and populates a summary index.&lt;/P&gt;

&lt;P&gt;From the admin account everything down to the dashboard using the query works fine.&lt;/P&gt;

&lt;P&gt;Other users can't seem to see any of the data in the summary table, others get "No results found."&lt;/P&gt;

&lt;P&gt;I was hoping to avoid giving them access to run the si report, to prevent multiple un-scheduled collections. In this particular case the owner of the si report is actually the report user, I had changed the permissions after the fact.&lt;/P&gt;

&lt;P&gt;A few questions:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Is permission information stored in a tag for the summary index data itself?&lt;/LI&gt;
&lt;LI&gt;Is it created at population time?&lt;/LI&gt;
&lt;LI&gt;Is there any way to correct it or allow rights to other users?  (they already have the role and auth from the role UI).&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2010 02:56:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/summary-index-permissions/m-p/94370#M963</guid>
      <dc:creator>ives</dc:creator>
      <dc:date>2010-11-25T02:56:00Z</dc:date>
    </item>
    <item>
      <title>Re: summary index &amp; permissions</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/summary-index-permissions/m-p/94371#M964</link>
      <description>&lt;P&gt;also related to... &lt;A href="http://answers.splunk.com/questions/6154/permission-question"&gt;http://answers.splunk.com/questions/6154/permission-question&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2010 02:59:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/summary-index-permissions/m-p/94371#M964</guid>
      <dc:creator>ives</dc:creator>
      <dc:date>2010-11-25T02:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: summary index &amp; permissions</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/summary-index-permissions/m-p/94372#M965</link>
      <description>&lt;P&gt;Solved. Be wary of the "Restrict Search Terms" option in user or role configuration. It applies to summary indexes.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2010 03:42:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/summary-index-permissions/m-p/94372#M965</guid>
      <dc:creator>ives</dc:creator>
      <dc:date>2010-11-25T03:42:59Z</dc:date>
    </item>
  </channel>
</rss>

