<?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 Restrict visibility of specific incident types based on user roles in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/restrict-visibility-of-specific-incident-types-based-on-user/m-p/597995#M3614</link>
    <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;
&lt;P&gt;We're currently focused on improving our access control model to limit the visibility of certain incident types based on user roles. Currently, this is done manually through the system command:&lt;/P&gt;
&lt;P&gt;```&lt;BR /&gt;/set_incident role = &amp;lt;role name&amp;gt;&lt;BR /&gt;```&lt;/P&gt;
&lt;P&gt;This command is executed at each incident level and isn't available for execution within playbooks. We are investigating how to integrate this command into a playbook to automate role-based logic.&lt;/P&gt;
&lt;P&gt;What is the best way to implement this, or are there alternative approaches we should consider? We're seeking input from the community on this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Sep 2024 12:43:59 GMT</pubDate>
    <dc:creator>M.IbrahimHabibullah</dc:creator>
    <dc:date>2024-09-17T12:43:59Z</dc:date>
    <item>
      <title>Restrict visibility of specific incident types based on user roles</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/restrict-visibility-of-specific-incident-types-based-on-user/m-p/597995#M3614</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;
&lt;P&gt;We're currently focused on improving our access control model to limit the visibility of certain incident types based on user roles. Currently, this is done manually through the system command:&lt;/P&gt;
&lt;P&gt;```&lt;BR /&gt;/set_incident role = &amp;lt;role name&amp;gt;&lt;BR /&gt;```&lt;/P&gt;
&lt;P&gt;This command is executed at each incident level and isn't available for execution within playbooks. We are investigating how to integrate this command into a playbook to automate role-based logic.&lt;/P&gt;
&lt;P&gt;What is the best way to implement this, or are there alternative approaches we should consider? We're seeking input from the community on this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Sep 2024 12:43:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/restrict-visibility-of-specific-incident-types-based-on-user/m-p/597995#M3614</guid>
      <dc:creator>M.IbrahimHabibullah</dc:creator>
      <dc:date>2024-09-17T12:43:59Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict visibility of specific incident types based on user roles</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/restrict-visibility-of-specific-incident-types-based-on-user/m-p/599765#M3684</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/545486011"&gt;@M.IbrahimHabibullah&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can use setIncident to restrict the incidents to be reachable by specific roles. Please see the screenshot below. The users only having Administrator role will have access to the incident.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="gyldz_0-1728374047465.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/62611iA00B4FE15D210DE2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="gyldz_0-1728374047465.png" alt="gyldz_0-1728374047465.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I hope this answers your question.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2024 07:54:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/restrict-visibility-of-specific-incident-types-based-on-user/m-p/599765#M3684</guid>
      <dc:creator>gyldz</dc:creator>
      <dc:date>2024-10-08T07:54:47Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict visibility of specific incident types based on user roles</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/restrict-visibility-of-specific-incident-types-based-on-user/m-p/1224286#M3955</link>
      <description>&lt;P&gt;Little late to the party....&lt;BR /&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/287891"&gt;@gyldz&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Do you know if this is also working with indicators?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2025 10:28:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/restrict-visibility-of-specific-incident-types-based-on-user/m-p/1224286#M3955</guid>
      <dc:creator>JBoehm</dc:creator>
      <dc:date>2025-03-20T10:28:43Z</dc:date>
    </item>
  </channel>
</rss>

