# How to Deactivate the Discourse Activation Email

**URL:** <https://meta.discourse.org/t/how-to-deactivate-the-discourse-activation-email/85379>\
**Category:** WordPress\
**Created:** [15.Апрель.2018 16:11:34 UTC](https://meta.discourse.org/t/how-to-deactivate-the-discourse-activation-email/85379 "2018-04-15T16:11:34Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [08.Декабрь.2018 17:29:09 UTC](https://meta.discourse.org/t/how-to-deactivate-the-discourse-activation-email/85379/11 "2018-12-08T17:29:09Z")

</div>

> [@RickU](#):
>
> When I disable 2FA for the admins then they can sign in to back-end no problem.  
> The 2FA is being implemented through iThemes security.

Having extra security for admins could be a good idea. There have been issues reported previously about conflicts between the iThemes Security plugin and [WP DIscourse](https://github.com/discourse/wp-discourse) SSO. I’d like to try it out to see if it can be made to work. I’ll let you know what I find.

> [@RickU](#):
>
> I am doing this is because I have SSO activated through Wordpress and Wordpress is doing the email verification in addition to that. In addition, I also disabled public registrations meaning that the only way to create an account is through Wordpress.

On the Discourse end, all you need to do is select the ‘enable sso’ Site Setting. When that setting is enabled, Discourse only allows accounts to be created through SSO.

---

_[View the full topic](https://meta.discourse.org/t/how-to-deactivate-the-discourse-activation-email/85379)._
