- Home
- Blog
- EDGEBIC How-To
- How to Deactivate a User in EDGEBIC
To deactivate a user in EDGEBIC by User Solutions, open Settings, the Security tab, and the Users sub-tab, select the person's row, and click Activate / Deactivate. Sign-in for that account is refused from that moment, whatever password is typed, while the account, its roles, and every audit entry it produced stay intact.
Deactivation is the right move when someone leaves, changes department, or goes on extended leave. Deletion is not, and the difference is worth understanding before you click. For the wider account structure, see how to set up users and roles.
Before You Start
- You are signed in as an administrator or with a role that includes the security permissions. The Security tab is hidden otherwise.
- You know which account belongs to the person. Usernames are not case-sensitive at sign-in, so check the full name and email columns rather than guessing from a username.
- You have decided whether anything the person owns needs handing over first. Work in EDGEBIC belongs to jobs and schedules, not to users, so there is usually nothing to reassign, but a half-built quote or an unsaved plan on their machine is worth closing out first.
Deactivating the Account
- Open the Settings tab, then the 🔒 Security tab, then the Users sub-tab.
- Find the person's row. The grid shows Username, Full name, Email, Roles, Active, Locked, and Last login.
- Select the row.
- Click Activate / Deactivate on the toolbar. The button is a toggle, so the same button switches an account back on later.
- Confirm the Active column on that row is now clear.
There is no separate save step. The change takes effect at the next sign-in attempt for that account.
What Changes When You Deactivate
| Surface | Effect |
|---|---|
| Sign-in | Refused for that account, correct password or not |
| Roles and permissions | Untouched; they are still attached and return in full on reactivation |
| Security audit trail | A permanent deactivation entry lands, plus every earlier entry stays |
| Schedule change history | Unchanged; entries recorded against that user remain readable |
| The schedule itself | Nothing moves. Jobs, capacity, and dates are unaffected |
| The username | Still taken, which is deliberate: it cannot be reused by accident |
How to Check It Worked
The Active column on the Users grid is the check. If it is clear, the account is off.
If you want a live confirmation, have the person try to sign in, or try their username with a deliberately wrong password from a test machine. The message deliberately does not reveal whether the account exists, is inactive, or simply has the wrong password, so read the grid rather than the sign-in message when you are diagnosing.
Reactivating Later
Select the account and click Activate / Deactivate again. The Active column ticks and the person can sign in immediately with whatever password is currently on the account.
One thing to watch: if the account was also locked out from failed attempts before you deactivated it, reactivating does not clear the lock. Those are two separate states on the row, shown in two separate columns, and each has its own button. If both are set, use Unlock as well.
Deactivate, Delete, or Reset: Picking the Right Action
The Users toolbar has several buttons that look interchangeable and are not. Matching the situation to the button avoids the classic support ticket where three actions were tried and none of them fixed anything.
| Situation | Right action | Why |
|---|---|---|
| Employee leaves the company | Activate / Deactivate (off) | Blocks access, keeps history, protects the username |
| Long leave, returning later | Activate / Deactivate (off) | One click to switch back on when they return |
| Locked out after failed attempts | Unlock | Leaves the known password in place |
| Forgot their password | Reset password | Sets a temporary one and forces a change |
| Account created by mistake, never used | Delete | The only case where deletion is genuinely tidier |
| Person changed jobs internally | Edit and adjust roles | Access should follow the job, not the account's existence |
A Quick Worked Example
A shop supervisor resigns with two weeks' notice. On his last afternoon the administrator opens Settings → 🔒 Security → Users, selects his row, and clicks Activate / Deactivate. The Active column clears. The next morning he tries to sign in from home and is refused. Six weeks later a customer disputes a delivery date on a job he rescheduled; the schedule change history still names him on that entry, so the planner can explain exactly what happened and when. Had the account been deleted, the login would have gone but the situation would be no cleaner, and the option to restore his access for a handover would have gone with it.
Common Mistakes
Deleting instead of deactivating. Deletion is permanent and buys nothing. It also frees the username, so a future starter can end up with an identity that looks like the departed person's in older conversations.
Removing all roles instead of deactivating. An account with no roles can still sign in; it simply sees almost nothing. That is not the same as blocked, and it reads as a broken installation to whoever tries it.
Assuming a password reset also blocks access. A reset replaces the password, it does not disable the account. If your goal is to stop someone signing in, deactivate.
Forgetting the lock is a separate state. Reactivating a previously locked account leaves the lock in place. Check both columns.
Next Steps
If the account you are dealing with is locked rather than being retired, how to unlock a locked-out user is the fix, and how to assign multiple roles to a user covers access changes for an internal move. For the full task library, see the EDGEBIC how-to hub, and for the platform overview, EDGEBIC.
Expert Q&A: Deep Dive
Q: A supervisor left on Friday and we deactivated him, but he still shows up in old schedule change entries and reports. Should we delete the account to clean that up?
A: No, and deleting it would not clean it up in the way you are picturing. The security audit trail and the schedule change history record what happened and who did it; those entries are the point of keeping them. Deleting the login removes the ability to sign in but leaves the historical record, so you gain nothing and lose the ability to reactivate if a question comes up about a job he touched. Deactivation is the correct end state for a departure.
Q: We deactivated a user by mistake and now they cannot sign in even after we reset their password. What did we miss?
A: A password reset clears a lockout but does not reactivate a deactivated account, so the two fixes do not substitute for each other. Go back to the Users grid and check the Active column on that row. If it is clear, select the row and click Activate / Deactivate again to switch it back on. The person can then sign in with whatever password is currently set, which after your reset means the temporary one you issued.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
