Fixes #1218 - Document avatars behavior and remove MS avatar limitation#1230
Open
ralf401 wants to merge 8 commits into
Open
Fixes #1218 - Document avatars behavior and remove MS avatar limitation#1230ralf401 wants to merge 8 commits into
ralf401 wants to merge 8 commits into
Conversation
Replace the obsolete note that Zammad ignores user avatars from Microsoft sign-in. The note now describes the actual behavior: Zammad fetches the avatar from the user's Microsoft profile when available, falls back to the Zammad Image Service (e.g. Gravatar based on email) otherwise, keeps already saved avatars even if the image service is later disabled, and updates the user's avatar whenever a new one is fetched from any source.
The Microsoft login doc previously contained a detailed block on avatar sources, persistence, and update behavior. Move that information to a new central 'Avatars' sub-page under /manage/users/ that covers all avatar sources (OAuth login providers, the Zammad Image Service, manual upload, Clearbit integration, and the LDAP-not-supported caveat) so that future login docs do not have to repeat themselves. Slim the Microsoft login doc to a one-line pointer to the central page. Add a hint in the organizations doc that organization avatars are looked up by the Zammad Image Service based on domain. Expand the Image Service entry in settings/system/services.rst to clarify that the service covers both user avatars (via email) and organization avatars (via domain) and link to the central page.
Add a 'Changing avatars' section to the central avatar page that covers: - admins cannot change user or organization avatars from the admin panel (no UI for the image/image_source fields exists); - the only supported way for a user to change their own avatar is via their profile settings (top-right avatar menu, then Profile, then the Avatar section); - organization avatars have no manual upload path and are populated only by the Zammad Image Service based on domain; - warn that the 'View from user's perspective' action technically allows an admin to upload an avatar while in a switched session, but this is not a supported workflow and should not be used for that purpose.
- Drop the warning about the 'View from user's perspective' feature; the misuse pattern is not worth calling out explicitly in the docs. - Replace the legacy 'top-right corner' avatar-menu location with the current Vue 3 desktop UI location: bottom of the navigation sidebar. Matches user-documentation wording and the LeftSidebarFooterMenu component in app/frontend/apps/desktop. - Soften the 'in this order of preference' framing to 'whichever source last fetched an avatar for a user becomes the active one', which is what the code actually does (Avatar.add's set_default_items logic in app/models/avatar.rb). The four sources are independent triggers, not a strict preference list. - Drop the parenthetical legacy UI path '*Avatar > Profile*' from the Sources section so the upload path is described in one place only (the Changing avatars section, which uses the new UI wording). - Consolidate the Changing avatars section into one paragraph per topic (users, organizations), with a one-sentence lead.
ArtifactsProduced during runtime |
YetAnotherGerrit
requested changes
Jul 14, 2026
YetAnotherGerrit
requested changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.