<?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: SAS Visual Investigator RBAC for Relationships in Fraud, AML and Security Intelligence</title>
    <link>https://communities.sas.com/t5/Fraud-AML-and-Security/SAS-Visual-Investigator-RBAC-for-Relationships/m-p/972505#M1113</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Authorisation rules are applied to the entities rather than the relationships. If a user is a member of a group that can see both Entity A and Entity B then they will see all relationships between them - you need to have access to the items at either end of the relationship.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For your scenario below you could try configuring rules so that the&amp;nbsp;&lt;EM&gt;ConfidentialGroup&lt;/EM&gt;&amp;nbsp;has Search/Read access to both Entity A and Entity B but the PublicGroup only has access to Entity A (or B) as appropriate.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Details can be found here:&amp;nbsp;&lt;A href="https://go.documentation.sas.com/doc/en/vicdc/v_037/visgatorag/dh-authorization-tab-about.htm" target="_blank"&gt;https://go.documentation.sas.com/doc/en/vicdc/v_037/visgatorag/dh-authorization-tab-about.htm&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Susan&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Aug 2025 13:54:44 GMT</pubDate>
    <dc:creator>susantrueman</dc:creator>
    <dc:date>2025-08-12T13:54:44Z</dc:date>
    <item>
      <title>SAS Visual Investigator RBAC for Relationships</title>
      <link>https://communities.sas.com/t5/Fraud-AML-and-Security/SAS-Visual-Investigator-RBAC-for-Relationships/m-p/971066#M1107</link>
      <description>&lt;P&gt;Hi Experts!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As this is a product functionality question, parking my question here hoping some experts have also faced a similar requirement.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have 2 entities EntityA and EntityB that all user groups must be able to view.&lt;/P&gt;&lt;P&gt;We have 2 data sources for relationships, PublicRelationships and ConfidentialRelationships.&lt;/P&gt;&lt;P&gt;We have 2 user groups, PublicGroup and ConfidentialGroup.&lt;/P&gt;&lt;P&gt;ConfidentialGroup should be able to see the relationships from both PublicRelationships and ConfidentialRelationships Source,&lt;/P&gt;&lt;P&gt;while PublicGroup must only see the relationships coming from PublicGroup.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any way to implement this? Somehow the Conditions tab under Relationships seem to point more to link display design colors rather than as "Filter Conditions".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking forward to some guidance!&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jul 2025 01:07:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Fraud-AML-and-Security/SAS-Visual-Investigator-RBAC-for-Relationships/m-p/971066#M1107</guid>
      <dc:creator>JAE2019</dc:creator>
      <dc:date>2025-07-18T01:07:40Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Visual Investigator RBAC for Relationships</title>
      <link>https://communities.sas.com/t5/Fraud-AML-and-Security/SAS-Visual-Investigator-RBAC-for-Relationships/m-p/972505#M1113</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Authorisation rules are applied to the entities rather than the relationships. If a user is a member of a group that can see both Entity A and Entity B then they will see all relationships between them - you need to have access to the items at either end of the relationship.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For your scenario below you could try configuring rules so that the&amp;nbsp;&lt;EM&gt;ConfidentialGroup&lt;/EM&gt;&amp;nbsp;has Search/Read access to both Entity A and Entity B but the PublicGroup only has access to Entity A (or B) as appropriate.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Details can be found here:&amp;nbsp;&lt;A href="https://go.documentation.sas.com/doc/en/vicdc/v_037/visgatorag/dh-authorization-tab-about.htm" target="_blank"&gt;https://go.documentation.sas.com/doc/en/vicdc/v_037/visgatorag/dh-authorization-tab-about.htm&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Susan&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Aug 2025 13:54:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Fraud-AML-and-Security/SAS-Visual-Investigator-RBAC-for-Relationships/m-p/972505#M1113</guid>
      <dc:creator>susantrueman</dc:creator>
      <dc:date>2025-08-12T13:54:44Z</dc:date>
    </item>
  </channel>
</rss>

