First sign-in

You sign in with your organizational user ID and your domain password. There is no separate Regulaxy password and no registration screen — the users are the ones who already exist in the directory service.

Both boxes are labeled Username and Password in English in the Hebrew interface too, and both are written left to right: the values themselves are Latin, and a Hebrew label above a Latin value makes the reader change direction twice to fill in one field. An eye button beside the word Password reveals what has been typed.

An Enterprise sign-in button appears below the form only in deployments where enterprise identity has been configured. Its absence is configuration, not a fault.

When sign-in fails

The system distinguishes between the reasons rather than returning one generic message:

What happened	What you see
One of the boxes is empty	The form is not submitted and asks for an ID and a password
The ID does not exist in the directory	A message that the ID was not found
The account exists and is disabled	A message that the account is disabled, pointing at the infrastructure team
The password is wrong	A message that says so
A valid ID with no permission to sign in	Sign-in refused — authentication succeeded, authorization is missing
The directory is not answering	The screen retries by itself
Too many attempts in a short time	A message that says to try again later

Lockout after failed attempts

Off by default. An administrator turns it on with two numbers: how many attempts are allowed, and over what window. While it is on, an attempt past the limit is refused before the directory is contacted at all, and the message says when to try again. A successful sign-in resets the counter, so a few typing mistakes never lock out a real user.

Session length and automatic sign-out

Session length is set in the settings, in hours, within a range of one hour to thirty days. The browser checks the session against that expiry every thirty seconds and again the moment you return to the tab, and returns you to the sign-in screen once it has passed — rather than leaving a screen that looks fine and loads nothing.

If the sign-in screen hangs

If sign-in has not completed within eight seconds, the loading screen is replaced by a short explanation and two actions: refresh the page, and return to sign-in. The explanation names the two usual causes — the API server is not reachable, or the browser is holding an old version of the page. It does not guess at a cause the browser cannot diagnose.