EDGEBIC How-To

How to Change Your Own Password in EDGEBIC

User Solutions TeamUser Solutions Team
|
6 min read

To change your own password in EDGEBIC by User Solutions, sign in, open the change-password prompt, enter your current password once and the new password twice, and save. The new password has to satisfy the policy in force, which by default means at least 8 characters including an uppercase letter, a lowercase letter, and a digit.

This is the self-service change, the one you make on your own account. It is different from an administrator resetting somebody else's password, which is covered in how to reset a user's password.

Before You Start

  • You know your current password. Self-service change requires it. If you have forgotten it, you need an administrator to reset the account instead.
  • You have somewhere safe to record the new password, ideally a password manager. There is no recovery path that does not involve an administrator.
  • You know the policy. By default: minimum 8 characters, maximum 128, at least one uppercase letter, one lowercase letter, and one digit. Your site may require more.

Changing the Password

  1. Sign in to EDGEBIC normally with your current password.
  2. If an administrator reset your account with Must change password on next login ticked, the change prompt opens on its own before you reach the main window. Skip to step 4.
  3. Otherwise open the change-password prompt from your account area in Settings.
  4. Type your Current Password.
  5. Type the New Password, then type it again to confirm.
  6. Click the change button.

If the current password is wrong, the change is refused with a plain message and nothing is saved. If the new password breaks a rule, the prompt tells you which rule and your old password stays in force until you get it right.

What Changes When You Save

SurfaceEffect
Your sign-inThe old password stops working immediately; the new one is live
The must-change flagCleared, so you are not prompted again next time
Failed-attempt counterUnaffected by a self-change; only sign-in attempts move it
Security audit trailA permanent password-changed entry lands in the database
Other usersNothing. A password change touches only your own account

How to Check It Worked

Sign out, then sign back in with the new password. You should land straight on the main window with your usual tabs and no change prompt in the way. If you are bounced back to the change prompt again, the must-change flag was not cleared, which usually means the save did not complete. Try once more and watch for an error message rather than assuming it worked.

If the new password is refused at sign-in, check the obvious first: caps lock, and the fact that the username is not case-sensitive at sign-in but the password very much is.

Why a Self-Change Beats an Admin Reset

An administrator reset is the recovery path, not the routine one. It is heavier because it hands your account's password to another person, even if only for a few minutes. A self-change never exposes your password to anyone.

That difference matters because EDGEBIC records security events permanently. Sign-ins, failed attempts, lockouts, password changes, and password resets all land in a security audit trail inside the database. If everyone shares a login, or if passwords keep passing through the administrator, the trail stops mapping actions to people, and the record loses most of its value in an audit conversation.

A Quick Worked Example

A new planner joins on Monday. The administrator creates her account with Must change password on next login ticked and gives her a temporary password in person. She launches EDGEBIC, signs in with the temporary password, and the change prompt opens before the main window. She types the temporary password as the current one, then her own password twice, and saves. She reaches the main window. The trail now shows the account creation and the reset against the administrator, and the password change and every later sign-in against her.

Common Mistakes

Typing the temporary password into the new-password box. The current field takes the password you were given, the new fields take the one you are choosing. Reusing the temporary password in both is a common slip and defeats the whole point of the prompt.

Choosing something that just squeaks past the rules. Eight characters with one capital and one digit is the floor, not a target. The policy cannot stop a weak-but-legal password, so that judgment is yours.

Assuming there is a reset email. Self-service reset by email is not enabled in every installation. If you lock yourself out of a password you have just changed, the fix is an administrator, not an inbox.

Sharing a login so nobody has to remember a password. The audit trail is the reason one account per person matters. A shared login makes every entry ambiguous.

Next Steps

If a colleague is locked out rather than merely wanting a new password, how to unlock a locked-out user is the faster fix, and how to set up users and roles covers the wider account structure. For the full task library, see the EDGEBIC how-to hub, and for where account security sits in the platform, EDGEBIC.

Expert Q&A: Deep Dive

Q: Our admin handed me a temporary password on a sticky note. How do I stop that password from being the one that lives in the system?

A: Sign in with the temporary password. If the administrator ticked must change password on next login when resetting, EDGEBIC forces you through the change prompt before the main window even opens, and the sticky-note password stops working the moment you save your own. If you were not forced through the prompt, go and change it yourself right away rather than leaving a shared password active. The change is recorded in the security audit trail against your username, so there is a record that ownership of the account moved back to you.

Q: I changed my password on my workstation but a colleague says the old one still worked for them ten minutes later. Is the change not taking?

A: Check that you are both pointed at the same database. Passwords live in the EDGEBIC database, not on the workstation, so on a shared SQL Server every install sees the change immediately. If one machine is still running on its own local database file, it has its own separate user table with its own separate password, which is exactly the symptom you are describing. Confirm the connection on the Settings DataSource tab on both machines before assuming the change failed.

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

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.

Let's Solve Your Challenges Together