<?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 Prevent QVD consumption in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Prevent-QVD-consumption/m-p/2523222#M106756</link>
    <description>&lt;P&gt;Hello all&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;i have a requirement to secure QVD files in away that there are a group of QVD files that should only be consumed by members of Team1&lt;/P&gt;&lt;P&gt;any developer outside Team1 shouldn't be able to consume these QVD files i.e. cannot create a folder data connection to where those QVD files reside.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;kindly advise on how to accomplish this requirement.&lt;/P&gt;&lt;P&gt;I tried with Windows security, but still any developer can consume the QVD files because the process running behind the scenes is ran by the user account running the Qlik Sense Engine&lt;/P&gt;</description>
    <pubDate>Fri, 04 Jul 2025 13:30:15 GMT</pubDate>
    <dc:creator>ali_hijazi</dc:creator>
    <dc:date>2025-07-04T13:30:15Z</dc:date>
    <item>
      <title>Prevent QVD consumption</title>
      <link>https://community.qlik.com/t5/App-Development/Prevent-QVD-consumption/m-p/2523222#M106756</link>
      <description>&lt;P&gt;Hello all&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;i have a requirement to secure QVD files in away that there are a group of QVD files that should only be consumed by members of Team1&lt;/P&gt;&lt;P&gt;any developer outside Team1 shouldn't be able to consume these QVD files i.e. cannot create a folder data connection to where those QVD files reside.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;kindly advise on how to accomplish this requirement.&lt;/P&gt;&lt;P&gt;I tried with Windows security, but still any developer can consume the QVD files because the process running behind the scenes is ran by the user account running the Qlik Sense Engine&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 13:30:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Prevent-QVD-consumption/m-p/2523222#M106756</guid>
      <dc:creator>ali_hijazi</dc:creator>
      <dc:date>2025-07-04T13:30:15Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent QVD consumption</title>
      <link>https://community.qlik.com/t5/App-Development/Prevent-QVD-consumption/m-p/2523252#M106770</link>
      <description>&lt;P&gt;Hi not sure but may be the this method&amp;nbsp;&lt;/P&gt;&lt;P&gt;Move Team1 QVDs to a separate folder (e.g., D:\SecureQVDs\Team1\)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Remove read permission for everyone except Team1 from that folder.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Use a Team1-only service account for reloads that access that folder.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All other developers will be denied access (because Qlik Engine runs under another user).&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 19:33:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Prevent-QVD-consumption/m-p/2523252#M106770</guid>
      <dc:creator>Chanty4u</dc:creator>
      <dc:date>2025-07-04T19:33:31Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent QVD consumption</title>
      <link>https://community.qlik.com/t5/App-Development/Prevent-QVD-consumption/m-p/2523254#M106772</link>
      <description>&lt;P&gt;Well first we cannot change the user account that runs the Qlik sense engine.&lt;/P&gt;&lt;P&gt;Second I didn't mention that qvds of Team1 shouldn't be consumed by members of Team2 and also qvd files of Team2 shouldn't be consumed by members of Team1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 20:11:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Prevent-QVD-consumption/m-p/2523254#M106772</guid>
      <dc:creator>ali_hijazi</dc:creator>
      <dc:date>2025-07-04T20:11:47Z</dc:date>
    </item>
  </channel>
</rss>

