Can we use organization and/or organization hierarchy to publish application and entitlements?

[Kramerica]

We have a requirement where certain applications and entitlements should only be available to request to certain users. (A requirement that was implemented in our legacy tool).

Can we use organization hierarchy to put these users in those organization and then publish End Points and Entitlements to that organization? 

Has anyone implemented it?

[rushikeshvartak]

You need to use dynamic attributes for filtering.  you can't use organizations in ARS 

[PremMahadikar]

Hi @Kramerica ,

I am not sure for your usecase, if organization hierarchy will help.

As suggested by Rushikesh, use dynamic attribute (DA) for any user's attribute (editable by user can be option), then Endpoint -> entitlement type -> "Config for Requestable Entitlement in ARS" can be used for filtering the entitlements based on users' attributes. Achieved by DA in ARS and hardcoded value in all entitlements to have mapping of selected users' attributes. Organization can be one of the user's attributes to filter. (Link for entitlement type filter)

Endpoint -> "Access Query" can be used for filtering endpoints based on users' attributes (refer link on access filter)

If this answers your question, please consider selecting Accept As Solution and hit Kudos

[nimitdave]

@Kramerica , you can explore usage of access query in the endpoint details tab of the particular endpoint. Using this query you can limit the applications visible to the logged in user as per their properties.

[Kramerica]

@nimitdave 

Our requirement is to filter entitlements for an application not the application itself. 

[PremMahadikar]

@Kramerica , Did you try with dynamic attribute to filter entitlements for an application? (as suggested above)