# /access-request-status endpoint - why is ORG\_ADMIN required to view access requests for others? **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** apis\ **Created:** [September 9, 2022, 2:46pm UTC](https://developer.sailpoint.com/discuss/t/access-request-status-endpoint-why-is-org-admin-required-to-view-access-requests-for-others/5739 "2022-09-09T14:46:05Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mcheek](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mcheek/32/23705_2.png) [@mcheek](https://developer.sailpoint.com/discuss/u/mcheek)\ **Post date:** [September 9, 2022, 2:46pm UTC](https://developer.sailpoint.com/discuss/t/access-request-status-endpoint-why-is-org-admin-required-to-view-access-requests-for-others/5739/1 "2022-09-09T14:46:05Z")
**Use Case** We need the ability to join data from ServiceNow to the /account-activities data so in Power BI we can include information about the request from the IDN side and include the link to the ServiceNow request. ![image](https://global.discourse-cdn.com/sailpoint/original/2X/c/c64bb99fe5b3b181b76f2be51a8253d1dcefc3f4.png) The ServiceNow workflow in the Service Catalog Integration has a step where it writes the accountActivityItemId to the ServiceNow record, so the join sequence is 1. ServiceNow (sn) to /access-request-status (ars) using sn.accountActivityItemId = ars.accountActivityItemId 2. /access-request-status (ars) to /account-activities (aa) using ars.accessRequestId = aa.id We use the completed date on the account activity record to show the “Provision Date” on the report. **Here’s the issue** Access to [the access-request-status endpoint](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) requires a token with ORG\_ADMIN access. Curiously, access to the /account-activities endpoint does not. **They have virtually the same data, so why does one require such elevated permissions?** **Workaround** If you utilize the clientMetadata object in the /access-requests payload, then you can put all the identifying information that you need there and link directly to the /account-activities record. We have done that, but it took us months to discover it was needed, so there are a bunch of records without clientMetadata on them, which is why the intermediate join using the /access-request-status data is required. ---
**Author:** ![mcheek](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mcheek/32/23705_2.png) [@mcheek](https://developer.sailpoint.com/discuss/u/mcheek)\ **Post date:** [October 4, 2022, 1:25pm UTC](https://developer.sailpoint.com/discuss/t/access-request-status-endpoint-why-is-org-admin-required-to-view-access-requests-for-others/5739/2 "2022-10-04T13:25:36Z")
@colin_mckibben since you’ve taken the time to edit my API documentation link, do you have any insight you can provide on my question? ---
**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Post date:** [October 4, 2022, 2:36pm UTC](https://developer.sailpoint.com/discuss/t/access-request-status-endpoint-why-is-org-admin-required-to-view-access-requests-for-others/5739/3 "2022-10-04T14:36:23Z")
Hi Mark, With the release of the new developer portal I had to update broken links in a lot of posts. I did forward your question to the product team, but with the Navigate conference happening this week it might take some time to get a response. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [July 19, 2023, 2:23pm UTC](https://developer.sailpoint.com/discuss/t/access-request-status-endpoint-why-is-org-admin-required-to-view-access-requests-for-others/5739/4 "2023-07-19T14:23:34Z")