> 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/google-chat/approving-access-with-google-chat.md).

# Approving Access with Google Chat

How to approve or reject Apono access requests

The Apono Google Chat app enables you to reject or approve a request to access services, databases, and applications that are centrally managed through Apono.

***

### Approve a request

{% hint style="success" icon="lightbulb" %}
If a pending request is blocked because the assigned approver is unavailable, an Admin can [force approve](/docs/audits-and-reports/requests-audit/activity.md#force-approve-a-pending-request) the request from the **Activity** page.

Force approval bypasses the configured approval flow and is recorded in the request timeline.
{% endhint %}

Follow these steps to approve a request:

1. On the request notification card, click **Approve**. The **Approval Reason** pop-up window appears.
2. In the **Please provide a reason for Approval** field, enter a reason that is less than **124 characters** long.

{% hint style="info" %}
If the [**Require Approve Reason**](/docs/access-flows/creating-access-flows-in-apono/self-serve-access-flows.md#enable-iga-settings) setting has been enabled for the access flow, you will be required to enter a reason.
{% endhint %}

3. Click **Submit**. The status of the request card updates to Approved. The requester will see the approved request and the remaining access duration on the [**My Requests**](https://portal.apono.io/my-requests?status=active) tab.

***

### Reject a request

Follow these steps to reject a request:

1. On the request notification card, click **Reject**. The **Reject Reason** pop-up window appears.
2. In the **Please provide a reason for Rejection** field, enter a reason that is less than **124 characters** long.

{% hint style="info" %}
If the [**Require Approve Reason**](/docs/access-flows/creating-access-flows-in-apono/self-serve-access-flows.md#enable-iga-settings) setting has been enabled for the access flow, you will be required to enter a reason.
{% endhint %}

3. Click **Submit**. The status of the request card updates to **Rejected**. The requester will see the rejected request on the [**My Requests**](https://portal.apono.io/my-requests?status=rejected) tab.


---

# 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/google-chat/approving-access-with-google-chat.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.