# Deny Access Removal Requests

**URL:** <https://developer.sailpoint.com/discuss/t/deny-access-removal-requests/173570>\
**Category:** SHF Discussion and Questions\
**Tags:** workflows, access-requests, sailpoint-identity-security\
**Created:** [August 26, 2025, 8:09pm UTC](https://developer.sailpoint.com/discuss/t/deny-access-removal-requests/173570 "2025-08-26T20:09:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [August 26, 2025, 9:14pm UTC](https://developer.sailpoint.com/discuss/t/deny-access-removal-requests/173570/2 "2025-08-26T21:14:14Z")

</div>

Use the Access Request Submitted Request/Response trigger and a workflow to achieve this. I had a similar use case when we only wanted certain people submitting access requests, so the workflow checked whether or not the user had a particular entitlement and returned approved=false if they didn’t

> [@Implementing A Request Response Type Trigger in Workflows](https://developer.sailpoint.com/discuss/t/implementing-a-request-response-type-trigger-in-workflows/10216):
>
> At the time of this writing, SailPoint Workflows does not have native support for our [request response type](https://developer.sailpoint.com/docs/extensibility/event-triggers/trigger-types/#request-response) triggers, such as the [Access Request Submitted trigger](https://developer.sailpoint.com/docs/extensibility/event-triggers/triggers/access-request-submitted). However, there is a way to implement request response triggers using the current capabilities of Workflows. This guide will demonstrate how to configure a Workflow that can successfully receive events from the Access Request Submitted trigger as well as respond wi…

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/deny-access-removal-requests/173570)._
