Summary

Add a third action, “Close,” to unblock requests alongside Accept and Deny. It would let admins resolve a request without approving or rejecting it, and send the requester a custom message.

Problem

Admins can only Accept or Deny an unblock request. Requests are often resolved some other way: the issue was fixed out-of-band, the site was miscategorized and has since been recategorized, or the user no longer needs access. In those cases Deny is the only way to clear the request from the queue, and end users read it as a rejection. That creates confusion, follow-up tickets, and frustration for both sides.

Who’s Affected

Admins and IT teams who manage unblock requests through the dashboard and its historical view, and the end users who submit them.

Impact & Context

Deny doesn’t reflect what actually happened, which leads to repeat requests and helpdesk follow-ups.

The historical view loses accuracy because requests resolved another way are recorded as denials.

Admins can’t explain the outcome to the requester (“this was fixed by a policy change,” “this site has been recategorized”).

Desired Outcome

A “Close” action on unblock requests, separate from Accept and Deny.

An optional free-text field so the admin can send a custom message to the requester when closing.

Closed requests appear with their own status in the historical view and reporting.

Optionally, the same free-text message field on Accept and Deny.