Users

Short description of the functionality, that will be demonstrated in the example

Case summary Short description of a problem that we are going to explain in below. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Step title Step title

1. Step title

Within each step, state the sequence of the process in clear and concise sentences. If they follow each other in points, it is best to use indents.

• Text that contains name of field, button, menu or shortcut must be bold
• We encourage the use of images for buttons and shortcuts: +

2. Step title

• Lorem ipsum dolor sit amet, consectetur adipiscing elit.
• Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
• Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Hint This is a HINT and should be marked with this icon. If necessary, copy this whole table and add a new hint.

Warning This is a WARNING and should be marked with this icon. If necessary, copy this whole table and add a new warning.

Users

Users

On a 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

1. Settings for RE, LT, SE, GE, ME, MF

2. Specific settings for LT

1. Settings for RE, LT, SE, GE, ME, MF

The user is a person (more exactly: his or her 30-character user ID) logging in the program. 

Select users from Subjects register and set a 30-character ID for each of them. Because of this you can assign any given number of user IDs to the subject (an employe, customer, etc.)!

The following can be set for individual users:

• user menu
• user authorizations. by default the authorizations set are user group authorizations.
• personal settings, which are used for searching items by IDs and names as well as for searching subject IDs themselves
• there are the following funciotns for changing passwords and adding user groups made avialble by right-clicking in tree view of Administration Panel

Define the user by entering the following:

User	any 30-character alphanumeric ID designating the user. The user name "AD" is reserved for the program so that adding a user with this ID is not allowed. An error is returned when trying to save a user with this ID (see No user can have the ID "AD"!). It is also possible to login as Windows Authentication: DomainName\Username. Before saving the ID, it is checked whether any user with the same ID already exists. The following error is returned if so (see User with this code already exists!).  You cannot leave the field empty. So you cannot save the user without the ID given (see ID must be specified! Changes not specified!).
Language	Set a language of the user interfacr (menus, IRIS messages, forms and dashboards). Default is set as by default - that is, the user interface appears in the same language as program. The setting takes effect after upgrading! In case when the user language does not match teh language set for the program, and the correct version (language and localisation) can be found in the upgrade directory, and error is returned.
Subject	Select the subject (it is usually an employee but it may also be a customer, ...) from Subjects register, to which you want to assign user status. You cannot leave the field empty. So you cannot save the user without this it (see Subject must be defined! Changes will not be saved!).
Name	Name of User
Last Name	Last name of user
Copy Settings to Users in Group	Distribute settings to all users of the group.
Database to Use Licenses From	Database from which Pantheon license will be used. Setting is per User - for each user we can determine which licese will be used. By confirming this setting Program asks: "Are you sure you want to reproduce the setting among all users of the group?" Click Yes - for all users. Click NO - for current user. Eg.: accountants can use their license when accessing Pantheon on database from their clients. In case of utilization of license from other database, information is shown in the Instalation program. Licensing rules and instructions for its establishemnt are explained in chapter Licesing and Product Keys.
Licences	A list of licenses that the user has available at his location via serial number. Select a license and save change. When user enters a program, selected license is used. This setting overrides program parameter /SE, /RE etc. that can be used in start parameter.
SQL Server	Select a Linked SQL server (if in use) and then select a database from a Linked SQL server from which Pantheon license will be used. Linked Server must have RPC and RPC Out set on True (in SQL Management Studio) in order to be able to select databases.
Administrator	User has the permissions to work with users (create, modify, delete). There must be at least one user with "Administrator" privileges. AD user therefore cannot be deleted and user cannot change this parameter to itself. When Pantheon user is withdrawn of "Administrator" privileges he is also authomatically withdrawn of "sysadmin" privileges on a server (login). All users (server logins) have "db_user" privileges.
Database roles	Set a database role for a current user: Owner or Reader/Writer/Executer
Refresh	Fills all databases on a SQL server.
Change the DB role on all Databases	Changes current DB role to either Owner role or Reader/Writer/Executer role.
Activate Users in all Databases	User is activated on all databases on server. Activation is only possible if conditions meet the requirements; there must be existing Subject, Department, Usergroup, Build version.
Dectivate Users in All Databases	User is deactivated on all databases on server. When deleting user, program asks wether we want to delete authorization for this user.
Set Password	Form for setting/resetting password.

• New Password - enter the password for the SQL server that user will use everytime for login into Pantheon. The password is hidden on the screen. The required minimum password length is set in program parameters.
• Confirm Password - in order to control the correctness of the entered password, it must be entered again. Both passwords must match in order po proceed.

You need to save any changes made to user related data by using . If you do not do it, a warning is returned when moving with the pointer somewhere else:

Confirm if you want to save changes and reject them by clicking Cancel if you do not want to do so.

Operations that have access also on other databases on the same SQL server can be prevented with authorizations. Such user is prevented to access any linked databases or current database through Pantheon. Authorization is located:  Datalab Applications - Datalab PANTHEON - Settings - Program - Administration Panel - Database - Access to Other Databases

	Without using an efficient user identification system authorizations prove useless. If you assign authorizations, you need to provide that every user signs up 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.
	Every PANTHEON user is assigned a corresponding SQL user name. For more information on this see topic System Environment | SQL Users in PANTEHON .

2. Specific settings for LT

Using LT edition allows you to additionally assign authorizations for the entire program, that is:

	by using a selection table in taskbar where you can select a level of authorizations for the ENTIRE program (the authorizations tree view is not available in this edition)
	Time Limit for Making Changes - the data 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 = the current day 1 = the current day and day earlier 30 = past 30 days -1 = no restrictions - you can change at will

See also:

• adding and deleting users 
• transferring users between groups