Site is locked down for members to be invited or request access.
We don’t want people changing their own email address, so the related email change site-setting is disabled. Of course, sometimes an admin must.
###Expectation:
go to the user’s admin page, see the email, and edit it, potentially have that pending confirmation of the new email.
###Actual
visit the admin page
click a button to see what it is.
there’s no way to edit it
Click Show Public Profile,
realize you have to click Preferences too.
No way to edit the email address… grrr
Go back to admin
disable the site setting
go back to publich profile/preferences
edit
go back to admin
disable the site setting.
As an admin, can we please just edit a user’s address at all times, from the Admin page?
Yeah, we are fine with allowing email/name/username editing on admin page. We must account for the sso override stuff though that disables editing here.
Of course, there are a couple of things that should be added related to this.
We should log all the name/email/username changes and have that visible somewhere
If an admin changes a users email, its probably sane to allow them to send an email right away to that user explaining that the email changed, doing this (optionally) automatically would be good.
As an admin, I can change an email now it just takes too many steps.
Addressing either (or both) of these two needs would help a lot"
Allowing an admin to change a user’s email from its Admin view (not only the public profile)
Allowing the change even if the site setting is disabled.
As for SSO, presumably the source of authentication already knows about the new email… the goal of the change in discourse would be to prevent an undesired second account from being created on the user’s next visit.
Currently this happens… we need to click an email confirmation link.
Maybe that would have to change when SSO is enabled, however I don’t think bringing the control from the user-side preferences to the admin side preferences changes the current SSO workflow.
désolé de déterrer ce vieux fil de discussion, mais le comportement de Discourse cause vraiment des problèmes en ce moment.
Si un utilisateur active ses comptes sur notre plateforme (Discourse n’est qu’une plateforme parmi d’autres), nous créons automatiquement un utilisateur Discord via l’API. Nous devons le faire afin d’attribuer les bons groupes. Si l’utilisateur change son e-mail avant de se connecter pour la première fois à Discourse via Discourse SSO, il créera un nouveau compte (<username>1) et nous devrons fusionner manuellement les 2 comptes.
Permettre à l’API de changer l’e-mail aiderait à réduire beaucoup de travail manuel. Et je suppose que les administrateurs devraient également être autorisés car ils savent normalement ce qu’ils font.
J’aimerais interdire aux utilisateurs de changer leurs adresses e-mail, mais pas aux administrateurs et à l’API.
Une autre solution facile pour nous serait si Discourse SSO ou SAML pouvaient être configurés pour simplement connecter le compte du même nom SANS effectuer de vérifications basées sur l’e-mail. Mais malheureusement, Discourse veut toujours être plus intelligent que quiconque l’utilise
