Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
ChristopherBirnbaum
Contributor II
Contributor II

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

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/DataSpac...). 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

Labels (3)
1 Solution

Accepted Solutions
mpc
Partner Ambassador
Partner Ambassador

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

From Next Decision and mpc with love

View solution in original post

2 Replies
mpc
Partner Ambassador
Partner Ambassador

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

From Next Decision and mpc with love
ChristopherBirnbaum
Contributor II
Contributor II
Author

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