"Work" area availability sets up in Node Purpose field - disregarding access rights (ROOT admin or whatever user)
QMC-> Node->Edit Node - >Node Purpose:
Development and Both - gives opportunity to develop applications.
Production - don't.
Most likely your central node is set to Production.
Hope this helps.
Yes my Central Node is configured as Production and Dev Node has Node Purpose of Development. But, if Work Area visibility is dependent only upon Node Purpose configuration, disregarding access rights -
Then why is it that when logging into HUB load balanced on Central Node (with Node Purpose as Production) using the service account (which is running all our Qlik Sense services) we are able to view the Work Area?
Its not a problem as such. I am just trying to know why is there such a difference?
The scenario is :
- Logging into HUB >> LoadBalanced on Dev Node >> Node Purpose set is Development
-- using any account I am able to see WORK Area and as you said it must be visible.
- Logging into HUB >> LoadBalanced on Central Node >> Node Purpose set is Production
-- using my ROOT Admin account ---> No WORK Area visible
-- using service account which obviously has ROOT Admin privilege ---> WORK Area Visible.
Now as you said if WORK Area visibility is independent of Access Rights then why is the above scenario occurring when logging in using my ROOT Admin account and the Service Account?
Sorry, my bad... I couldn't reproduce your issue on my side as soon as I'm not using default security rules.
Check your security rules as well.
Use the drop-down to select which environment the node is intended for: Production, Development, or Both.
This setting is defined in the QMC on each node that is added, and the effects are as follows:
- Production: this server is intended to support users to access apps but not create them. This means that when a user connects to this node, the Create new app button in the hub is not displayed to the user. To hide the Work section in the hub, you need to disable the security rule that grants the application owner access.
- Development: this server is intended to allow users to create apps but not serve the normal user traffic for users consuming published apps. In this case, the create and edit capabilities are enabled, but the server will not be considered when load balancing user traffic.
- Both: this setting allows both activities to occur on the node. This means that both normal user traffic is handled and users can create apps.
Hope this helps.
The Work section of the Hub is intended to be the personal work space for an individual user. The Work section will show if one of two conditions are met:
- The user has the ability to create a new app
- The user has read rights on unpublished apps
So basically when NodeType=Production, the Work area will still show if the user has read rights on an unpublished app (generally determined by App ownership).
Your logic is absolutely correct. Thanks a lot for that info.
But would like to know that when Node Purpose is Development then it doesnt matter whether the user has read access to apps in hub or not right? Because even when as a ROOT Admin I am not having any read access to apps, I am able to see an empty WORK Stream when load balanced to Development Node....
Please let me know.
As asked earlier please let me know on my below ques :
- When logged into HUB >> load balanced on Node Purpose = Development
The WORK Area will show irrespective of whether I have Read access to unpublished Apps or not right? Because I am able to see empty WORK Area when Load Balanced on Development Node.