@claude - Let's update the Mattermost Product Documentation to note that Google SSO users do not automatically sync username or email changes from the identity provider captured via Engineering PR mattermost/mattermost#34475
Scope & constraints
- Review PR #34475 as the source of truth and use only PR-verifiable claims.
- Keep the update minimal and focused on the visible product clarification, not implementation details.
- Do not modify: changelogs, important upgrade notes, version archive, removed/deprecated features, unsupported legacy releases.
- Do not describe internal React/component changes or i18n mechanics.
- Do not imply new sync functionality was added; the PR clarifies an existing limitation.
Required doc touchpoints
Identify likely pages covering:
- Google SSO / Google Workspace authentication behavior
- Account Settings or Sign-in Method behavior for SSO users
- Any existing end-user or admin auth docs that could incorrectly imply profile field sync
If no existing product doc page cleanly fits, recommend the smallest viable clarification on the closest auth page rather than creating broad new content.
Output requirements
Return:
- whether a docs update is truly needed
- the most likely doc page/section to update
- the exact proposed text
- a brief why-this-page rationale
- before/after snippet
- confirmation that no non-editable docs were touched
Keep the proposed content tightly aligned to PR evidence:
- visible note appears in Account Settings → Security → Sign-in Method
- applies to Google SSO
- clarifies lack of automatic username/email sync from Google Workspace to Mattermost
Do not add workaround steps unless they are explicitly present in the target docs or separately validated by maintainers; the PR summary mentions a workaround path, but confirm whether product docs should include it before adding it.
@claude - Let's update the Mattermost Product Documentation to note that Google SSO users do not automatically sync username or email changes from the identity provider captured via Engineering PR mattermost/mattermost#34475
Scope & constraints
Required doc touchpoints
Identify likely pages covering:
If no existing product doc page cleanly fits, recommend the smallest viable clarification on the closest auth page rather than creating broad new content.
Output requirements
Return:
Keep the proposed content tightly aligned to PR evidence:
Do not add workaround steps unless they are explicitly present in the target docs or separately validated by maintainers; the PR summary mentions a workaround path, but confirm whether product docs should include it before adding it.