Your account
HOL-D105Story implementation: Planned

Choose which updates I receive

notifications · Proposed launch phase 1

Start from Home

Review as Registered user · Full workflow planned

User story

As a registered member, I want to change my optional update preferences in one place so I receive the categories of updates I choose.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Provide a dedicated Notifications settings page with separate editorial, place, community and event category choices; save these directly without changing profile identity or privacy.
  • Load current owner choices, show what is saved, preserve unrelated settings, and support cancel, failed save/retry, reload and stale-edit handling. Defaults must not silently opt anyone into delivery.
  • Distinguish category preferences from live delivery channels and from mandatory security/account messages. Existing in-app examples remain visibly simulated until their own backend is connected.
  • Professional/org/staff context does not create marketing consent, override Member content eligibility or allow editing anyone else’s preferences.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin on this account’s permitted Home. For a local review use Sign in → Try a demo account → Alex Morgan → Free Member Home. Settings belong to this same personal account; keep Professional/organization/staff authority separate.

Navigation from sign-in

  1. 01Open the fictional Registered user account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Begin at this role’s Home, open its account/workspace menu, then Profile & settings when that navigation is delivered. Follow the section named in the checks; stop if a planned destination is unavailable.

Feature checks start here

Choose which updates I receive · Full workflow planned

Planned follow-up. Requirements are recorded; the dedicated settings page and backend workflow are not implemented. Current navigation/editor work does not implement this outcome.

  1. 03From the role Home open account menu → Profile & settings → Notifications when the dedicated page is delivered; this new page is currently planned.
  2. 04On a dedicated test account change one category and save. Reload and compare that choice; check cancel/retry without changing name, interests or privacy.
  3. 05Review any simulated example separately; a saved preference alone is not evidence that email/push was sent.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Use owner-scoped category preferences already represented in private profiles. Define a bounded patch/version contract and do not replace the entire preference object.
  • Keep security/account notices distinct from optional categories. Do not connect email/push/SMS, create subscriber consent or manufacture notification history in this story.
  • Future real delivery needs channel-specific consent and read/unread/event persistence under separate notification work. No new permission is conferred by an opted-in category.

How to verify when implementation is approved

  1. Test owner/other-account/unverified denial, disjoint-update preservation, repeated save and stale conflict.
  2. Verify opt-out controls future optional examples without affecting required account/security communication policy.

Before this can work

  • Use an existing fictional account; keep its current role/entitlement and selected Home. No profile/preference reset is required to review requirements.
  • Dev only. No real card/address/recipient data, provider setup, outbound delivery or publication is part of this review.

Connected stories