# ServiceNow Catalog Widgets - Approvals & Tracking **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** access-requests, servicenow, sailpoint-identity-security\ **Created:** [September 8, 2026, 1:50pm UTC](https://developer.sailpoint.com/discuss/t/servicenow-catalog-widgets-approvals-tracking/221875 "2026-09-08T13:50:45Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Greg\_Zajac](https://avatars.discourse-cdn.com/v4/letter/g/c77e96/32.png) [@Greg\_Zajac](https://developer.sailpoint.com/discuss/u/Greg_Zajac)\ **Post date:** [September 8, 2026, 1:50pm UTC](https://developer.sailpoint.com/discuss/t/servicenow-catalog-widgets-approvals-tracking/221875/1 "2026-09-08T13:50:45Z")
I have read over the documentation available for the ServiceNow Catalog widget and have been able to implement the OOTB framework for requesting access. My question is, does there exists widget(s) so that an approver can use ServiceNow to action upon IdentityNow approvals within ServiceNow and/or a widget that a requester can track the status of their approvals within IDN/ISC while remaining in ServiceNow? Thanks! ---
**Author:** ![Deepak\_Chaudhary](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/deepak_chaudhary/32/34380_2.png) [@Deepak\_Chaudhary](https://developer.sailpoint.com/discuss/u/Deepak_Chaudhary)\ **Post date:** [September 8, 2026, 3:24pm UTC](https://developer.sailpoint.com/discuss/t/servicenow-catalog-widgets-approvals-tracking/221875/2 "2026-09-08T15:24:14Z")
Hi Greg, yes this looks possible and that requires to set up the Approval flow to _Configurable approvals_. `sysapproval_approver` this will map to the ServiceNow’s native approval module. After this the request can be approved using the OOTB ServiceNow **My Approvals** widget in the Service Portal. Upon actioning the ticket, ServiceNow automatically sends a payload to ISC that initiate the provisioning from back end. Please make sure that you are using the latest version of ISC service catalog application. ---
**Author:** ![Greg\_Zajac](https://avatars.discourse-cdn.com/v4/letter/g/c77e96/32.png) [@Greg\_Zajac](https://developer.sailpoint.com/discuss/u/Greg_Zajac)\ **Post date:** [September 9, 2026, 2:16pm UTC](https://developer.sailpoint.com/discuss/t/servicenow-catalog-widgets-approvals-tracking/221875/3 "2026-09-09T14:16:06Z")
Thanks Deepak, But what if you plan on using IdentityNow for approvals and not ServiceNow? ---
**Author:** ![punna0001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/punna0001/32/42011_2.png) [@punna0001](https://developer.sailpoint.com/discuss/u/punna0001)\ **Post date:** [September 10, 2026, 4:59am UTC](https://developer.sailpoint.com/discuss/t/servicenow-catalog-widgets-approvals-tracking/221875/4 "2026-09-10T04:59:02Z")
Hello Greg. If you want **ISC to handle the approvals** , set the Service Catalog **Approval Flow to None**. With `None`, ServiceNow raises the request in ISC without creating approval steps in ServiceNow. Any required approvals then follow your ISC access request configuration, so approvers would action them in ISC. For tracking, suitably entitled users can still view their own requests and status in the ServiceNow Portal under **Account Requests**. So, if approvals need to remain in ISC, `None` is the option I would use. Ref: [Configuring Approval Flow](https://documentation.sailpoint.com/connectors/servicenow/service_catalog/help/integrating_service_catalog/configuring_app_flow.html) | [Request and Review Access](https://documentation.sailpoint.com/connectors/servicenow/service_catalog/help/integrating_service_catalog/request_review_access.html) ---
**Author:** ![Greg\_Zajac](https://avatars.discourse-cdn.com/v4/letter/g/c77e96/32.png) [@Greg\_Zajac](https://developer.sailpoint.com/discuss/u/Greg_Zajac)\ **Post date:** [September 10, 2026, 2:14pm UTC](https://developer.sailpoint.com/discuss/t/servicenow-catalog-widgets-approvals-tracking/221875/5 "2026-09-10T14:14:15Z")
Harish thank you so much for your insights! ---
**Author:** ![kannan\_sb85](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kannan_sb85/32/35971_2.png) [@kannan\_sb85](https://developer.sailpoint.com/discuss/u/kannan_sb85)\ **Post date:** [September 10, 2026, 2:59pm UTC](https://developer.sailpoint.com/discuss/t/servicenow-catalog-widgets-approvals-tracking/221875/6 "2026-09-10T14:59:07Z")
@Greg_Zajac - Is the requirement “approvers must not leave ServiceNow” (a UX constraint), or is the requirement “we want one place to see everything” (a visibility constraint)? If the latter, `None` plus the Account Requests widget probably already satisfies that, and the custom widget is not worth building. ---
**Author:** ![Greg\_Zajac](https://avatars.discourse-cdn.com/v4/letter/g/c77e96/32.png) [@Greg\_Zajac](https://developer.sailpoint.com/discuss/u/Greg_Zajac)\ **Post date:** [September 10, 2026, 5:16pm UTC](https://developer.sailpoint.com/discuss/t/servicenow-catalog-widgets-approvals-tracking/221875/7 "2026-09-10T17:16:06Z")
Hi Kannan! The requirement is actually the first statement, attempt to keep all interactions with ISC contained within the pages of ServiceNow. That there’d be widget(s) similar to a user requesting access to then allow approvers to go into ServiceNow and execute any approval action like they would in ISC.