@claude - Let's update the Mattermost Product Documentation to reflect the System Admin's System Console user-management experience captured via Engineering PR mattermost/mattermost#33550
Scope & constraints
- Review the PR and base all proposed doc changes only on PR-visible evidence.
- Focus only on the admin-visible capability change: System Admins can view and update user AuthData and username in the System Console user detail workflow.
- Keep the update minimal and capability-focused. Do not document internal code structure, component refactors, test-only changes, or implementation mechanics.
- Mention validation / confirmation behavior only if it helps explain the admin workflow and is clearly supported by PR evidence.
- DO NOT modify: changelogs, important upgrade notes, version archive, removed/deprecated features, unsupported legacy releases.
Required doc touchpoints:
Identify the existing admin docs page(s) covering:
- System Console user management
- user detail / user administration workflows
- any admin docs that describe editing user identity or authentication-related fields
- If no existing page directly covers this workflow, identify the closest likely admin page and propose the smallest possible addition there.
Output requirements (what to return: proposed text, page list, before/after, etc.)
- whether a docs update is needed
- the exact page(s) to update
- a short rationale for each page
- proposed before/after text or insertion text
- a note showing which sentence is supported by which PR evidence
- Keep the proposed doc change concise; prefer a small edit to an existing admin page over creating a new section.
@claude - Let's update the Mattermost Product Documentation to reflect the System Admin's System Console user-management experience captured via Engineering PR mattermost/mattermost#33550
Scope & constraints
Required doc touchpoints:
Identify the existing admin docs page(s) covering:
Output requirements (what to return: proposed text, page list, before/after, etc.)