User Profile

1Purpose #

Two jobs, and no others. It tells you who the application currently thinks you are — which login, which role, which company and branch you picked — and it lets you set a new sign-in password for yourself.

• Use it to confirm you are signed in as the right person before blaming a screen for hiding something: nearly every "why can I not see this" turns out to be the role or the branch shown here.
• Use it to change your own password. Nobody else's — this screen can only ever change the account you are signed in with.
• It is not an editor. Name, address, phone numbers, e-mail and photo are shown read-only. There is no Save for them anywhere on this page.
• The details are a snapshot taken at sign-in . If an administrator corrects your e-mail while you are working, this page keeps showing the old one until you sign out and in again.

2Changing your password, step by step #

1. Check the card on the left really is you — the login name and role are what the rest of the application acts on.
2. In Current Password , type the password you signed in with. Getting it wrong is the commonest failure, and the message says so plainly.
3. Type the new password in New Password , then the same thing again in Confirm New Password .
4. Click Change Password . Pressing Enter does nothing here — there is no form to submit.
5. Answer Yes, Change in the confirmation box. Cancel leaves everything as it was and keeps what you typed.
6. Read the coloured message at the top of the page — the screen scrolls up to it for you. Green means the new password is now in force; orange or red means nothing was changed and says why.
7. After a green message the three boxes are emptied. Nothing else on the page changes, and you are not signed out.

3Field details #

The card and the two read-only panels

• Photo — the image stored on your user record. It can only be set outside this application; the placeholder outline means no image is stored.
• User ID — the internal number of your row in the login table. It is what the server uses to decide whose password is being changed, so it is worth quoting when reporting a problem.
• Login Name — what you type to sign in. The database itself refuses to let it be changed, on any screen, ever.
• User Name — your display name. Shown here, in the shell header and against anything you post.
• Role — your primary role only, as stored on the user record. Additional roles granted separately are not listed here.
• Company and Branch (Branch is shown in the ERP edition only) — the ones you chose after signing in, not a property of your account. They change when you switch company, without any change to your profile.
• Address, City, PIN Code, Mobile No, Residential Phone, Email — contact details held on your user record. They are display-only here. Email and Mobile No are not decoration: the leave workflow writes to them when it notifies you as an approver (as against notifying you as the employee, which uses the address on your employee record). An empty one there is why an expected notification was skipped.
• A dash (—) means the value is empty on your record, not that the screen failed to read it.

Change Password

• Current Password — required. Compared exactly, so case matters; a wrong value is refused by the server, never by the browser.
• New Password — required, at least 6 characters and at most 50. The 6-character test ignores surrounding spaces but the password is stored with them , so a value typed as secret must be typed with those spaces every time you sign in afterwards. Do not start or end with a space.
• Confirm New Password — must match the new password exactly. Only used for that comparison; it is never sent anywhere.
• Change Password button — validates what you typed and then opens the confirmation box. Nothing is sent until you answer it.
• The message panel — orange for something you can fix, red for a refusal, green for done. Only one message is shown at a time: checks stop at the first failure.

4Rules and integrity #

• You can only ever change your own password. The account is taken from the signed-in session by the server, never from anything this page sends, so this screen cannot be pointed at somebody else.
• Every check is made twice. The browser checks first only to save a trip to the server; the server checks again and its answer is the one that counts. The wording is deliberately identical, so a message never changes meaning depending on where it came from.
• The old password is gone. The change overwrites the stored value — there is no history, no undo and no way back except changing it again to something you remember.
• You are not signed out, here or anywhere else. Your current session continues, and a session already signed in on another device keeps working until it expires on its own. Changing the password does not end it. If you are changing it because somebody else knows it, sign out everywhere as well.
• A remembered password on this browser goes stale. If Save Password was ticked on the sign-in screen, the old password is still sitting in this browser's storage and will be filled in for you — the next sign-in then fails until you retype it. Clear it by signing in once with the new password, whether or not you tick the box again.
• Refusals that are not about what you typed. A disabled account cannot change its password; nor can an account that signs in through Windows authentication, because it has no password stored here at all.
• Passwords travel to the server in readable form on the ordinary signed-in call and are encrypted there, because the browser cannot do this product's encryption. Over HTTPS that is protected in transit like everything else — but it is a reason to change a password on a machine you trust, not on a shared one.
• Nothing else on this page can be saved , so there is nothing here to lose by navigating away.

5Why a value looks wrong #

• It was corrected while you were signed in. The page never re-reads your record; sign out and back in to see the new value.
• Company or Branch is blank. You have not chosen a company yet, or you arrived here before the choice was made. Neither is stored on your account.
• Role does not explain what you can do. Extra roles are granted in the roles screen and are not shown on this card.
• The page bounced you to the sign-in screen. The session lives in the browser's memory only, so refreshing the tab ends it. Use the links in the application rather than reloading the page.

6If something does not work #