topic Show datamodel in published apps in Management & Governance

Show datamodel in published apps

tobgen69 — Thu, 17 Nov 2016 16:07:22 GMT

Hi,

i would like to change the security settings in QlikSenseServer to give a specific usergroup or for example root and content admins the access on the datamodel in published apps.

Does anyone know how to do this or has already implemented this?

I know that by general this is not intended by the security settings of Qlik but i think this would be a big benefit in understanding the database when using an app which is not yours. The way to duplicate the app and then take a look at the datamodel is no option.

Thanks

Re: Show datamodel in published apps

shraddha_g — Thu, 17 Nov 2016 16:10:15 GMT

I dnt think it is possible.. Try if you csn find anything in security rules in QMC

Re: Show datamodel in published apps

tobgen69 — Thu, 17 Nov 2016 16:16:14 GMT

Thanks for your reply.

In some of the security rules is mentioned the "App_Appscript" and the "Loadmodel".

This rule is actually given specific users the access to read the specified app-objects. But the Loadmodel and the appscript are explicitly negated. Anyway, removing this part doesnt give the access on the loadmodel.

(resource.objectType = "userstate" or resource.objectType = "sheet" or resource.objectType = "story" or resource.objectType = "bookmark" or resource.objectType = "snapshot" or resource.objectType = "embeddedsnapshot" or resource.objectType = "hiddenbookmark")

and user.group like "*dev" and (resource.resourcetype = "App.Object" and resource.published ="true" and resource.objectType != "app_appscript" and resource.objectType != "loadmodel")

Any other ideas?

Re: Show datamodel in published apps

Anonymous — Mon, 21 Nov 2016 17:05:40 GMT

Rather than changing the security rules, I would suggest you to deploy the data model app in their my work area.

Re: Show datamodel in published apps

tobgen69 — Mon, 21 Nov 2016 17:33:32 GMT

So i should duplicate an app and locate it to each user? This would imply that for example if you change something in the datamodel you need to change the 100 duplicates of this app, or do i not understand you properly?

If I do this seems not viable to me.

Re: Show datamodel in published apps

Vegar — Mon, 21 Nov 2016 17:42:45 GMT

A quick but not perfect solution could be to add a picture of the ddata model in an app sheet.

It is not optimal, but it will give your users a feel for the data.

Re: Show datamodel in published apps

tobgen69 — Mon, 21 Nov 2016 19:09:01 GMT

Thanks vegar.lie.arntsen for your idea. I will keep this in mind as an quick overview for some cases, but of course it would be nice to use the full model with all these worthy informations.

Re: Show datamodel in published apps

Anonymous — Mon, 21 Nov 2016 19:27:33 GMT

It's a great question. If you have 100+ users , This is not a right solution.

If your intended audiences are developers and need only for few of them you can go for it. Otherwise add as picture inside story is appropriate place.

Re: Show datamodel in published apps

tobgen69 — Wed, 23 Nov 2016 15:05:34 GMT

I found a solution in an other thread:

Re: can't see a peer's data load editor scripts

That means, you only have to change the content admin security rule to work in "hub and qmc".

Works fine for me, tested in QS 3.1.1.

It still has some sideeffects, as for now i can see ALL apps in "my work", but i guess all of this is managable with some more accurate securtiy rules.

Re: Show datamodel in published apps

Thu, 19 Jan 2017 08:16:55 GMT

Hi Tobi,

to let Users see the Datamodel in published apps, you have to create a user role f.e. "DataModelReader" by creating the following security role:

Recource filter: App_*

Actions: read, update (!!!)

Condition: user.role="DataModelReader"

Context: Both in Hub and QMC (!!!)

Now you have a new user role called "DataModelReader" which you can grant to your users.

Users having that role can see the the link to the data model and to the script. They can open the data model viewer and will see the data model but can not safe any changes.

They can also open the script editor, but they will not see any code -except the standard variable definitions- and they can not safe any changes in the script.

For we already talked to each other and tried that solution, I know this helps

Regards

Sabine

Re: Show datamodel in published apps

tobgen69 — Thu, 19 Jan 2017 13:14:32 GMT

Hi Sabine,

it definitly does!

Thanks again for that great solution and for sharing it with the community.

Best regards

Tobi

Re: Show datamodel in published apps

Anonymous — Thu, 02 Feb 2017 14:07:28 GMT

Hi Sabine,

i think you meant :

Condition: user.roles="DataModelReader"

Are you sure a user can not change anything? I could change the design, for example by adding an object.

I could not change the load script, but i saw it.

Better would be if we can define a rule just for the datamodel only with the action read.

This solution is to risky as other user can change the app object.

I am using the newest Qlik Sense Version 3.1 SR4

Regards!

Re: Show datamodel in published apps

shubham_singh — Thu, 15 Jun 2017 08:20:35 GMT

Hi Sabine,

Your method of providing data model and script access of published app works like a charm however it has a small problem that when I assigned the role to myself I could see all the unpublished app in My Work including those of different owners. It would be nice if I could see only those app in My Work that are owned by me.

Re: Show datamodel in published apps

Anonymous — Tue, 28 Nov 2017 04:06:55 GMT

Hi Sabine,

In your method, User can change the app information. Application name/title. Any security rule to keep this app information always hidden for Edit / disable the edit option for app information to published app for users ?

Re: Show datamodel in published apps

dominik1 — Fri, 05 Apr 2019 04:38:30 GMT

one thing, the condition is user.roles and not user.role

Re: Show datamodel in published apps

federerman — Wed, 17 Apr 2019 17:47:10 GMT

The solution posted is not ideal as it gives end users the ability to update/edit the app name and description from the hub. This could cause other security rules to break.