> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/deals/administering-transactions.md).

# Administering Transactions

Transactions Admin gives authorized brokerage staff a centralized place to locate Deals, monitor incoming work, review submitted documents, communicate with agents, and more.

This administrative experience provides broader visibility and additional tools beyond the agent-facing **My deals** dashboard.

{% hint style="info" %}
This section is intended for authorized Transaction Coordinators, compliance staff, Brokerage Administrators, and other team members responsible for reviewing or managing transactions across the brokerage. Available Deals, tools, and permissions vary by role and brokerage.
{% endhint %}

### What can transaction administrators do?

Depending on their permissions and brokerage configuration, authorized staff can use Transactions Admin to:

* Search for Deals across their office, or brokerage.
* Locate transactions by property, MLS number, agent, office, status, and other available information.
* Monitor operational inboxes.
* Identify Deals and documents that require attention.
* Review transaction information and important dates.
* Review submitted documents.
* Approve or decline documents.
* Provide feedback to agents.
* Monitor missing or incomplete requirements.
* Manage transactions through the brokerage’s closing process.
* Access available transaction reporting and exports.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FyHGezTPwZ0eDQCfNoBeC%2F2026-08-19_15-30-09.png?alt=media&amp;token=32c3abdb-7d8f-41fa-b887-8ebc7c93b0d1" alt=""><figcaption></figcaption></figure>

### How the Admin experience differs

Agents primarily use **My deals** to create and manage transactions in which they are involved.

Authorized staff use **Transactions Admin** to oversee Deals within the offices, teams, or brokerage areas included in their permissions.

The Admin dashboard may include:

* Brokerage-wide Deal search
* Contract Inbox
* Escrow Release
* Listing Inbox
* Notifications settings
* Advanced filters
* Submission times
* Administrative analytics and exports

The exact dashboard, inboxes, and available actions depend on the brokerage’s configuration and the administrator’s assigned permissions.

### Understand the transaction review process

A common office-review workflow follows this general process:

1. An agent creates and completes the appropriate Deal information.
2. The agent uploads or prepares the required documents.
3. The agent makes the Deal visible to the office when required.
4. The agent notifies the office that a document is ready for review.
5. An authorized staff member opens the Deal and reviews the submitted document.
6. The document is approved or declined.
7. If declined, the agent reviews the feedback, corrects or replaces the document, and submits it again.
8. The office continues monitoring the transaction through closing.

Your brokerage may use a different review process or require additional steps.

### Administrator visibility and permissions

Administrative access does not always provide visibility into every Deal in Rechat. The transactions and tools available to you may depend on:

* Your assigned office or offices
* Your brokerage role

If an expected Deal is unavailable, confirm that the Deal has been shared or submitted correctly and that your role includes access to the appropriate office or transaction.

### Maintain a clear review history

When reviewing transactions:

* Keep feedback specific and actionable.
* Explain why a document was declined.
* Identify the missing information or correction needed.
* Keep transaction-related communication connected to the Deal.
* Confirm that replacement documents are added to the correct checklist item.
* Review important dates and Deal information alongside the documents.
* Avoid approving incomplete or incorrectly assigned files.

Clear feedback helps agents resolve issues faster and creates a more useful transaction history for everyone involved.

### Get started

* [Navigate the Transactions Admin Dashboard](/guides/deals/administering-transactions/navigate-the-transactions-admin-dashboard.md)
* [Review Transactions and Documents](/guides/deals/administering-transactions/review-transactions-and-documents.md)

### Related articles

* [Understand Your Deal Workspace](/guides/deals/understand-your-deal-workspace.md)
* [Understand Your Transaction Checklist](/guides/deals/understand-your-transaction-checklist.md)
* [Submit Documents for Office Review](/guides/deals/submit-documents-for-office-review.md)
* [Manage a Deal Through Closing](/guides/deals/manage-a-deal-through-closing.md)


---

# 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://help.rechat.com/guides/deals/administering-transactions.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.
