<?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 Accesspoint - why? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Accesspoint-why/m-p/185354#M1286137</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Stefan,&lt;/P&gt;&lt;P&gt;I can see that is has an advantage, but at the cost of the interface and adding another layer of complexity. At the moment I have an asp menu (cloned from the examples I think), but which delivers a corporate style page and allows, for example, 'marquee' scrolling to show information/news. Nice and simple!&lt;/P&gt;&lt;P&gt;Is the Accesspoint interface configurable? My question I think should have been 'what am I missing out on by not using AccessPoint'? For example is it neccessary to use AccessPoint to force the release of Session or Document CALs?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gordon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Feb 2010 16:15:44 GMT</pubDate>
    <dc:creator />
    <dc:date>2010-02-08T16:15:44Z</dc:date>
    <item>
      <title>Accesspoint - why?</title>
      <link>https://community.qlik.com/t5/QlikView/Accesspoint-why/m-p/185352#M1286132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have only seen screen shots of AccessPoint in the manuals and think the interface quite honestly looks awful. What are the advantages over a simple link from a web page? Does AccessPoint only show the user the documents that he has permissions to in terms of Windows and 'Section Access'?&lt;/P&gt;&lt;P&gt;Am I missing something?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gordon&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/Accesspoint-why/m-p/185352#M1286132</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Accesspoint - why?</title>
      <link>https://community.qlik.com/t5/QlikView/Accesspoint-why/m-p/185353#M1286134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, the advantage is, that the AccessPoint is personalized:&lt;/P&gt;&lt;P&gt;- So one does only see those QlikView-applications with appropriate permissions&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2010 15:58:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Accesspoint-why/m-p/185353#M1286134</guid>
      <dc:creator />
      <dc:date>2010-02-08T15:58:51Z</dc:date>
    </item>
    <item>
      <title>Accesspoint - why?</title>
      <link>https://community.qlik.com/t5/QlikView/Accesspoint-why/m-p/185354#M1286137</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Stefan,&lt;/P&gt;&lt;P&gt;I can see that is has an advantage, but at the cost of the interface and adding another layer of complexity. At the moment I have an asp menu (cloned from the examples I think), but which delivers a corporate style page and allows, for example, 'marquee' scrolling to show information/news. Nice and simple!&lt;/P&gt;&lt;P&gt;Is the Accesspoint interface configurable? My question I think should have been 'what am I missing out on by not using AccessPoint'? For example is it neccessary to use AccessPoint to force the release of Session or Document CALs?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gordon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2010 16:15:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Accesspoint-why/m-p/185354#M1286137</guid>
      <dc:creator />
      <dc:date>2010-02-08T16:15:44Z</dc:date>
    </item>
  </channel>
</rss>

