Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I always found it weird that Sense does not have a proper way of handling "Roles",
that is a way to explicitly create them and delete them.
As it is now a role named "NewRole" is "automagically" created when you create security rules having user.roles="NewRole" as part of the condition,
and they are deleted when those security rules are deleted - but only in the sense that they cannot be added to users that did not have that role. The users that already had the role still have it! 🙄
And it is not possible to filter or sort on Admin Roles in qmc/users...
@gandalfgray, it would be concerning if the access rule originally tied to the new Role was still allowing access, otherwise a new Role can be granted to the user; Have you found any different?
@Andre_Sostizzo , eh, no.
But that was not the point of my post.
The point was that there is no real "Role" object,
and that if you delete all security rules using a "Role" the role is not listed in the "Role" dropdown for users, but the Role still exist on any user that had it granted before.
@gandalfgray, understood. I think the problem where the Role remains assigned to the user would be treated as a new Feature Request (Idea) by R&D.
Qlik has recently release a new way to submit Feature Requests through the Community Idea page without the need for opening a Support case. Please feel free to submit your request.
https://community.qlik.com/t5/Ideas/idb-p/qlik-ideas
For the issue where we cannot sort or filter by Admin Role, the FR has been documented under https://support.qlik.com/articles/000099389