Nprinting connection and limiting Qlik Sense App Id's

[RenaatV]

Hi,

I've read all the documentation and scanned the discussion list and couldn't find any solution for the problem we're having. We've got quite a lot of Qlik Sense apps over different departments. We're using NPrinting and are looking at how we can restrict a developer to create a connection towards Qlik sense apps.

We looked at setting up different developer roles with a predefined app, but then these developers still need to be able to setup connections towards the qlik sense apps from their respective departments. But if they are able to setup connections and manage to retrieve a Qlik sense app Id and user ID (quite easy) from other departments then they can access everything. So is their some way to restrict having the possibility to setup connections to certain qlik sense app id's?

Thanks in advance

[Ruggero_Piccoli]

Hi,

Your scenario is clear and the solution is to remove the rights to create connections from developers security role and assign the right to create connection only to authorized administrators. Those administrators create the connections and developers will use them. 

Best Regards,

Ruggero

[RenaatV]

Thanks! Already thought it was going to be something like this.  A bit cumbersome in our organisation as it will take up to 2 days to get a connection so was looking for something simpler. But if nothing else is in place this will do.

And just for confirmation, if we want to restrict access to apps for developers belonging to distinct departments, we will be required to setup different developer roles, right? For example 'dev_accounting','dev_loans','dev_hr'

[Ruggero_Piccoli]

Hi,

Yes, you have to create a different security role for each group of developers and limit the visible apps in each role. Then, in case, you can assign many security roles to the same developer user. For example the developer Bill can have all 3 roles: 'dev_accounting', 'dev_loans', 'dev_hr' or you can assign to Bill a second role for a limited amount of time, etc. because there is not a limit in the number of security roles a user can have.

Best Regards,

Ruggero