> 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/reassign-an-event.md).

# Reassign an event

Sometimes, you may need to reassign an event from one buyer to another. If you have access to this option, you can use this option to reassign events quickly. Users in an Observer role cannot reassign events.

### Reassign an event <a href="#reassignanevent1" id="reassignanevent1"></a>

To reassign an event from one buyer to another in your organization, do the following:

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

{% step %}
In **Reassign this RFQ from to**, select a buyer from your team.

{% endstep %}

{% step %}
Click **Confirm**. The event is reassigned to the selected buyer.
{% endstep %}
{% endstepper %}

### Reassign multiple events <a href="#reassignmultipleevents" id="reassignmultipleevents"></a>

To reassign multiple events to a buyer in your organization, do the following:

{% stepper %}
{% step %}
From the Events list, select one or more events. A blue banner displays at the top of the list, confirming the number of events you selected.
{% endstep %}

{% step %}
Click **Reassign**. The Reassign RFQs dialog box displays. The ID for each selected event displays.
{% endstep %}

{% step %}
From the drop-down list, select a buyer from your team.
{% endstep %}

{% step %}
Click **Confirm**. The events are reassigned to the selected buyer.
{% 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.fairmarkit.com/buyers/events/manage-opened-events/reassign-an-event.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.