Creating a User

Add user on the user list creates an account. Creating it is quick; the part that matters is what you give them afterwards.

The steps

1. Add user and set a Username.
2. Set a Password and Confirm Password, or rely on directory authentication.
3. Fill in First Name and Last Name.
4. Add contact details if they will receive alerts.
5. Save.
6. Assign a permission group — see Assigning Groups.
7. Add them to a logical group if their view should be narrowed.

Steps 6 and 7 are the ones people forget. A new account with no permission group can sign in and see nothing, which reaches you as "eConnect is broken" rather than as a permissions question.

Naming conventions

Usernames are permanent in practice: they appear throughout the audit trail, and changing one makes historical records harder to follow.

Agree a convention and keep to it — matching your directory accounts is usually simplest, because it means one identity per person rather than two to reconcile.

Fill in the real name properly. It is what appears beside every audited action, and a blank or abbreviated name makes review needlessly hard.

Passwords

Where eConnect holds the password, it must satisfy the rules configured under Security Policy — length, complexity, and possibly expiry.

Set something temporary and have the person change it at first sign-in. See Passwords and Resets.

Where your organisation uses directory authentication, eConnect does not hold a password at all and the account is managed centrally, which is the better arrangement where available.

Service accounts

For an integration rather than a person, mark the account Service user. See The User List.

Give a service account the narrowest permission group that lets its integration work. Service accounts tend to be created once, granted broadly, and never reviewed — which makes them the weakest point in most permission arrangements.

Copying an existing user

Setting up someone in an existing role is usually best done by matching an established colleague's permission and logical groups rather than assembling from scratch.

Check what you are copying first. Roles accumulate access over time, and copying a long-standing account propagates rights nobody intended to grant again.

Confirm it worked

Have the person sign in, then look at their session history. A sign-in with no subsequent activity usually means they landed on an empty Home — permissions, not a fault.

What is recorded

Creating an account is audited under the user administration type, so every account can be traced to who created it and when. See What eConnect Audits.