> For the complete documentation index, see [llms.txt](https://docs.apono.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apono.io/docs/access-requests-and-approvals/slack/reviewing-historical-requests-with-slack.md).

# Reviewing historical requests with Slack

Use the Apono Slack app to review approved or rejected requests

If you're responsible for approving access requests, visibility into your past decisions is essential for accountability and compliance.

The **History** section in the Apono Slack app shows the **10 most recent** access requests you have handled. This enables you to audit your own decision history and streamline follow-up actions.

From this tab, you can:

* Review details of previously handled access requests
* Understand request context, justification, and duration
* Track trends in the access requests you have handled

{% hint style="success" %}
If you need to audit requests across your entire organization, you should use the **Activity** and **Reports** pages in the Admin UI. Read the [Activity Overview](https://docs.apono.io/docs/audits-and-reports/activity-overview.md) to learn more.
{% endhint %}

***

### Review handled requests

<figure><img src="https://1094436629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv6MBfUGvblSdAz31yJXm%2Fuploads%2Fgit-blob-29f7b8e2558df7a0851c178cf791cf390c70357c%2Fslack-history.png?alt=media" alt="" width="563"><figcaption><p>Apono Slack app History</p></figcaption></figure>

Follow these steps to review access requests you have approved or rejected:

1. In the Apono Slack app, click **Home > My Tasks > History**. A list of the most recent requests you have approved or rejected appears.
2. Review the pending request.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Each request contains the following information:</p><ul><li>Request <strong>ID</strong></li><li><strong>Requestor</strong> who made the request</li><li><strong>Integrations</strong> containing the resources to be accessed</li><li><strong>Resource Types</strong> to be accessed</li><li><strong>Requested Duration</strong></li><li><strong>Justification</strong> for requesting access</li><li>Current <strong>Status</strong> of the request.</li></ul></div>
3. Click **More Details** to view the full request message on the **Messages** tab.
4. To view more than the last 10 requests, click **See more tasks**. The **History** tab in the Web Portal opens.


---

# 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.apono.io/docs/access-requests-and-approvals/slack/reviewing-historical-requests-with-slack.md?ask=<question>&goal=<user_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.
