The Profile block ([us_family]) is headed "Your profile", but the one person on it you cannot change is yourself. It lists the students you book for and lets you add, edit and remove them — while your own name, your birth year, and whether you take lessons yourself are fixed at whatever signup recorded.
That leaves two things needing a studio admin:
A wrong or changed name. A typo at signup, or a name that has since changed, has to be fixed by someone with WordPress admin.
A wrong answer to "Who are you registering?" That radio sets us_guardian_only, which decides whether you are offered as a student when booking. Someone who picked "on behalf of one or more students" and later took up lessons themselves — or who simply picked the wrong one — cannot correct it. GuardianService::bookableStudents() already carries a comment saying they can "put the account right from the profile page", and docs/features/parent-guardian-accounts.md repeats it; neither is true today.
Proposed
A Your details section at the top of the profile page, saved through the same nonce-checked template_redirect post/redirect/get path the child rows use:
Your name (required) — display_name and nickname together, so UserName does not fall back to the email address.
I take lessons myself — the positive of us_guardian_only.
Your birth year — us_birth_year, held to the same normaliseBirthYear() rule as every student.
Your email is shown but not editable: it is the account's user_login as well as its address, so changing it stays a studio-side job.
Out of scope
Re-asking the account-scope registration questions here. The child rows do not offer them on edit either, so doing it only for the account holder would be the odd one out.
The **Profile** block (`[us_family]`) is headed "Your profile", but the one person on it you cannot change is yourself. It lists the students you book for and lets you add, edit and remove them — while your own name, your birth year, and whether you take lessons yourself are fixed at whatever signup recorded.
That leaves two things needing a studio admin:
- **A wrong or changed name.** A typo at signup, or a name that has since changed, has to be fixed by someone with WordPress admin.
- **A wrong answer to "Who are you registering?"** That radio sets `us_guardian_only`, which decides whether you are offered as a student when booking. Someone who picked "on behalf of one or more students" and later took up lessons themselves — or who simply picked the wrong one — cannot correct it. `GuardianService::bookableStudents()` already carries a comment saying they can "put the account right from the profile page", and `docs/features/parent-guardian-accounts.md` repeats it; neither is true today.
## Proposed
A **Your details** section at the top of the profile page, saved through the same nonce-checked `template_redirect` post/redirect/get path the child rows use:
- **Your name** (required) — `display_name` and `nickname` together, so `UserName` does not fall back to the email address.
- **I take lessons myself** — the positive of `us_guardian_only`.
- **Your birth year** — `us_birth_year`, held to the same `normaliseBirthYear()` rule as every student.
Your email is shown but not editable: it is the account's `user_login` as well as its address, so changing it stays a studio-side job.
## Out of scope
Re-asking the account-scope registration questions here. The child rows do not offer them on edit either, so doing it only for the account holder would be the odd one out.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Profile block (
[us_family]) is headed "Your profile", but the one person on it you cannot change is yourself. It lists the students you book for and lets you add, edit and remove them — while your own name, your birth year, and whether you take lessons yourself are fixed at whatever signup recorded.That leaves two things needing a studio admin:
us_guardian_only, which decides whether you are offered as a student when booking. Someone who picked "on behalf of one or more students" and later took up lessons themselves — or who simply picked the wrong one — cannot correct it.GuardianService::bookableStudents()already carries a comment saying they can "put the account right from the profile page", anddocs/features/parent-guardian-accounts.mdrepeats it; neither is true today.Proposed
A Your details section at the top of the profile page, saved through the same nonce-checked
template_redirectpost/redirect/get path the child rows use:display_nameandnicknametogether, soUserNamedoes not fall back to the email address.us_guardian_only.us_birth_year, held to the samenormaliseBirthYear()rule as every student.Your email is shown but not editable: it is the account's
user_loginas well as its address, so changing it stays a studio-side job.Out of scope
Re-asking the account-scope registration questions here. The child rows do not offer them on edit either, so doing it only for the account holder would be the odd one out.