Core code mergedBackend
The service that checks permissions, stores attendance and supports reporting.
People, groups and sessions
Each person can belong to one standing group or be unassigned. Leaders enroll people in events explicitly. Attendance belongs to a dated session of an event.
Attendance and follow-up
The API supports session rosters, recording and correcting attendance, and scoped summaries for the dashboard. The roster distinguishes present, absent and unmarked. Safe retries help prevent repeat submissions from creating duplicate changes.
Permissions and audit history
People and connected apps need permission for the action and access to the relevant record. A denial on a particular record takes priority. Audit history records changes in a linked sequence that can be checked for tampering.
File sharing and uploads
Approved users can upload files directly to private storage. The November 20 change lets the portal renew an upload form within its allowed window. The API verifies the file before marking it ready. The configured storage provider still needs a staging check.
Service monitoring
The backend sends operational logs and metrics through OpenTelemetry. Operators can use Grafana to inspect service behavior. The hosted monitoring setup still needs verification.
105 API actions · 64 pathsCounted in the November 20 API contract. The file-upload merge reports 477 tests passed using disposable PostgreSQL, Redis and S3-compatible storage.
Integration pendingFrontend
The browser portal where youth leaders find a session, open a roster and record attendance.
What exists today
The existing Next.js portal has screens for youth sessions, students, groups, events and attendance. Its repository describes responsive navigation and browser checks with simulated API responses. Connecting the portal to v3 is the next delivery step.
Refresh how the portal talks to v3
Choose the API revision for staging, update the portal’s API client and refresh its example data. Recheck how the interface responds when a user’s access changes or a page needs to reload after a filter changes.
Prove the leader workflow
Sign in, see a dashboard limited to the leader’s access, pick an authorized session, open the roster, then mark and correct attendance. Verify empty lists, denied access, and retry behavior.
Connect the rest of the planned screens
The v3 design covers a people directory, event and session management, follow-up, account settings, file handling and administration. Available screens and actions depend on the role and the staging scope.
Check usability with real staging roles
Try the workflow on phones and desktop browsers, with keyboard navigation and clear loading, error and confirmation states. Use representative staging roles to verify what each leader can see and change.
First acceptance milestoneA representative youth leader completes the agreed attendance workflow against the v3 staging service.