> ## Documentation Index
> Fetch the complete documentation index at: https://help.taack.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage requests

> Review, approve, and deny ticket requests when attendance requires approval.

Some events need you to approve patrons before their ticket is confirmed. Taack calls these ticket requests.

## When requests are created

A patron submits a request instead of an immediate purchase when:

* **Attendance requires approval** is enabled on the event, or
* A specific ticket type is marked as **Request only**

The patron completes checkout (or submits their details for free events), and the sale enters a requested state. They see the ticket under **Pending** in their wallet until you act on it.

## Review requests

You can review requests from two places:

| Location                              | Scope                                                                    |
| ------------------------------------- | ------------------------------------------------------------------------ |
| **Requests** in the dashboard sidebar | All pending requests across your committee's events                      |
| **Requests** tab on a specific event  | Requests for that event only (tab only appears when approval is enabled) |

The **Requests** sidebar item shows a count badge whenever something is waiting on you.

Each request shows the requester's name, ticket type, quantity, and any custom question responses they submitted at checkout.

## Approve or deny

<Steps>
  <Step title="Open the request">
    Click a pending request to see full details.
  </Step>

  <Step title="Approve">
    Click **Approve** to confirm the patron's ticket.

    * For **paid tickets**, approving triggers payment capture on the patron's saved card.
    * For **free tickets**, the ticket is confirmed immediately.
    * The patron receives confirmation and the ticket moves from **Pending** to **Upcoming** in their account.
  </Step>

  <Step title="Deny">
    Click **Deny** to decline the request. The patron is notified and no charge is captured for paid requests that were still pending.
  </Step>
</Steps>

<Warning>
  For paid request-only tickets, the patron's card is authorized at checkout but not charged until you approve. Denied requests do not result in a charge.
</Warning>

## Payment plan requests

If a request was started on a [payment plan](/organizers/payment-plans), it carries a **Payment plan** badge showing the **Deposit** and **Total plan** amounts, with payment status **Authorized**.

* **Approve** charges only the deposit and starts the plan. The payment schedule is finalized at that moment.
* **Deny** releases the reserved tickets — nothing was charged.
* The patron's later plan payments never come back through your approval queue.

## Team members and requests

Committee **Members** and **Admins** assigned to an event can also review requests from their dashboard. This helps distribute guest-list management across your team without giving everyone full organizer access.

## Tips for approval workflows

<Tip>
  Enable **Attendance requires approval** at the event level when every ticket type needs review. Use **Request only** on individual ticket types when only certain tiers — like VIP or comp lists — need approval.
</Tip>

<Tip>
  Keep an eye on **Requests** as your event approaches. Patrons waiting on approval may follow up if they don't hear back quickly.
</Tip>

## Next steps

* [Sales](/organizers/sales) — view confirmed sales after approval
* [Check in guests](/organizers/check-in) on event day
* [Create an event](/organizers/create-an-event) — configure approval settings