Dealers Den

Use This Dashboard Area Safely

Use this guide when event setup, attendee operations, staff work, payment-adjacent tasks, public pages, or closeout records need a controlled path. In this guide, Dealers Den narrows that work to dealers Den settings, packages, applications, registrations, acknowledgements, and entitlements. Because this is a surfaces page, read it as part of the Event Management learning path rather than as an isolated checklist.

Event records become real-world instructions: what attendees see, what staff do, what money or inventory must reconcile, and what future organizers inherit. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What The Screen Controls

This page explains a specific surface. Treat every button, field, filter, and table as a way to view or change real records, not just as a visual layout. The intended readers are Dealers Den leads and Event leads. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/dealers-den?id=:eventId, /rego/events/manage/dealers-den-applications?id=:eventId, and /rego/events/manage/dealers-den-regos?id=:eventId.
• Records or contracts involved: Dealer packages, Dealer applications, and Dealer registrations.
• Main care point: Watch for changing one part of the event without checking attendees, staff, finance, communications, public information, and closeout records.
• Proof worth keeping: event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the Event Management situation, the owner, and the exact item involved in Dealers Den.
2. Read the current state before changing it: Use /rego/events/manage/dealers-den?id=:eventId, /rego/events/manage/dealers-den-applications?id=:eventId, and /rego/events/manage/dealers-den-regos?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the smallest action that matches the task: Keep Dealer packages, Dealer applications, and Dealer registrations in view so the work stays tied to the records or contracts it can affect.
4. Check the list, detail view, history, or public page afterward: Before handing off, save proof such as event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff so the next operator can see what changed and why it was safe to continue.

Before You Leave The Screen

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on attendees, staff, money, public pages, communications, and post-event records.
3. Proof is findable: The handoff points to evidence that the next operator can see what changed and why it was safe to continue.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Anchor the work to one event. Open Dealers Den settings for the correct event. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Define dealer eligibility, application questions, packages, acknowledgements, limits, and review owners before opening applications. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Change only the intended event setting or record. Review each application using the same criteria and record clear approval or rejection reasons. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Confirm dealer registrations, package entitlements, payments, and attendee registration links are consistent. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Save changes and check the public Dealers Den page or application entry point. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. Escalate conflicts, unclear criteria, or capacity issues before sending decisions. This leaves a handoff trail another operator can understand.

Purpose

Dealers Den tools manage vendor applications, packages, acknowledgements, approval decisions, and dealer registrations.

Key responsibilities

• Make package rules clear.
• Review applications consistently.
• Record approval or denial decisions.
• Keep entitlements aligned with packages.
• Ensure dealer registration records match event capacity and policy.

Common mistakes

• Changing package rules after applications open without telling applicants.
• Approving more dealers than space allows.
• Recording decisions in chat but not in the dashboard.
• Forgetting acknowledgements or required terms.
• Mixing attendee registration and dealer registration states.

Verification

• Settings save and reload.
• Packages order correctly.
• Applications can be reviewed.
• Dealer regos appear in the expected surface.
• Denials and approvals are visible to permitted staff.