Settings (Users)

 (New user)

Opens a blank window for entering a new user.

HINT In the Set Password form, you can set user password.

 (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 form Set password where you can set a new password for the user.

Specify which licence is assigned to user. Each user can have different license in use. This parameter overrides start parameters example: /SE, /RE etc. - Multiple licences can be selected and when multiple licences are selected, form for selecting licence is opened when login into program. Select your license and confirm.

Server roles

HINT There are three most common levels of security principals: server logins, database users and security roles that can be assigned to the login or user. Logins are created on the server level and are used to connect to a SQL Server instance. Users are created on the database level and are used to access a database for which they have permissions.

• Administrator – If checked (), the 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 can change any server-level permissions or database-level permissions if they have access to the 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 the database level.
  They have complete and total control of the database assigned to them.
  They have access to every object and every setting on the database-level.
  By default, they have no other SQL Server instance-level access.
  They cannot 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 a Contact person defined.

Touchscreen profile

Select a 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.

WARNING The licensing rules for such use and guidance on setting it up such databases are explained in the chapter PANTHEON Licensing for Accounting firms.

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 registers 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.

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.

Dectivate user in all databases

Deactivates the user on all databases on the server. When deactivating the user, the program asks whether you also want to delete authorization for this user.

WARNING This feature does not work on hosted (cloud) databases.

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 (), the user is created and active in database and server.

Subject exists?

If checked (), the user as subject exists.

Department exists?

If checked (), the user as department exists.

Same build?

If checked (), structure of database and server is the same.

By clicking, User Settings console for selected user will open in separated window.

WARNING Tabbed mode needs to be enabled.

(Pop up)