Skip to main content
Source snapshot: 13 October 2026. These pages describe the current implementation, including unfinished controls. See coverage and review notes.

​
Event detail

Host: admin.<ROOT_DOMAIN> · Route: /[tenant]/events/[eventId]

​
Purpose and access

Inspect an event’s registrations and associated income/expenditure.You need an account session and a resolved membership context in the selected Mahallu (including the API’s current platform elevation path). The API independently checks the requested operation’s permissions and feature availability.

​
Screen layout

The page shows the event heading, a Registrations table, and Income & expenditure. Registration actions operate on event-specific records.

​
Fields and displayed information

Displayed table columns: Participant, Phone, Attended, Actions.

​
Fields and filters: Event registrations table

​
Actions

​
Linked navigation

​
Interaction sequence

Open an event from Events → enter a participant name and optional phone → Register → the fields reset and the list refreshes. Toggle attendance for a saved participant or confirm removal → refresh. Review linked financial records in the income/expenditure panel.

​
States and rules

The event is resolved within the tenant. Missing or unavailable events use notFound. Registration status changes and finance totals are separate concerns.The rendered action controls bind loading indicators to pending state. Failed API saves keep their documented error/notification path; a loading indicator alone does not establish persistence.

​
Implementation references

Paths below are relative to the application repository. This is source-reviewed behavior, not a recorded browser test.
  • apps/web/src/app/sites/admin/[tenant]/events/[eventId]/page.tsx
  • apps/web/src/features/tenants/event-registrations-table.tsx
Data and access helpers: apps/web/src/lib/session.ts, apps/web/src/lib/server-api.ts, apps/web/src/lib/tenants.ts, apps/web/src/lib/event-detail.ts, apps/web/src/lib/business-resources.ts, apps/web/src/lib/api-client.tsRelevant controller permission keys: events.view, events.create, events.update, events.delete, finance.view. Keys are operation-specific; the current guard grants OWNER/ADMIN and its platform-elevation context an operational bypass. A visible control still does not establish authorization.

​
API behavior references

  • apps/api/src/events/event-registrations.controller.ts
  • apps/api/src/events/events.controller.ts