Skip to main content

Event applications, staff, and venues

Beyond the event record itself, these resources handle how an event was requested, who runs it, and where it happens.

Event applications​

An event application is a request to run an event. Operators review these at https://core.mlhtools.com/resources/event_applications.

  • Name: the applicant/event name.
  • Status: the application's state. When it is approved, rejected, or withdrawn, the matching timestamp (Approved at / Rejected at / Withdrawn at) is set, and for rejections and withdrawals the Rejection reason / Withdraw reason is recorded.
  • Manage URL: a link to manage the application.
  • CRM ID, CRM type, CRM stage: link the application to the CRM.
  • Logo: the event's logo.
  • Response and Metadata: the raw application answers and metadata (JSON).

Each application belongs to an event and has application submitters.

:::info Maintainer note Add the review workflow: who reviews applications, what the statuses are and what each means, and how CRM stage maps to the review process. (Event-application reviews also happen in Organizer HQ — clarify which system is the source of truth.) :::

Event staff​

Event staff are the people working an event (https://core.mlhtools.com/resources/event_staffs).

  • User: the staff member.
  • Role: one of event staff, observer, or coach on call.
  • Lead: whether this person is the event's lead. Each event has a single lead — if none is set, the first staffer added becomes the lead automatically.

:::info Maintainer note Explain what each role can do and when to assign coach on call vs observer. :::

Event venues and addresses​

An event address attaches a location to an event. Its address type can be Venue, Shipping, or Loading Dock, alongside the standard address fields (contact details, street lines, city, state, postal code, country). See Participants and member records → Addresses for the full field list.

Event submissions​

Event submissions are the project-first submissions for an event — the single project a hacker submits when the event uses the project-first flow. They don't carry the per-challenge review fields (winner, challenge, status) — that's what challenge submissions are for. See Programs and submission flows.