topic is it possible for users to allow them access to data (QVDs) in managed space but restricting useage of connections (ODBC or other) in Data Movement & Streaming

is it possible for users to allow them access to data (QVDs) in managed space but restricting useage of connections (ODBC or other)

ChristopherBirnbaum — Wed, 19 Mar 2025 21:46:28 GMT

Hello!

We face follwing scenario as BI-Provider for our customer.

We create QVDs for frontend apps in a dedicated managed space (e.g. "DWHS ETL") and use these QVDs to load data to apps in another space for "managed analytics" as a main use case.

Some of the advanced users would like to consume the raw-data from the QVDs and create their own apps. The QVDs are created from scripts, that are published to this very space and use an ODBC connection to our production Database.

We would like to allow them access to the managed space "DWHS ETL" through the "can consume data" permission (see https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/DataSpaces/permissions-data-space.htm). However that would also allow them to use the ODBC connection to the production Database. (especially through elevated permissions, as we use a special user for accessing the database which would exceed their permissions)

Is it possible to seperate the permissions in a way, that the "advanced users" can access the QVDs but not the ODBC connection?

BR
Christopher

Re: is it possible for users to allow them access to data (QVDs) in managed space but restricting useage of connections (ODBC or other)

mpc — Wed, 05 Mar 2025 08:52:47 GMT

Hi,

In the same Space AFAIK no, but you can create the Data Connection in one Space, and store the QVD in a dedicated Space, with only DataFiles:// connection and Can Consume Data role to the "advanced users"

Bests

Re: is it possible for users to allow them access to data (QVDs) in managed space but restricting useage of connections (ODBC or other)

ChristopherBirnbaum — Wed, 05 Mar 2025 14:46:00 GMT

thank you, we came to the same conclusion.

we'll keep scripts and ODBC connection in the "ETL" space and create a seperate "Data/QVD" space