<?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: Best practises - Access Qvw in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Best-practises-Access-Qvw/m-p/449829#M1272389</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can try Loop and Distribute in task creation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Mar 2013 06:43:08 GMT</pubDate>
    <dc:creator>gainkarthi</dc:creator>
    <dc:date>2013-03-19T06:43:08Z</dc:date>
    <item>
      <title>Best practises - Access Qvw</title>
      <link>https://community.qlik.com/t5/QlikView/Best-practises-Access-Qvw/m-p/449828#M1272387</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking for some best practises about developing a qlikview document for multiple customers. These customers only sees their own data. My client only runs small bussiness server, no publishing server. Qlikview is only accessible by a browser. Information in this document is very confidential, so security has high priority at all times! &lt;/P&gt;&lt;P&gt;My questions are:&lt;/P&gt;&lt;P&gt;- Is section access and data reduction secure/stable enough? From my point of view, it is easy to make a mistake in access rights and the whole document is accessible by everyone without knowing. It already happened onces (it wasn't me fortunately &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/wink.png" /&gt;). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Is it better to split this qlikview document into smaller documents and set security on license level for every customer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for your thoughts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Best-practises-Access-Qvw/m-p/449828#M1272387</guid>
      <dc:creator>frankhuning</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Best practises - Access Qvw</title>
      <link>https://community.qlik.com/t5/QlikView/Best-practises-Access-Qvw/m-p/449829#M1272389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can try Loop and Distribute in task creation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Mar 2013 06:43:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Best-practises-Access-Qvw/m-p/449829#M1272389</guid>
      <dc:creator>gainkarthi</dc:creator>
      <dc:date>2013-03-19T06:43:08Z</dc:date>
    </item>
  </channel>
</rss>

