- Home
- Blog
- EDGEBIC How-To
- How to Reset a User's Password in EDGEBIC
To reset a user's password in EDGEBIC by User Solutions an administrator selects the account on the Users tab, clicks Reset password, and sets a temporary password, which also clears any lockout and forces the user to choose a new password at their next sign-in. The admin-set reset is the path that works in every installation, whether or not a self-service email option is switched on.
This is the narrow task of resetting one password. For how EDGEBIC guards accounts and the plan behind them, read how EDGEBIC protects your schedule data, and for the wider setup 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 password-reset permission. The Security tab is hidden otherwise.
- You know the current password policy. By default a password needs at least 8 characters with an uppercase letter, a lowercase letter, and a digit, and your installation may require more. The temporary password you set must satisfy it.
- You have a way to hand the temporary password to the user securely: in person, or through your normal secure channel, not in plain email if you can avoid it.
Resetting the Password
- Open the Settings tab and click the 🔒 Security tab, then the Users sub-tab.
- Select the user's row in the grid.
- Click Reset password on the toolbar. A small password prompt opens.
- Type the temporary password, confirm it, and click the set button. If the password fails the policy, the prompt shows the error; adjust and try again.
- Give the temporary password to the user.
That single action does three things behind the scenes: it stores the new password, it clears the account's failed-attempt count and any active lockout, and it sets the must-change flag so the person is forced to pick their own password on the next sign-in.
What Changes When You Save
| Surface | Effect |
|---|---|
| The user's sign-in | The old password no longer works; the temporary one does |
| Lockout state | Cleared as part of the reset |
| Failed-attempt count | Reset to zero |
| First sign-in after reset | The user is forced to choose a new password before reaching the main window |
| Security audit trail | A permanent password-reset entry lands in the database |
The must-change behavior is what keeps the reset honest: you set a throwaway password to get the person back in, and the moment they sign in, EDGEBIC makes them replace it with one only they know, through the same prompt covered in how to change your own password.
How to Check It Worked
Have the user sign in with the temporary password. They should reach the change-password prompt immediately, set a new password that meets the policy, and land on the main window with their normal tabs. If they still cannot sign in, check two things on the Users grid: the Active column must be ticked, because a deactivated account is refused regardless of password, and the Locked column should be clear. If Active is unticked, use Activate / Deactivate; a reset alone does not reactivate a deactivated account.
Where Reset Fits Among the Account Actions
The Users toolbar has several buttons that look similar but solve different problems, and picking the wrong one is why a "reset" sometimes does not fix things. Match the symptom to the action:
| Symptom | Right action | Why |
|---|---|---|
| User forgot their password | Reset password | Sets a new temporary password and forces a change |
| User knows the password but is locked out | Unlock | Clears the lockout, leaves the password alone |
| User cannot sign in and the account shows inactive | Activate / Deactivate | A deactivated account is refused whatever the password |
| Someone left the company | Activate / Deactivate (deactivate) | Keeps history; avoids reusing the username by accident |
Reset is the heaviest of the sign-in fixes because it replaces the password outright, which is exactly why it also clears a lockout: a person who has forgotten their password has usually also failed enough attempts to trip the lock, and one action handles both.
A Quick Worked Example
A supervisor forgets her password over a long weekend. The administrator opens Settings → 🔒 Security → Users, selects her row, and clicks Reset password. He types a temporary password that meets the policy (at least 8 characters with an uppercase letter, a lowercase letter, and a digit by default) and confirms it. He tells her the temporary password in person. On Monday she signs in with it, is immediately prompted to set her own, and never has to share her real password with anyone. The audit trail records both the reset (against the admin) and her first sign-in (against her), so the sequence is fully traceable.
Common Mistakes
Assuming a reset email will go out. Self-service reset is installation-dependent. If a user says the reset email never arrived, do not wait for it: the admin Reset password button is the dependable path in every build.
Setting a temporary password that fails a stricter policy. After you tighten the policy, a short temporary password is rejected at the moment you set it. Type one that meets the current rules.
Using a reset when Unlock is enough. If the person still knows their password and the account is merely locked after failed attempts, unlock the account instead of resetting. Unlock is the lighter action and leaves the known password in place.
Forgetting the account is also deactivated. A reset clears a lockout but does not reactivate a deactivated account. Check the Active column and reactivate separately if needed.
A Note on the Audit Trail
Every reset lands a permanent entry in the security audit trail inside the database, recorded against the administrator who performed it, and the user's subsequent first sign-in is recorded against them. There is no viewing screen for that trail in the application today; it exists as an append-only record your administrator or support can query when a compliance question comes up. The practical takeaway is that admin resets are fully accountable even though they let one person set another's temporary password: the who, the when, and the follow-on sign-in are all on record. That is also why shared accounts undercut the whole system, since a reset on a shared login maps to no single person.
Next Steps
If the real problem is a lockout rather than a forgotten password, how to unlock a locked-out user is the faster fix. For the full task library, see the EDGEBIC how-to hub, and for where account security sits in the wider platform, EDGEBIC.
Expert Q&A: Deep Dive
Q: A planner is on vacation and forgot their password before leaving a critical schedule half-built. Can I get in without knowing their password?
A: You do not need their old password. As an administrator, select their account on the Users tab and click Reset password, set a temporary one, and sign in as them if you must, or hand the temporary password to whoever is covering. Every action is still recorded against that username in the audit trail, so the trail stays honest. If you want the returning planner to own their password again, leave the must-change flag on so they reset it on their next sign-in.
Q: We set a stricter password policy and now an old account cannot sign in even after a reset. What is happening?
A: The temporary password you set must itself satisfy the current policy. If your installation now requires, say, twelve characters or a special character, a shorter temporary password is rejected at the moment you try to set it, and the dialog shows the error. Type a temporary password that meets the new rules, save, and hand it over. Existing passwords are checked against the new policy at reset time, which is exactly why the reset is the moment the stricter rule bites.
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.
