 | Loading… |
|
|
|
Settings
       
Setting form determine user's server roles, set using license from another database, set subject and activation on different databases.
The form can be accessed by clicking the individual user on the Users panel in Administration Panel.
The form is made up of certain elements, which we describe below.
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.
|
|
|
Opens a new form Set password where you can set a new password for the user.
|
| Licences |
Specify which licence is assigned to user. Each user can have different license in use. This parameter overrides start parameters example: /SE, /RE etc. |
|
Server roles
|
 |
HINT
There are three most common levels of security principals:
Server logins, database users and security roles that we can put logins or users in.
Logins are created on the server level, we use them to connect to a SQL Server instance.
Users are created on the database level, we use them to access a database that they have permissions in.
|
- Administrator – If checked (
 ), user has the permissions to work with users (create, modify, delete). At least one user with Administrator rights (AD) 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.
 |
WARNING
Logins in system administrator (sysadmin) role have complete and total control of the whole SQL Server instance.
They have access to all databases, every object and every setting. |
- Security Admin - If checked (), logins in security administrator role (securityadmin) manage logins and their properties.
They change any server-level permissiona or database-level permissions if they have access to a database.
They can also reset passwords for SQL Server logins.
They should be treated almost equal to a sysadmin.
|
|
Database roles
|
Select the user's role for the database. You can select one of the following options:
- Owner - Users in Database Owner (dbo) role are similar to a sysadmins but apply only on a database level.
They have complete and total control of the database they are in.
They have access to every object and every setting that is database scoped.
By default they have no other SQL Server instace level access.
They can't change any server setting or view any server data or settings that do not apply to their database.
- Reader/Writer/Executer - Users in database reader (db_datareader) role can read all data from all user tables and views.
Users in database writer (db_datawriter) role can add, delete, or change data in all user tables.
In most use cases this role will be combined with db_datareader membership to allow reading the data that will be modified.
|
|
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!).
|
WARNING
Subject must have define a Contact person.
|
|
|
Touchscreen profile
|
Select POS profile from the drop-down list. When the user logs in to the POS, the desired profile will be opened. Each user can have their own 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.
|
|
WARNING
The language you choose also determines the language of the code lists that are updated when you upgrade.
|
|
|
Name
|
Enter or edit the first name of the user.
|
|
Last name
|
Enter or edit the last name of the user.
|
|
Tax No.
|
Enter tax number of the selected subject from the Contact/Clerk field.
|
|
ID of private individidual
|
Enter 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.
|
|
Refreshes and displays data on all databases that are on the server.
|
|
|
Changes current database role to either Owner or Reader/writer/executer role.
|
|
|
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.
|
|
|
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 (Owner or Reader/Writer/Executer).
|
|
Active/created?
|
If checked ( ), user is created and active in database and server.
|
|
Subject exists?
|
If checked (), user as subject exist.
|
|
Department exists?
|
If checked (), user as department exist.
|
|
Same build?
|
If checked (), structure of database and server is 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.
|
These buttons make it easier to compare user permissions by opening the form in a separate window.
 (Integrate) |
By clicking, User Settings console for selected user will open in separated window.
|
WARNING
Tabbed mode nedd to be enabled.
|
|
|
(Pop up)
|
Opens form in a separate window, which you can migrate to other screen for easier viewing. |
| Loading… |
| Loading… |
|
|
|
|