# I  can  deactivate User  but  cant  reactivate him

**URL:** <https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664>\
**Category:** API and Webhooks\
**Created:** [July 27, 2017, 12:28pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664 "2017-07-27T12:28:28Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lilia\_Schmidt](https://avatars.discourse-cdn.com/v4/letter/l/4bbf92/32.png) [@Lilia\_Schmidt](https://devforum.zoom.us/u/Lilia_Schmidt)\
**Post date:** [July 27, 2017, 12:28pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664/1 "2017-07-27T12:28:28Z")

</div>

Hello,

how&nbsp; is&nbsp; it&nbsp; possible, that in&nbsp; Users Rest&nbsp; Api i&nbsp; can&nbsp; deactivate&nbsp; User,&nbsp; but&nbsp; cant Activate&nbsp; him&nbsp; again

[https://zoom.github.io/api/#user](https://zoom.github.io/api/#user)

What&nbsp; should&nbsp; i&nbsp; do, if i&nbsp; need to&nbsp; activate&nbsp; Users&nbsp; again?&nbsp; Should&nbsp; i&nbsp; create&nbsp; another&nbsp; Users?

&nbsp;For&nbsp; example&nbsp; i’ll&nbsp; deactivate&nbsp; 100 Users&nbsp; and&nbsp; then&nbsp; i’ll&nbsp; need&nbsp; to&nbsp; activate&nbsp; them&nbsp; again.

---

<div class="post-metadata">

**Author:** ![Joshua\_Woodward1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua_woodward1/32/1480_2.png) [@Joshua\_Woodward1](https://devforum.zoom.us/u/Joshua_Woodward1)\
**Post date:** [July 27, 2017, 5:15pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664/2 "2017-07-27T17:15:59Z")

</div>

Hi Lilia,

&nbsp;

We have a fix for this coming very soon, please stay tuned.

---

<div class="post-metadata">

**Author:** ![Lilia\_Schmidt](https://avatars.discourse-cdn.com/v4/letter/l/4bbf92/32.png) [@Lilia\_Schmidt](https://devforum.zoom.us/u/Lilia_Schmidt)\
**Post date:** [July 27, 2017, 5:24pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664/3 "2017-07-27T17:24:08Z")

</div>

Thank you Joshua,

it&nbsp; will&nbsp; save us!&nbsp; Do you&nbsp; know&nbsp; the&nbsp; Exact&nbsp; Date&nbsp; please ?

we must&nbsp; launch&nbsp; our&nbsp; integration solution 1 of September, is&nbsp; there&nbsp; any&nbsp; option&nbsp; that you&nbsp; release it&nbsp; August ?🙂

&nbsp;

Or&nbsp; could&nbsp; we became&nbsp; a&nbsp; betta&nbsp; testers tor only one&nbsp; this&nbsp; Api?

---

<div class="post-metadata">

**Author:** ![Joshua\_Woodward1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua_woodward1/32/1480_2.png) [@Joshua\_Woodward1](https://devforum.zoom.us/u/Joshua_Woodward1)\
**Post date:** [July 27, 2017, 5:29pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664/4 "2017-07-27T17:29:09Z")

</div>

It should be released in early August.

&nbsp;

Just out of curiosity, what is the use case where you are deactivating 100 users?

---

<div class="post-metadata">

**Author:** ![Lilia\_Schmidt](https://avatars.discourse-cdn.com/v4/letter/l/4bbf92/32.png) [@Lilia\_Schmidt](https://devforum.zoom.us/u/Lilia_Schmidt)\
**Post date:** [July 27, 2017, 8:04pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664/5 "2017-07-27T20:04:33Z")

</div>

It’s simple, try to&nbsp; imagine:

we&nbsp; have a project management software, zoom meetings options&nbsp; will&nbsp; be&nbsp; implmented to Our Calendar.

Every customer for us == one sotware&nbsp; instance

Every instance (Customer)&nbsp; can&nbsp; have&nbsp; from 10&nbsp; up to 1000 User who use our&nbsp; system&nbsp; for&nbsp; collaboration

If some&nbsp; customer stop paying to us, his Instance&nbsp; should be&nbsp; Downgraded, and he&nbsp; shouldnt&nbsp; be able to Use Video Meetings, in this case we&nbsp; want to deactivate&nbsp; his&nbsp; users,&nbsp; and when he renew&nbsp; payments, we&nbsp; need to reactivate&nbsp; them&nbsp; again.

Since&nbsp; we&nbsp; have&nbsp; about&nbsp; 1 500&nbsp; Customers, and&nbsp; all&nbsp; of&nbsp; them have&nbsp; from&nbsp; 10 to 1000 Users, processing such&nbsp; oprations,&nbsp; if&nbsp; we&nbsp; can deactivate&nbsp; users users via&nbsp; rest api&nbsp; automatically, but&nbsp; cant&nbsp; activate it again,&nbsp; only manually from&nbsp; Administration, looks&nbsp; really sad&nbsp; 🙂

&nbsp;

That’s&nbsp; why we are waitng for this Api so much&nbsp; 🙂

&nbsp;

---

<div class="post-metadata">

**Author:** ![Joshua\_Woodward1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua_woodward1/32/1480_2.png) [@Joshua\_Woodward1](https://devforum.zoom.us/u/Joshua_Woodward1)\
**Post date:** [July 27, 2017, 8:14pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664/6 "2017-07-27T20:14:11Z")

</div>

Are you creating all these users under your main account, or are you creating a sub account per customer (with that customer’s users under that sub account)

If the later you could mange the sub accounts plan, affecting all users, without having to deactivate/reactive on a user basis.

&nbsp;

Not sure 100% of your implementation, but feel free to shoot me an email [joshua.woodward@zoom.us](mailto:joshua.woodward@zoom.us) and maybe we could dive deeper.

---

<div class="post-metadata">

**Author:** ![Joshua\_Woodward1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua_woodward1/32/1480_2.png) [@Joshua\_Woodward1](https://devforum.zoom.us/u/Joshua_Woodward1)\
**Post date:** [August 28, 2017, 9:46pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664/7 "2017-08-28T21:46:56Z")

</div>

This is now available&nbsp;[https://zoom.github.io/api/#activate-a-user](https://zoom.github.io/api/#activate-a-user)

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 5:16pm UTC](https://devforum.zoom.us/t/i-can-deactivate-user-but-cant-reactivate-him/664/8 "2020-08-21T17:16:59Z")

</div>

Closed on August 21, 2020, 5:16pm UTC


