- Shipped
- August 15, 2026 at 1:50 AM UTC
- Author
- Kamo
- Commit
- 4fe61d1
The member profile's legal-name card was self-only, so an admin who typed a name wrong on the create form could never correct it — MemberCreateForm asks for prefix/first/middle/last/suffix and nothing afterwards could change them. The card now renders for MANAGE_MEMBERS / MANAGE_MEMBER_SECURITY holders too. That makes the endpoint's gate load-bearing, and it did not have one: PUT /api/security/members/{id} checked only that the target sat in the caller's organization, so any colleague could rename any other. Name, preferred name and date of birth write to the USER account rather than the membership, so they are gated on MANAGE_MEMBERS / MANAGE_MEMBER_SECURITY (or god) whenever the target is not yourself. Member-level fields keep their previous behaviour.