Sign In
Operators sign in to CleverCommand using a login code and a one-time password (OTP). These credentials are created and managed by your company administrator through CleverOps. The sign-in process is designed for quick access -- especially important during shift changes when operators need to get into the system fast.
Prerequisites
Before you can sign in, you need:
- A login code assigned to you by your company admin in CleverOps
- Access to the OTP delivery method configured for your account (typically displayed in CleverOps)
- A supported browser (Chrome, Edge, or Firefox)
Sign-In Steps
- Open CleverCommand in your browser or launch the installed desktop app
- On the sign-in screen, enter your login code in the first field
- Enter the OTP (One-Time Password) in the second field
- Click Sign in
- Once authenticated, you are taken directly to the Events page
Quick Re-Login
CleverCommand saves your recent login history for fast re-authentication. When you return to the sign-in screen, you will see a list of recently used login codes. Simply select your login code from the list to pre-fill the field, then enter your current OTP.
Quick re-login is especially useful during shift changes. The outgoing operator logs out, and the incoming operator can select their saved login code and enter their OTP to be up and running in seconds.
Session Management
- Your session remains active as long as the browser tab or app window is open. CleverCommand renews it in the background before it runs out, using the server's clock, so a workstation whose own clock is wrong does not lose its session.
- If the session cannot be renewed -- for example it was ended from another device, or the sign-in server could not be reached for a long time -- you are returned to the sign-in screen with the message Your session ended. Sign in again to continue. The app never keeps polling on a dead session.
- Wrong workstation clock. If this computer's date and time are more than five minutes off, a banner at the bottom of every screen says This computer's clock is about … behind (or ahead) and how to fix it in Windows. You stay signed in, but event times shown are off by that amount until the clock is corrected. If a session ended because of it, the sign-in screen says so.
- If you close all CleverCommand tabs, you will need to sign in again on your next visit
- Signing in on one tab authenticates all CleverCommand tabs open in the same browser
- Signing out from any tab ends the session across all tabs in this browser only; your CleverOps and CleverAlert sessions stay signed in
Troubleshooting Sign-In
| Issue | Solution |
|---|---|
| Invalid login code | Double-check the code with your company admin in CleverOps |
| OTP not working | OTPs are time-sensitive -- request a fresh one from your admin |
| "Too many attempts" | The sign-in door limits wrong login code + OTP combinations as a protection against guessing. Five wrong tries for the same login code from one connection pauses that login code on that connection for 15 minutes; other operators on the same network, and the same operator on a different network, are not affected (the connection as a whole has a much higher limit, sized for a full shift signing in at once). Keep failing and the pause lengthens to an hour. Wait 15 minutes, or ask your manager to check your login code and OTP. Typing the right credentials never counts against you |
| Stuck on loading after sign-in | Check your internet connection and try refreshing the page |
Never share your login code or OTP with unauthorized personnel. Each operator should use their own unique credentials so that event actions are properly attributed.