允许管理员轻松更改电子邮件地址

Current setup:

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. :sunny:

###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?

extra brownie points from this customer if @techAPJ could allow the name to be edited while he’s there.

Please?

14 个赞

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.

2 个赞

I guess API considerations, such as this post by @SnipersCode, would come in to play as well.

3 个赞

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.

4 个赞

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.

1 个赞

您好,

抱歉打扰这个旧帖子,但 Discourse 的行为目前确实造成了问题。

如果用户在我们的平台(Discourse 只是众多平台之一)上激活他们的账户,我们会通过 API 自动创建一个 Discord 用户。我们需要这样做才能分配正确的组。如果用户在通过 Discourse SSO 首次登录 Discourse 之前更改其电子邮件,他将创建一个新账户(\u003cusername\u003e1),我们必须手动合并这两个账户。

允许 API 更改电子邮件将有助于减少大量手动工作。而且我认为管理员也应该被允许,因为他们通常知道自己在做什么。

我想禁止用户更改他们的电子邮件地址,但允许管理员和 API 进行更改。

1 个赞

配置您的 sso,以便在登录时分配组。

1 个赞

抱歉,我们的设置无法实现这一点。

(至少目前不行)

对我们来说,另一个简单的解决方案是,如果 Discourse SSO 或 SAML 可以设置为仅登录同名账户,而无需进行基于电子邮件的检查。但不幸的是,Discourse 总是想比任何使用者都更聪明 :frowning:

好吧,我想抱怨的不是我一个人。终于有可能了!

非常感谢! :slight_smile:

2 个赞

6 个帖子被拆分到一个新主题:更改电子邮件地址作为管理员不起作用