是否可以通过 API 更改用户的电子邮件地址，同时不触发确认邮件？
我们的用户实际上是协会的成员。当用户直接向工作人员提交电子邮件地址变更请求时，工作人员会在我们的 ERP 系统中更新联系人的记录。随后，工作人员需要以该用户的身份登录我们的 Discourse 系统并提交电子邮件地址变更。
工作人员抱怨称，确认邮件会让用户感到困惑、未被查看或被忽略，因此电子邮件地址变更从未完成。
我希望借此一举两得：
我们不希望使用 SSO 覆盖电子邮件的功能，因为我们有少数用户希望 Discourse 的通知与协会的主要通知不同。
I would say this is a self inflicted wound at that point?
Hey, Paul. I’m still happy to help on this, but Jeff makes a point. Just how will you know whether someone wants a different address? You’ll just change it via the API on ERP but let them change it in Discourse if they want to?
The idea would be, if the request is made to change the email address and the old address matches the ERP system AND Discourse, then change it in both. Additionally, they may have an online or paper form that asks if the email change should include Discourse.
Another salient point here is: nearly all the association members use Discourse as a mailing list (mailing list mode) and never visit the Discourse instance site. So, having to go to the site to confirm the email address change adds a layer of confusion for them.
I realize this is not a normal use case for mainstream Discourse installations, but I have been asked to make it happen, so I’m barking up the tree.
Worst case it’ll take a plug in. If I can’t do it, I’d fit a guy. If you want to give it a shot, search here for ‘reverse engineering’.
Discourse 现在支持每个用户多个电子邮件地址，这是否解决了您最初的问题？