<?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: Controlling what can be access in a Data Connection in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Controlling-what-can-be-access-in-a-Data-Connection/m-p/2546650#M32725</link>
    <description>&lt;P&gt;Since this seems to be a database-side control, you could try pre-populating the connection string with a specific database.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Apr 2026 20:12:59 GMT</pubDate>
    <dc:creator>Eduardo_Monteiro</dc:creator>
    <dc:date>2026-04-10T20:12:59Z</dc:date>
    <item>
      <title>Controlling what can be access in a Data Connection</title>
      <link>https://community.qlik.com/t5/Management-Governance/Controlling-what-can-be-access-in-a-Data-Connection/m-p/2546645#M32724</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I've created a data connection in my client's environment and I'm successfully using security rules to control who can use the connection. What I need now is a way to control/limit what they can see in the Database and Owner drop-downs. Is there a way to accomplish this?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Steven&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2026 18:34:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Controlling-what-can-be-access-in-a-Data-Connection/m-p/2546645#M32724</guid>
      <dc:creator>stascher</dc:creator>
      <dc:date>2026-04-10T18:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling what can be access in a Data Connection</title>
      <link>https://community.qlik.com/t5/Management-Governance/Controlling-what-can-be-access-in-a-Data-Connection/m-p/2546650#M32725</link>
      <description>&lt;P&gt;Since this seems to be a database-side control, you could try pre-populating the connection string with a specific database.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2026 20:12:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Controlling-what-can-be-access-in-a-Data-Connection/m-p/2546650#M32725</guid>
      <dc:creator>Eduardo_Monteiro</dc:creator>
      <dc:date>2026-04-10T20:12:59Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling what can be access in a Data Connection</title>
      <link>https://community.qlik.com/t5/Management-Governance/Controlling-what-can-be-access-in-a-Data-Connection/m-p/2546656#M32726</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/39296"&gt;@stascher&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Yes. The available databases, schemas and tables will be restricted by the user set in the Data Connection.&lt;BR /&gt;Create a user in the Database with the exact restrictions you need, and this will be reflected in Qlik.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Mark Costa&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 11 Apr 2026 02:18:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Controlling-what-can-be-access-in-a-Data-Connection/m-p/2546656#M32726</guid>
      <dc:creator>marksouzacosta</dc:creator>
      <dc:date>2026-04-11T02:18:38Z</dc:date>
    </item>
  </channel>
</rss>

