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

#### HPV-004 | Hall features (from the admin master list)
**Source:** p.73–74 · **Actor:** provider, admin
- The system holds one **master list** of hall features, created and managed by the **admin**
  (ADM-016). Examples: meals · break · display screen · sound system · extra equipment · any other
  feature the admin approves.
- The provider **cannot create** new features. When adding or editing a hall the provider: (1) picks
  the features available in the hall from the predefined list; (2) sets a **fixed extra price per
  selected feature**.
- **Rules:** the feature list is the admin's responsibility only; the provider selects, never creates;
  a feature price is set **per hall**; a feature price is **fixed per booking slot** and charged **once
  per slot** in the request; it is **not** charged per hour or per attendee; the same selected
  features apply to **all slots** of one request; features have **no quantity** and **no dependencies**.

**Acceptance, rules and screen notes citing HPV-004:**

- WF-10 — Hall provider onboarding — External contract → admin creates provider account → credentials sent → provider adds halls, features, prices, availability — ADM-015, HPV-001, HPV-003, HPV-004, HPV-006
- BR-HALL-04 — The master list of hall features is managed by the admin only. — HPV-004, ADM-016
- BR-HALL-05 — The provider picks the features available in each hall and sets a fixed extra price per feature; a feature price is charged once per slot in the booking request. — HPV-004, HPV-005
- BR-ADMIN-HALL-03 — The admin does not set the feature price per hall; the provider does. — ADM-016, HPV-004
