Signing In
The sign-in screen asks for a username and password. Everything else on it is optional and worth understanding once, because a couple of the options change how the client behaves every time you start it.
Signing in
- Enter your Username and Password.
- Choose Sign In.
In a browser, the server is the address you visited, so there is nothing to configure. In the desktop client you also choose which server to connect to, under Advanced.
Your credentials are the ones your administrator created for you — see Creating a User. Where your organisation uses a directory service, this is usually the same account you sign in to Windows with.
Choosing a server
The desktop client can talk to any eConnect server you have an account on. Open Advanced and set
the Server address, in the form https://server.example.com, then Connect.
Enter connects, so setting a server is a typed address and a keystroke rather than a reach for the mouse.
You only need to do this once per server; the client remembers it. If you work across more than one site, this is where you switch between them.
The options under Advanced
| Option | What it does |
|---|---|
| Save Password | Remembers your password on this computer |
| Auto Login | Signs you in automatically when the client starts |
| Allow self-signed certificates | Accepts a server certificate the machine does not trust |
Save Password and Auto Login are conveniences for a machine only you use. On a shared workstation, leave both off — anyone who opens eConnect on that machine would otherwise be signed in as you, and everything they then do is recorded against your name in the audit trail.
This tells eConnect to accept a server certificate your machine cannot verify, which also means it cannot verify it is talking to the right server. Use it only on a network you control, and only when your administrator has told you the certificate is expected. The better fix is to have the certificate trusted on the machine.
In a browser, an untrusted certificate also prevents eConnect being installed as an app — see Using eConnect in a Browser.
Which build you are on
The sign-in screen shows the build date of the server you are connecting to, in your own time zone rather than the server's. Hover it for the full build detail.
It is the fastest way to answer "am I on the version that has the fix?" — and the one piece of information worth quoting when you raise a support case.
If you cannot sign in
- Password rejected. Your organisation may enforce complexity and expiry rules, and repeated failures can lock the account. See Passwords and Resets.
- Account locked. Lockout clears after a period set by your administrator, or they can clear it.
- Cannot reach the server. Check the address under Advanced, and that you are on a network that can reach it.
- Certificate warning. Talk to your administrator before enabling the self-signed option.
After signing in
You land on Home, showing the modules you have access to. If something you expect is missing, it is a permissions or licensing matter rather than a fault — see Assigning Groups to Users.
Signing out
Sign out from the user menu in the title bar. eConnect also signs you out after a period of inactivity, which is covered — along with what each kind of sign-out records — in Session Timeout and Signing Out.