User
On the form for a specific user you can determine user's server roles, set using license from another database, set subject and activation on different databases.
 |
WARNING
You can select users from the Subjects register and set a 30-character ID for each of them. This enables you to assign any number of user IDs to the subject (an employee, customer, etc.).
|
In this section, you can define the user settings and general information.
|
New user
|
Opens a blank window for entering a new user.
|
|
Confirm
|
Saves all changes made for the user.
|
|
Discard changes
|
Discards all changes made for the user.
|
|
Username
|
Any 30-character alphanumeric ID that will be used as a user name.
Before saving the ID, it is checked whether any user with the same ID already exists. If such an ID already exists, the program displays an error message (see the chapter A user with the ID {0} already exists.).
Entering the ID is mandatory. This means that it is not possible to save a user without an ID (see the chapter ID must be specified! Changes not saved!). The user ID must start with a letter and not with a symbol or number.
|
|
Set password
|
Opens a new window Set password where you can set a new password for the user.
|
|
Server roles
|
Check the relevant checkboxes to define the user as:
- Administrator – User has the permissions to work with users (create, modify, delete). At least one user with Administrator rights must be defined in the program. Therefore, the AD user cannot be deleted and user cannot change this parameter to itself. If you remove Administrator rights from a user, the user automatically loses sysadmin rights on the server (login). All users (server logins) have db_user rights.
- Security Admin
|
|
Database roles
|
Select the user's role for the database. You can select one of the following options:
- Owner
- Reader/writer/executer
|
|
Subject
|
From the drop-down list displaying subjects from the Subjects register, select the subject (usually an employee, but can also be a customer, etc.) to which you are assigning the status of the program user.
Entering the subject is mandatory. This means that it is not possible to save a user without the subject (see the chapter Subject must be defined! Changes will not be saved!).
|
|
Touchscreen profile
|
|
|
Contact/clerk
|
Depending on the subject selected in the Subject field, you can select the already created contacts for the given subject.
|
|
SQL server
|
Select a Linked SQL server (if in use) and then select a database from a Linked SQL server from which PANTHEON licenses will be used.
 |
HINT
The Linked Server must have RPC and RPC Out set on 'True' (in SQL Management Studio) in order to be able to select databases.
|
|
|
Database to use licences from
|
The database from which the licenses will be used. The setting is user-specific, which means that you can specify which licenses from which database will be used for each user.
If you are using licenses from another database, the information will be displayed in the Installation panel.
|
|
Language
|
Select the language of the user interface (menus, IRIS messages and language on forms).
The default option is Default, which means that the user interface will be in the same language as the program.
The setting takes effect after upgrading.
|
HINT
If the user language does not match the language set for the program, and the correct version (language and localization) can be found in the upgrade directory, an error message is displayed. For more information, see the chapter PANTHEON language change.
|
|
|
Name
|
Enter or edit the first name of the user.
|
|
Last name
|
Enter or edit the last name of the user.
|
|
Tax No.
|
Displays the tax number of the selected subject from the Subject field. The tax number is recorded in the General panel of the Subjects register.
|
|
ID of private individidual
|
Displays the ID or unique number of the contact person recorded in the Subjects register among the contacts.
|
|
Foreigner
|
Check this checkbox if the user is a foreigner.
|
In this section, you need to define the database server settings for each user.
|
Refresh
|
Refreshes and displays data on all databases that are on the server.
|
|
Change the database role on all databases
|
Changes current database role to either Owner or Reader/writer/executer role.
|
|
Activate user in all databases
|
Activates the user on all databases on the server. Activation is only possible if the following fields are populated with the required data: Subject, Department, User group, Build version.
|
|
Deactivate user in all databases
|
Deactivates the user on all databases on the server. When deactivating the user, the program asks wether you also want to delete authorization for this user.
|
WARNING
This feature does not work on hosted (cloud) databases.
|
|
After clicking the Refresh button, this section displays the user's database server information.
|
Database/schema
|
Name of the database on the server.
|
|
Database
|
Subject entered in the field This company field on the Company panel in Administration Panel.
|
|
DB role
|
User's role in the database (read/write/execute rights).
|
|
Active/created?
|
|
|
Subject exists?
|
If the subject exists, a  (checkmark) is displayed, while
a  (cross) is displayed if it does not exist.
|
|
Department exists?
|
If the department exists (is assigned to the user), a (checkmark) is displayed, while a (cross) is displayed if it does not exist.
|
|
Same build?
|
If the build is the same, a (checkmark) is displayed, while a (cross) is displayed if it is not the same.
|
|
WARNING
Without using an efficient user identification system, authorizations will prove useless. If you assign authorizations, you need to ensure that every user logs in into the program using his or her own user name. This can be done most easily by specifying a minimum password length so that no one can gain access without proper identification.
|
Using LT license allows you to additionally assign authorizations for the entire program.
|
|
Selection table in toolbar allows you to select the level of authorizations for the ENTIRE program (the authorizations tree view is not available for this license).
|
|
|
Days allowed to change – This information is used in assigning authorizations for individual documents. Set the number of days from document date during which the user is allowed to change/delete the document:
- 0 = current day
- 1 = current day and day earlier
- 30 = past 30 days
- -1 = no restrictions – can be changed always
|