# Deactivate user in Ignition

**URL:** <https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876>\
**Category:** Ignition\
**Created:** [March 6, 2024, 8:09am UTC](https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876 "2024-03-06T08:09:28Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [March 6, 2024, 8:09am UTC](https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876/1 "2024-03-06T08:09:29Z")

</div>

Hi  
Is it possible to set an Ignition user in a de-active state, so he can't access the system until Admin gives him again permission?  
I can't any system function or config option for that.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 6, 2024, 8:23am UTC](https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876/2 "2024-03-06T08:23:07Z")

</div>

Just a thought:

- Create a "Never" schedule.
- Switch the user to the Never schedule using [system.user.editUser | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-user/system-user-editUser).

The problem now is that Admin needs to switch the user back to the right schedule but the record is gone - unless you record the "from" and "too" somewhere.

---

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [March 6, 2024, 8:29am UTC](https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876/3 "2024-03-06T08:29:31Z")

</div>

It seems it doesn't work with the Perspective Idp system.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 6, 2024, 3:01pm UTC](https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876/4 "2024-03-06T15:01:10Z")

</div>

IdPs are (deliberately) a bit of a black box. It's a different model than user sources, fundamentally.

This would have to be _possible_ in Ignition's IdP (I have no idea whether this is a general concept that is supported by all IdPs in the first place), to be exposed via some scripting approach.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 6, 2024, 3:06pm UTC](https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876/5 "2024-03-06T15:06:25Z")

</div>

Maybe a really bad hack, but could you script a change to their username and not tell them? Add a random string of eight characters. When they pay their subscription to your wonderful application the administrator just has to remove the eight characters from the end. (Make sure that space isn't an allowed add-on or it could get messy.)

---

<div class="post-metadata">

**Author:** ![bryan.fletcher](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bryan.fletcher/32/8921_2.png) [@bryan.fletcher](https://forum.inductiveautomation.com/u/bryan.fletcher)\
**Post date:** [January 20, 2026, 7:44pm UTC](https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876/6 "2026-01-20T19:44:27Z")

</div>

Here’s a possible hack/solution…  
As the admin, set user to the above suggested “never” schedule to clearly identify ~disabled~ users… but the real solution is the admin account changes the password in the background…  
then when admin does re-instate user to non-never schedule then restore some default password.

---

<div class="post-metadata">

**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\
**Post date:** [January 20, 2026, 9:14pm UTC](https://forum.inductiveautomation.com/t/deactivate-user-in-ignition/86876/7 "2026-01-20T21:14:34Z")

</div>

Add a "Active" role and require it for basically everything at the project level? Then just add it to all users, and remove it from your InActive users...
