<?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: Multiple owners of knowledge objects in Security</title>
    <link>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329167#M12611</link>
    <description>&lt;P&gt;That's exactly what we are trying to avoid.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Apr 2018 13:18:13 GMT</pubDate>
    <dc:creator>tusharsaran1</dc:creator>
    <dc:date>2018-04-12T13:18:13Z</dc:date>
    <item>
      <title>Multiple owners of knowledge objects</title>
      <link>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329164#M12608</link>
      <description>&lt;P&gt;Is it possible to configure more than 1 owners of a dashboard/report?&lt;BR /&gt;
We want to give write perms to a few individuals for a dashboard that is readable by everyone. The only way I can think of doing this is if we can add multiple owners. Is that possible?&lt;BR /&gt;
Alternatively, is there another way of giving write perms to a few individuals rather than to a role?&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2018 11:43:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329164#M12608</guid>
      <dc:creator>tusharsaran1</dc:creator>
      <dc:date>2018-04-12T11:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple owners of knowledge objects</title>
      <link>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329165#M12609</link>
      <description>&lt;P&gt;You can't set multiple owners for a knowledge object.&lt;BR /&gt;
The best shot you have is to create a role for the few individuals that should have write permissions and give said permissions to that role only.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2018 13:09:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329165#M12609</guid>
      <dc:creator>damien_chillet</dc:creator>
      <dc:date>2018-04-12T13:09:50Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple owners of knowledge objects</title>
      <link>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329166#M12610</link>
      <description>&lt;P&gt;You can assign the write permission to any role, not "just" for the owner.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2018 13:10:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329166#M12610</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-04-12T13:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple owners of knowledge objects</title>
      <link>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329167#M12611</link>
      <description>&lt;P&gt;That's exactly what we are trying to avoid.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2018 13:18:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329167#M12611</guid>
      <dc:creator>tusharsaran1</dc:creator>
      <dc:date>2018-04-12T13:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple owners of knowledge objects</title>
      <link>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329168#M12612</link>
      <description>&lt;P&gt;Why are you trying to avoid creating a new role? &lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2018 13:21:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329168#M12612</guid>
      <dc:creator>damien_chillet</dc:creator>
      <dc:date>2018-04-12T13:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple owners of knowledge objects</title>
      <link>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329169#M12613</link>
      <description>&lt;P&gt;Because we will soon have hundreds of dashboards in our environment. Each dashboard only requires 2-3 users to have write access. Creating new Splunk roles and corresponding LDAP groups for each set of users is not practical.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2018 13:37:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Multiple-owners-of-knowledge-objects/m-p/329169#M12613</guid>
      <dc:creator>tusharsaran1</dc:creator>
      <dc:date>2018-04-12T13:37:14Z</dc:date>
    </item>
  </channel>
</rss>

