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.
오래된 스레드를 다시 꺼내게 되어 죄송합니다. 현재 Discourse의 동작 방식이 실제로 문제를 일으키고 있습니다.
사용자가 우리 플랫폼(여러 플랫폼 중 Discourse는 하나일 뿐입니다)에서 계정을 활성화하면, API를 통해 자동으로 Discord 사용자를 생성합니다. 이는 올바른 그룹을 할당하기 위해 필요합니다. 사용자가 Discourse SSO를 통해 Discourse에 처음 로그인하기 전에 이메일 주소를 변경하면, 새로운 계정(<username>1)이 생성되고, 우리는 두 계정을 수동으로 병합해야 합니다.
API를 통해 이메일을 변경할 수 있도록 허용하면 수작업이 많이 줄어들 것입니다. 또한, 관리자도 일반적으로 자신이 하는 일을 잘 알고 있으므로 이 권한을 부여하는 것이 적절하다고 생각합니다.
일반 사용자의 이메일 주소 변경은 비활성화하되, 관리자와 API에는 변경을 허용하고 싶습니다.
