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.
Desculpe por reativar este tópico antigo, mas o comportamento do Discourse está realmente causando problemas no momento.
Se um usuário ativa suas contas em nossa plataforma (o Discourse é apenas uma das muitas plataformas), criamos automaticamente um usuário do Discord via API. Precisamos fazer isso para atribuir os grupos corretos. Se o usuário alterar seu e-mail antes de fazer login no Discourse via Discourse SSO pela primeira vez, ele criará uma nova conta (<username>1) e teremos que mesclar manualmente as 2 contas.
Permitir que a API altere o e-mail ajudaria a reduzir muito o trabalho manual. E acho que os administradores também deveriam ter permissão, pois normalmente sabem o que estão fazendo.
Gostaria de proibir os usuários de alterarem seus endereços de e-mail, mas não os administradores e a API.
Uma outra solução fácil para nós seria se o Discourse SSO ou SAML pudessem ser configurados para simplesmente fazer login na conta com o mesmo nome SEM fazer verificações baseadas em e-mail. Mas, infelizmente, o Discourse sempre quer ser mais esperto do que qualquer um que o utiliza
