Share all details related to your problem, including any error messages you may have received.
Hello Experts,
I must show only contractors’ user type in Identity Operations for Rapid Setup Termination process. Since Identities → Identity Operation is not a Quicklink, We cannot use Dynamic scopes here. Please let me know if we can filter the identities and show only specific identities when the user clicks Identities → Identity Operation. (By default employees should not appear here in selectIdentities suggestion)
Hello Emanuele, Sorry if my ask is not clear. We know we have capability “RapidSetupIdentityOperationsAdministrator” which provides access to Identity Operation under Identities. The ask is once someone clicks the Identity Operation, I am able to see all the identities in the system and terminate it. The requirement is, in this screen I should see only few users maybe based on “User type = Contractor” by default and hide all the employee in the Identity Selection screen. Is this possible with any configuration OOTB?
sorry for the question, why dont use an identityselector in quicklinks populations?
otherwise you need create a custom spright and add to this capability
Identity Operation is not a Quicklink. Hence Dynamic scope cannot be applied here.
Capability & SPright is to provide access to a menu item i.e Identity Operation. Our requirement is not around this and instead restricting identities displayed in Identity selection screen when Identity Operation is clicked. So capabilities is of no help here
I searched a lot and I dont find a good method for restricting identities in this case.
I think to solution but I dont know if resolve your case.
The first is create a quicklink with a filter rule or match critiria and assing this to a workgroup; for example a workgroup can view the external and anthor for internal, but applies for all pages.
Also, you can create a plugin and remove the FullAccessTerminateIdentity capability for all users.
Or you need to find the class that SP uses in this page and change it for filter the identities
Hello @ashutosh08 & @enistri_devo,
Thank you for your response.
Scoping is a good option to consider as all other options involves more customization like changing xhtml pages or creating a custom quicklink & workflow.
Do we know if we can use Configuration-> IdentitySelectorConfiguration for this requirement?
As mentioned by other community member it will be a global change and your use-case is to just restrict the data to be viewed by user, so scope is looking best for it.
But before considering do analyze thoroughly as it will also be a global change.