> For the complete documentation index, see [llms.txt](https://docs.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2core.b2broker.com/how-to-articles/manage-clients/how-to-identify-who-resolved-client-requests.md).

# How to identify who resolved client requests

To find the Back Office user who approved or rejected a specific client request:

{% stepper %}
{% step %}
Navigate to **Clients** > **Requests**.
{% endstep %}

{% step %}
Locate the needed request.

{% hint style="info" %}
By default, the list is filtered by the `Pending` status. Clear the **Status** filter to view all requests.

To narrow your search, apply other filters such as **Client name**, **Client email**, **Country**, the request's **Type**, **Status** (`Approved` or `Rejected`), or a date range.
{% endhint %}
{% endstep %}

{% step %}
Check the **Processed by** column to see the email address of the Back Office user who resolved the request. This same **Processed by** information is also displayed in the upper-right corner of the request details page.
{% endstep %}
{% endstepper %}


---

# 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.b2core.b2broker.com/how-to-articles/manage-clients/how-to-identify-who-resolved-client-requests.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.