Login trouble in Fast WMS almost always comes down to one of a handful of things — the wrong login page, a licence limit, an expired session, or a deactivated account. None of them means your data is at risk. Work through the checklist and you will usually be back in within a minute.
Likely causes
- Wrong login page. Fast WMS has a separate desktop login and handheld login. Floor staff must use the handheld address; the same credentials will fail on the wrong page only because it is the wrong screen for that flow.
- Active-user cap reached. Your licence allows a set number of active users. When that is full, further logins are refused.
- Account deactivated. A user who left was set inactive and can no longer sign in.
- Session dropped. On on-premise installs a server restart or app-pool recycle logs everyone out at once — just sign in again.
- Wrong password or Caps Lock. The everyday culprit, especially on handheld keyboards.
- Machine binding. Some on-premise builds bind to specific machines; a brand-new device may need to be authorised.
Step-by-step fixes
- Confirm you are on the right login page — desktop users on the desktop URL, scanner users on the handheld URL.
- Re-enter the password carefully, watching for Caps Lock and trailing spaces.
- If you see a "maximum users reached" message, an admin should deactivate someone who has left to free a slot — see Adding a new user.
- If your account was deactivated, ask an admin to reactivate it (this may need a free licence slot).
- If everyone was logged out together, wait a moment and sign in again — the server likely recycled.
- Still blocked on a new device? Contact us to check machine authorisation.
Tip: avoid shared loginsGive every operator their own account. Shared logins hide who did what, and they burn a single session that logs the previous person out — a frequent cause of "it logged me out" reports.
Permissions and access levels are managed separately — if you can log in but a screen is missing, see Setting user roles and permissions. And if login works but the handheld won't upload scans, that's a sync issue: see The app won't sync after reconnecting.
