> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/events/manage-opened-events/manage-requesters.md).

# Manage requesters

When working on an event, you can add a requester to the event so they can view the event in their events list, add internal notes, and participate in conversations with suppliers.

{% hint style="info" %} <mark style="color:purple;">**Note**</mark><mark style="color:purple;">: A requester can be added to an event in a Draft, Opened, Closed, Awarded, or Canceled status.</mark>
{% endhint %}

{% hint style="info" %} <mark style="color:purple;">**Note**</mark><mark style="color:purple;">: You can add a requester even if they did not initially request an event.</mark>
{% endhint %}

### Add a requester <a href="#addarequester" id="addarequester"></a>

{% stepper %}
{% step %}
From the Events list or the event Details screen, select **Actions > Add Requester**.\
The Add Requester dialog box displays.
{% endstep %}

{% step %}
In **Requester Name**, enter a requester's name. As you type, matching users with the Requester role display.
{% endstep %}

{% step %}
Click **Add**. The user is added as requester, and a label with their name will now display on the event.
{% endstep %}
{% endstepper %}

### Change a requester <a href="#changearequester" id="changearequester"></a>

If a requester has already been associated with an event, you may need to update the event with a new requester.

{% stepper %}
{% step %}
From the Events list or the event Details screen, select **Actions > Change Requester**.\
The Change Requester dialog box displays.
{% endstep %}

{% step %}
In **Requester Name**, click the **Remove** :x: button, and enter the new requester's name. As you type, matching users with the Requester role display.
{% endstep %}

{% step %}
Click **Update**. The new user is added as requester, and a label with their name will now display on the event.
{% endstep %}
{% endstepper %}

### Remove a requester <a href="#removearequester" id="removearequester"></a>

{% stepper %}
{% step %}
From the Events list or the event Details screen, select **Actions > Change Requester**.\
The Change Requester dialog box displays.
{% endstep %}

{% step %}
Select the **Remove the requester** check box. The Requester name field is disabled.

{% endstep %}

{% step %}
Click **Update**. The requester is removed from the event.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fairmarkit.com/buyers/events/manage-opened-events/manage-requesters.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.