Your account
HOL-D001Story implementation: In progress

Make my Backcountry profile my own

membership · Proposed launch phase 1

Start from Home

Review as Registered user

User story

As a registered member, I want to edit my own personal profile without repeating account setup so I can keep my information accurate.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Provide the same private Your profile editor for every registered account, including free/paid Members and people currently in Professional, organization or staff workspaces. Reach it through the shared Profile & settings navigation without changing the selected Home.
  • Use a regular form with Display name, optional Profile line, optional broad Home region and Profile image choices Initials/Ridge line/Field day/Winter camp. Save this section directly; no four-step setup or notification/privacy choice is required.
  • Preserve the exact existing custom region and intentional empty optional fields. Suggestions must not substitute Northern Vermont for Burlington, Vermont. Validate a blank display name clearly; do not insert generic fallback identity text.
  • Offer explicit Save profile and Cancel, show dirty state and safe leave confirmation, retain input on failed save and show success only after persistence. Reject stale same-field edits; do not overwrite unrelated preferences changed elsewhere.
  • Persist only changed permitted private fields. Preserve interests, notification choices, privacy/publication, owned activity, selected Home, paid entitlement, organization grants and Professional drafts/published names. Private edits do not silently publish or rewrite a public person profile.
  • Keep interests editable as their own Interests & preferences section under this existing story; saved eligible starting Home remains D092. The first increment builds Your profile only; further preference editing is a separate acceptance step.
  • Use existing approved image/initial choices in this slice. Actual file upload/storage/cropping remains an explicit future D001 acceptance decision, not a fabricated connected capability.

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. Local review: Sign in → Try a demo account → Alex Morgan → Free Member Home. Edit the same personal account; workspace selection and rights remain unchanged.

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. 02From the signed-in Home open account/workspace menu → Profile & settings → Your profile when delivered. Legacy /my-backcountry/edit must remain a working alias.

Feature checks start here

Your profile

Available in dev and connected staging for the named dummy accounts. Casey’s profile-line Save, refresh, exact restoration, Cancel and unsaved-change choices passed live staging checks. Name, exact home region and image choice remained unchanged. Full-story and remaining role/error acceptance stay In progress; this is not stakeholder approval.

  1. 03From this role’s Home open account/workspace menu → Profile & settings → Your profile when delivered. Current legacy Edit profile links must lead to the same editor; implementation is underway.
  2. 04On a dedicated fictional account edit Display name and Profile line, retain a custom region such as Burlington, Vermont, and select one approved image or Initials. Select Save profile directly; notification/privacy steps are not required.
  3. 05Reload and reopen Your profile; compare exact saved values with the private account menu and Member profile. Check an intentional empty Profile line/Home region and a rejected blank Display name.
  4. 06Change a value then Cancel or navigate away; confirm the saved profile remains unchanged. A failed save retains input; a stale same-field save gets a clear conflict/reload choice.
  5. 07Compare unrelated interests, notification/privacy settings, saved work, selected Home, Professional/public name, org grants and membership before/after; they must not change. Review separate interests editing only when delivered.
  6. 08Use another account/read-only security checks to verify owner isolation; avoid resetting or publishing someone else’s profile for review.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Extend the existing owner profile/preferences model with a bounded read/patch contract for display name, profile line, broad region and existing image-choice enum only. Require the actual verified owner; reject unknown/private authority fields and cross-account writes.
  • Apply only supplied changed fields, compare expected original values/version for same-field conflicts and preserve concurrent unrelated preference updates. Do not perform whole-profile defaults/repair or replace the whole preferences object during editing.
  • Preserve exact valid custom region and optional empty values. Validate display name, lengths/types and allowed image choices. A real user's private edit is not a seed repair and never derives their name from email.
  • Keep private edits separate from Professional drafts/public publication and org records. No automatic public name/photo overwrite, grant, entitlement, preferred Home or activity change; explicit publication remains D090.
  • No new file-upload/Storage system, card/address/billing tables, hosted migration or provider credentials in this first slice. Preserve earlier guard-only seed repair and repeat-startup protection.

How to verify in dev

  1. Verify anonymous/other-owner/unverified denial, field allowlist, invalid/blank name, custom/empty region, optional clearing and allowed image selection/removal-to-initials.
  2. Verify save/reload/same-account return, stale same-field conflicts and concurrent disjoint updates; confirm unrelated interests/notifications/privacy/activity/publication/preference/grants/entitlement remain byte-for-byte unchanged where applicable.
  3. Browser check free and paid editor equivalence plus personal editing from Professional/org/staff contexts without saved Home mutation. Preserve12 dummy scenarios and staff-operation MFA; no shared-user global sign-out or account reset for tests.

Before this can work

  • Use existing fictional accounts or a dedicated test account; preserve its permissions, selected Home and published professional identity.
  • First slice: private navigation/editor/local persistence only. Existing image choices suffice; no file upload/provider, payment, outbound delivery or publication.

Connected stories