A standard login is initialised from the standard TermWeb application.
The permissions of each user can be configured in the administration page. Users can be members of user groups and be assigned permission schemes according to their group. Permission schemes can also be assigned to dictionaries and sections, in order to enforce security rules between sections More detailed information about permission management can be found in the User Manual.
Logged in users have each their own separate preferences. These preferences are automatically stored in the database. This allows the user to be able to select a dictionary, a filter or a term and access it directly after the next login. Also some more specific preferences like Gridview configuration is possible. User preferences are stored automatically with each action from the user during his session.
TermWeb sessions go along with the HTTP/HTTPS sessions created by the browsers. The session ids of TermWeb are the same as the HTTP/HTTPS session ids. This means the following:
Let’s say you login via a certain browser, e.g. Firefox.
Opening a new tab in Firefox will leave the session open and directly get you into TermWeb.
If you open a new Firefox window without closing the first one, then again the same session is being used and you directly get into TermWeb.
Even if you close the first Firefox window, but have at least one Firefox window open, even if it has not loaded TermWeb at all, the HTTP session of the browser stays open, and you get into TermWeb directly.
Now, only if you close all Firefox windows and open Firefox again, then a new HTTP/HTTPS session is created, so TermWeb opens in the login screen. In this case it is important to say that the TermWeb session stays open. This is why you may see a message of an already existing session of the same user and may need to click on the login button twice in order to close the previous session and keep the new one (HTTP/HTTPS session) as the active TermWeb session.
If you open another browser, let's say Chrome and login, then you will see the same behavior, as if you have closed Firefox and opened it again, because each browser has its own HTTP/HTTPS session.
This allows the following workflow: Open Firefox and login as user1. Open Chrome and login as user2. Since each session is different, TermWeb allows this and you can work with 2 different users on the same computer.