Skip to content
Sudomimus

Avatar review lifecycle

View as Markdown

Uploaded avatars are user-controlled media, so Sudomimus separates account preview from application delivery.

The user may see a newly uploaded image on their own account surface while it is waiting for review. Applications continue to receive the current approved avatar, or a generated fallback, until the upload is approved.

States

Section titled “States”
State What the user sees What applications receive
PENDING The account surface can show the uploaded preview and mark it as waiting for review. The previous approved avatar, or the generated fallback.
APPROVED The upload becomes the account avatar. Future /userinfo responses can include the approved avatar when claim policy and consent allow it.
REJECTED The upload should be shown as rejected or replaced by the fallback/current avatar. No change. Applications keep receiving the previous approved avatar or fallback.

Application delivery

Section titled “Application delivery”

Applications do not fetch account-avatar review state directly. They see avatar data only through the claim system:

  • Session and OIDC /userinfo can include picture and picture_animated.
  • Avatar fields appear only when the application’s claim policy and the user’s grant allow them.

When an upload is approved, applications see the new avatar in the next /userinfo response that includes the avatar claim. Treat those URLs as replaceable profile fields, not permanent identifiers.

UI guidance

Section titled “UI guidance”
  • Show pending uploads only in account-management UI, not as if they were already published to applications.
  • Keep a fallback ready for rejected uploads.
  • Do not promise that an uploaded avatar is visible to applications until it is approved.
  • If your product supports motion, use the animated URL; otherwise render the static URL.
Section titled “Related”