Handle applications with multiple entitlement attributes

Hello All,

We have an application with multiple entitlement attributes in schema.
We wish users to request access for attribute X ( out of X, Y, Z ). Can we stop users to request Y, Z attributes if X is not done yet.

Our thought was making Y, Z non requestable entitlements but if we make it, they don’t show up on “Remove” request.

Any thoughts on this on how to achieve?

Thanks

Hi @pritishmhrn,

you use an identitySelector rule into quicklink population.
In this rule you hide the ent Y,Z for all identity dont have ent X.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.