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

# Approving Access with Teams

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

***

### Reject a request

<figure><img src="/files/awrw4PAcEr6XEIbRCyqj" alt="" width="563"><figcaption><p>Team request message</p></figcaption></figure>

Follow these steps to reject a request:

1. In Teams, click **Apono**.
2. Review the request message.

{% hint style="info" %}
Each request appears as a separate message and contains the following information:

* An explanation why you are the approver of the request
* The request ID
* The **PENDING** status
* The user who made the request (**Requested by**)
* The **Resources** the user wants to access
* The **Permissions** the user is requesting
* The **Duration** of the access
* The justification for requesting access
  {% endhint %}

3. Click **Reject**. The **Please provide a reason for rejection** popup window appears.
4. Enter a **Reason**. The rejection reason must be less than **124** characters.

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

5. Click **Reject Request**. The requester will receive a notification in Teams that includes the rejection reason.

***

### 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/activity-overview/activity.md#force-approve-a-pending-request) the request from the **Activity** page in the Web Portal.

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

<figure><img src="/files/awrw4PAcEr6XEIbRCyqj" alt="" width="563"><figcaption><p>Team request message</p></figcaption></figure>

Follow these steps to approve a request:

1. In Teams, click **Apono**.
2. Review the request message.

{% hint style="info" %}
Each request appears as a separate message and contains the following information:

* An explanation why you are the approver of the request
* The request ID
* The **PENDING** status
* The user who made the request (**Requested by**)
* The **Resources** the user wants to access
* The **Permissions** the user is requesting
* The **Duration** of the access
* The justification for requesting access
  {% endhint %}

3. Click **Approve**. The **Please provide a reason for approval** popup window appears.
4. Enter a **Reason**. The approval reason must be less than **124** characters.

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

5. Click **Submit**. The requester will receive a notification in Teams.

{% hint style="warning" %}
Requests pending approval for over 7 days become Failed automatically.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apono.io/docs/access-requests-and-approvals/teams/approving-access-with-teams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.