<!-- generated by php artisan docs:split-brd from brd/BRD-Morvia-Project-Guide-en.md — edit the BRD, not this file -->

#### ADM-022 | Events management
**Source:** p.113–114, p.134–135 · **Actor:** admin
- **Built as (TD-43):** `GET /admin/events[/{id}]`, `POST /admin/events/{id}/suspend|reactivate`; the admin does not add or edit (an event belongs to a provider). Events are not related to a course for now.
- The admin views the events added by providers. **Linked to a Morvia course:** shows the linked course,
  with navigation to its details. **External:** name · image · description · city · date · external link.
- **Events screen (p.134–135):** event name · organiser · city · date · external link · status
  (**Published** · **Inactive / ended**). Actions: **add** · edit · activate / deactivate.
- **Rules:** registering for or booking an event happens outside the platform through the link; the
  internal payment gateway is not used; **no approval workflow** for events before publishing in the
  current scope; no multiple reviews of an event; the admin can follow and suspend events without a
  separate approval cycle.

**Acceptance, rules and screen notes citing ADM-022:**

- BR-EVT-01 — Events have no approval workflow; external events are redirect links with no booking or payment in Morvia. — HPV-014, ADM-022, TRN-016
- BR-ADMIN-HALL-20 — The admin can follow and suspend events without a separate approval cycle. — ADM-022
