> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/data-management/cancel-or-follow-up-on-an-app-access-approval.md).
# Cancel or follow up on an app access approval
Cancel a stalled app access approval or send the approver a reminder from the Waiting approval menu on a request, with each reminder logged on the request timeline
**Cancel or follow up on an app access approval**
Manually cancel a stalled app access approval or nudge the approver, right from the request.
**What this does**
Sometimes an app access approval sits pending too long — the approver is out, or the request is no longer needed. You can now step in directly from the request instead of waiting.
**How it works — step by step**
1. Open the request that has a pending app access approval.
2. Next to the *Waiting approval* status, click the *⋯* menu. You'll see two options: *Send reminder* and *Cancel*.
3. *To cancel*: click the cancel icon and confirm. Siit marks the app access approval as expired.
4. *To nudge the approver*: click the reminder icon. Siit sends a one‑click reminder immediately, and logs it as an event on the request timeline.
**Availability**
Available on the *Pro plan*.
**Frequently asked questions**
*Who can do this?* Any admin who has access to the request.
*Is this different from canceling a standard approval?* No, it's the same cancel/reminder mechanic you already use on standard approvals, now available for app access approvals as well.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.siit.io/guides/data-management/cancel-or-follow-up-on-an-app-access-approval.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
