Registration Portal Requirements

This module contains the business and functional requirements for the Registration Portal, a self-service web application that enables users to register for memberships and events.

1. Overview

The Registration Portal is part of the Event and Membership Administration system. It provides streamlined, process-driven workflows for onboarding Members and Event Participants.

Key Capabilities:

  • LinkedPerson Management - Manage groups of related people (family, friends, team) for registration

  • Membership Registration - Process-driven workflow for membership applications

  • Event Participant Registration - Comprehensive participant information capture for events

2. Phase 2 Enhancements

Phase 2 introduces several new capabilities:

  • Identity Selection - OIDC authentication option for Event Registration

  • Manual Payment - QR code handoff to staff at registration desk

  • Event Cancellation - Cancel registrations with refund rules

  • Communication Preferences - Capture preferred notification channels

See Functional Overview for detailed capability descriptions.

3. Requirements Categories

3.1. Functional Requirements

3.2. User Interface Requirements

3.3. Security Requirements

  • Security Requirements - Token exchange, automatic refresh, session security, and data protection requirements

4. Azure DevOps Features

Requirements are organized to support two Azure DevOps Features:

Feature Priority Scope

Membership Registration

High

Enhancements to existing workflow: Manual Payment, Communication Preferences

Event Registration

Medium

New feature: Full registration flow, Identity Selection, Cancellation with refunds

Implementation Order:

  1. Membership Registration improvements (existing customer, higher priority)

  2. Event Registration (new feature, after Membership improvements)

5. Source Documentation

This requirements documentation is derived from:

  • Phase 2 Design: Phase 2 Registration Design

  • Requirements Guide: ../../../doc-standard/docs/modules/ROOT/pages/requirements-guide.adoc

  • Existing implementation in the Registration Portal codebase

  • Stakeholder requirements from development team

6. Document Status

Status: Phase 2 Requirements Defined (December 2024)

  • Functional Overview created

  • Use Cases updated with Phase 2 scenarios and acceptance criteria

  • Screen Designs specified for all customer-facing screens

  • Ready for Azure DevOps work item creation