# Establish current ownership of email?

**URL:** https://meta.discourse.org/t/establish-current-ownership-of-email/113755
**Category:** Support
**Created:** [8 april 2019 om 14:01 UTC](https://meta.discourse.org/t/establish-current-ownership-of-email/113755 "2019-04-08T14:01:27Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)
#### Post date: [8 april 2019 om 14:01 UTC](https://meta.discourse.org/t/establish-current-ownership-of-email/113755/1 "2019-04-08T14:01:27Z")

</div>

Does anyone have an idea how we can verify that users are still in possession of their original email address?

Our usecase is that we allow access based on their employer’s domain. If people leave their employer, they will still have access to our Discourse install. This could be a compliancy issue.

Anyone have done something like this, in a user friendly fashion? The only option I have is to suspend all users, forcing a re-activation, but that seems a bit hostile.

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [8 april 2019 om 14:13 UTC](https://meta.discourse.org/t/establish-current-ownership-of-email/113755/2 "2019-04-08T14:13:54Z")

</div>

> [@Bas](#):
>
> verify that users are still in possession of their original email address

You can use the “deactivate” button in the admin panel to force a specific user to re-validate their email address.

If you want to automate the process we have this plugin:

[https://github.com/discourse/discourse-auto-deactivate](https://github.com/discourse/discourse-auto-deactivate)

But it only deactivates ‘inactive’ users. If a user leaves the company it won’t deactivate them immediately.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [8 april 2019 om 14:51 UTC](https://meta.discourse.org/t/establish-current-ownership-of-email/113755/3 "2019-04-08T14:51:20Z")

</div>

How many employers are there? Could they let you know somehow?

---

<div class="post-metadata">

### Author: ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)
#### Post date: [9 april 2019 om 09:54 UTC](https://meta.discourse.org/t/establish-current-ownership-of-email/113755/4 "2019-04-09T09:54:08Z")

</div>

> [@david](#):
>
> You can use the “deactivate” button in the admin panel to force a specific user to re-validate their email address.

Yeah, that’s the route I was going to take. Feels a bit hostile, but might be needed once a year or so.

> [@david](#):
>
> If you want to automate the process we have this plugin:

Fantastic! We can modify that one re-authenticate all

> [@pfaffman](#):
>
> How many employers are there? Could they let you know somehow?

More than 100, it’s not practical unfortunately.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [26 juni 2022 om 11:15 UTC](https://meta.discourse.org/t/establish-current-ownership-of-email/113755/5 "2022-06-26T11:15:39Z")

</div>



---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [26 juni 2022 om 11:57 UTC](https://meta.discourse.org/t/establish-current-ownership-of-email/113755/6 "2022-06-26T11:57:06Z")

</div>


