If I understand correctly, Distribution Lists (DLs) can solve your problem.
You can create a list for "development group" and another for "admin group" and use those to control access. Maintenance would then be done on the respective DLs, not on QMC.
Access to the Qlikview Management Console (QMC) is controlled by membership in the local (local to the windows machine where the Qlikview Management Service is running) widows group "Qlikview Administrators".
Anyone can access the Access Point page. What documents they actually see listed is controlled by what documents they have windows security READ access to (if using NTFS mode) or the document permissions assigned in the QMC (if using DMS mode). The permission may be granted to specific userids and/or Active Directory groups.
These are two seperate permission mechanisms. A userid can be a member of "Qlikview Administrators", and therfore have access to the QMC, but have no access to any documents in Access Point. The converse is also true.
I do see that there is "qlikview adminstrator" group in our windows server manager
windows->server manager->local user and groups-> groups-> qlikvew adminstrator.
And few people have been added to that group.
Question is how does qlikview application know that people in that group should have access to QMC
say if xxx is in that group and yyy is not in that group. yyy is part of "Qlikview developer" group.
How does it differentiate yyy cant login to QMC.
How can I give read/write priv per user
I come from informatica background and it works in a diferent way. Where it has all groups and users can be set inside the Inforamtica application it self.
