# Access Request User Population and Request for Others Population scoping **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** identity-security-cloud\ **Created:** [March 18, 2025, 4:20pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715 "2025-03-18T16:20:56Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![David\_Norris](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@David\_Norris](https://developer.sailpoint.com/discuss/u/David_Norris)\ **Post date:** [March 18, 2025, 4:20pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/1 "2025-03-18T16:20:56Z")
Somewhat related to this: > [@How I can filter available identities by some attributes in the Request Center?](https://developer.sailpoint.com/discuss/t/how-i-can-filter-available-identities-by-some-attributes-in-the-request-center/104014): > > Hello everybody, I would like that in the request center, when I request an access item for others, the identities that are of my interest are shown, meaning that they are filtered based on a specific attribute of mine, such as only identites that are under my “company” are shown and not all the identities on Sailpoint. Anyone knows how I can obtain that? There seems to be no way to finely / custom-define the scope of which users can use access request, and which users can Request On Behalf Of others (except via Managers, or Everyone option): ![image](https://global.discourse-cdn.com/sailpoint/original/3X/d/5/d5bd262e7314924f68251d26e27cdc6d3fe97d23.png) Access Request seems to be a tenant-wide feature. And that if I have a Request On Behalf Of use case, I can only scope either Managers, or Everyone, can request for others. In the Everyone case, that would mean, anyone can search for anyone’s name / existence via Access Request. How are others getting around / avoiding this exposure scenario? ---
**Author:** ![kdfreeman](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kdfreeman/32/22737_2.png) [@kdfreeman](https://developer.sailpoint.com/discuss/u/kdfreeman)\ **Post date:** [March 18, 2025, 4:26pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/2 "2025-03-18T16:26:16Z")
I think you need to look for segments for your requirements. > **[Managing Access Request Segments - SailPoint Identity Services](https://documentation.sailpoint.com/saas/help/requests/segments.html?h=segments)** > > SailPoint Identity Services Documentation > **[Segments | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/v3/segments/)** > > Segments ---
**Author:** ![David\_Norris](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@David\_Norris](https://developer.sailpoint.com/discuss/u/David_Norris)\ **Post date:** [March 18, 2025, 4:28pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/3 "2025-03-18T16:28:47Z")
My understanding is that Segments only control the search-ability / visibility of access items (roles / access profiles / entitlements). It doesn’t control the search-ability / visibility of identities. This statement from the doc: “Admins can add access items to segments to make this access visible only to users included in these segments” i.e. Segment is a viewability relationship between Identities and access items, but not between identities and identities. ---
**Author:** ![kdfreeman](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kdfreeman/32/22737_2.png) [@kdfreeman](https://developer.sailpoint.com/discuss/u/kdfreeman)\ **Post date:** [March 18, 2025, 4:41pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/4 "2025-03-18T16:41:57Z")
Yes, at this point, there are two options as you have shown. If you select Everyone, all can request access on behalf of others. Refer this thread: [Request for Others - Manager Info - #8 by Tulasi](https://developer.sailpoint.com/discuss/t/request-for-others-manager-info/104670/8) ---
**Author:** ![David\_Norris](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@David\_Norris](https://developer.sailpoint.com/discuss/u/David_Norris)\ **Post date:** [March 18, 2025, 4:46pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/5 "2025-03-18T16:46:51Z")
Yikes…two options, and neither is suitable. ---
**Author:** ![KRM7](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/krm7/32/2685_2.png) [@KRM7](https://developer.sailpoint.com/discuss/u/KRM7)\ **Post date:** [March 18, 2025, 4:51pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/6 "2025-03-18T16:51:29Z")
> [@David\_Norris](#): > > Access Request seems to be a tenant-wide feature. And that if I have a Request On Behalf Of use case, I can only scope either Managers, or Everyone, can request for others. > > In the Everyone case, that would mean, anyone can search for anyone’s name / existence via Access Request. Yes, that is correct. We are ok with this. No one will request access for others unless it is required and of course we will have approvals configured for access items, so no problem for us. Yes, there should have been some customization here apart from Managers or everyone request for others, you can create an idea for that. ---
**Author:** ![David\_Norris](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@David\_Norris](https://developer.sailpoint.com/discuss/u/David_Norris)\ **Post date:** [March 18, 2025, 4:52pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/7 "2025-03-18T16:52:51Z")
> [@KRM7](#): > > We are ok with this. The concern is that anyone / everyone authenticated in the tenant can lookup anyone’s existence in the tenant. This also has some minor overlap with consent / preference management. Some users / identities don’t want / need to be searchable for access request use cases. ---
**Author:** ![David\_Norris](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@David\_Norris](https://developer.sailpoint.com/discuss/u/David_Norris)\ **Post date:** [March 18, 2025, 5:20pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/8 "2025-03-18T17:20:17Z")
> [@KRM7](#): > > you can create an idea for that. Lost feature parity from IIQ. It’s not like it needs a ‘new’ idea. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [May 17, 2025, 5:20pm UTC](https://developer.sailpoint.com/discuss/t/access-request-user-population-and-request-for-others-population-scoping/104715/9 "2025-05-17T17:20:53Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.