topic Re: Do we need doc cal assigned for a user in Mashup in QlikView

Do we need doc cal assigned for a user in Mashup

aniketsr — Mon, 26 Jan 2026 18:19:17 GMT

Hi All,

I have to propose a single data point page where data comes from many streams along with some objects from qlikview

is it that only work bench license is needed

Is any more license required ? Like named cal or doc cal etc ?

Any help will be appreciated.

Thank you

Re: Do we need doc cal assigned for a user in Mashup

Miguel_Angel_Baeyens — Thu, 24 May 2018 12:43:45 GMT

Which are your needs, exactly?

Workbench works along the Information Access Server (IAS) server license which implies

one document only (or more if the license is expanded)
anonymous users (e.g.: section access will not work)
and that the site where the QlikView document will be published will be publicly available

There is no equivalent to the user license lease in the IAS license.

Re: Do we need doc cal assigned for a user in Mashup

aniketsr — Thu, 24 May 2018 13:19:30 GMT

Hi ,

Thank you for the response..

Let me explain the exact requirement so that you can guide me in a better way:

We have new web page created using java script for some users, wherein the data in that web page comes from different tools and qlikview is one of them.

we have some charts which we have created in qlikview which is been used by users and those dashboards are accessed through access point as we have given them CALs .

There are some set of users who have access to the new web page but those users do not have access to the dashboards, more prissily we have not assigned any CAls to them.

Now if we happen to incorporate the object from our existing dashboards in the new web page is it necessary that we have to assign CALs to those users also.

Thank you .

Re: Do we need doc cal assigned for a user in Mashup

aniketsr — Thu, 24 May 2018 13:26:05 GMT

Hi have a general information regarding IAS as bellow:

Do we have any security breech for the data if the server is available on the public internet?

Information Access Server (IAS) is an edition of QlikView Server designed to power public Internet sites:

Includes the add-on QlikView Real Time Server
Is licensed for uncapped number of user but limited to one QlikView document
Must be set to anonymous mode only and authentication must be off
Requires that the QlikView server be on the public Internet and publicly accessible
Requires that the URL for accessing the site powered by the QlikView Server be publicly accessible
Requires that no QlikView client (e.g., QlikView Desktop, Internet Explorer plug-in, Ajax) can access the QlikView Server (all user interfaces must be built by the customer manually or with QlikView Workbench)

Re: Do we need doc cal assigned for a user in Mashup

Miguel_Angel_Baeyens — Thu, 24 May 2018 13:35:21 GMT

As the name implies, that is the license you need when you want to make a QVW, or parts of it, publicly available in the Internet.

But, the same document cannot be served for both internal users (using Named User CALs) and external users (anonymous, via mashups), because you cannot apply 2 licenses on the same server.

On one hand, you will keep your existing environment with the QlikView Server license you have now (SBE or Enterprise) which will lease licenses as it is doing now.

On the other, you will add a different new server with only that QVW which has to be exposed via mashups. The IAS license tells you how many documents you can share. This server will be exposed to the internet or connected to the webserver which will.

You can request more documents for your license to your Partner Manager or Qlik Sales Rep.

Re: Do we need doc cal assigned for a user in Mashup

Peter_Cammaert — Thu, 24 May 2018 15:47:42 GMT

If I'm not mistaken, you can also use Qlik WorkBench to integrate regular QlikView Server content into web sites like SharePoint. In that case, every user must be authenticated and be recognised by QlikView Server and a CAL needs to be assigned to that user. If matching IDs are impossible, you can use Header authentication to connect to a different authentication mechanism.