This is the language spoken by the user. If you have more than one language version of Isah, you can use this field to specify the language in which the Isah user interface is to be displayed. If the relevant language version is installed correctly, the Isah user interface will be shown in this language.

If you select this check box, the user may use another routing for a sales file, production file, or purchase file, instead of the default routing.

If this check box is not selected, the user is not allowed to do so. This means that:

• The user is not allowed to change the routing code on the sales line, in the production file, or on the purchase line.
• The user is not allowed to change the value of the Routing required check box on a sales line, in a production file, or a purchase line.
• When changing the status on the sales line, in the production file, or on the purchase line, the user may only enter a status that follows or precedes the old status in the routing. The user is therefore not allowed to skip any statuses.

Note: If configured in the default values for users, this check box is automatically selected for all new users.

Specify whether the user may perform processes for other users. When processing parts receipts, a user might choose to register not just his own receipts, but also another user's receipts.

If you leave this check box empty, the user will not be allowed to execute processes for other users.

Use the Code for bottleneck analysis presets field to enter a code for the lines you create with the Run bottleneck analysis process. Enter the code you use most frequently. This code will automatically be filled in on the Run bottleneck analysis form. As a result, all created lines will have this code. In cases where another code is to be used, you can change the code before you start the process.

Using codes is practical for a number of reasons. Once a code has been set, the Bottlenecks preset, which is available on various order forms, will show only the non-corrected bottlenecks with your code. Also, as mentioned above, the code will be used as the default code on various forms, such as the processing form for performing analyses.

If different types of bottleneck analyses are performed within your company, it may be useful to assign each analysis a different code for presets.

• If your company performs periodic batch analyses as well as occasional analyses for one or more orders, enter the batch analysis as the default setting. This setting is used by default in the bottleneck analysis cockpit and in the presets for the different forms. To perform one of the occasional analyses, select a different code for presets on the processing form.
• If both sales and purchasing employees perform bottleneck analyses, the user-specific default setting ensures that every employee only sees the most recent bottleneck analysis that is relevant to him.

This field is relevant if your organization wants to use the Integrated Login functionality. Before users can log in to Isah automatically by using Integrated Login, they must be linked to Windows users. Follow these steps to configure Integrated Login:

1. In the Windows user name field, enter the data of the Windows user you want to link to the Isah user. You can choose from the following data:
   • The User Principal Name: [User name]@[Company internet domain]. This is the most common format.
   • The domain and the user name: [Domain name]\[User name].

   For automatic login to work, the name the user uses to log in to Windows does not have to match the value in the Windows user name field. The only thing that is important is that the credentials belong to the Windows user in question.

   A Windows user can be linked to only one Isah user. A Windows user linked to an Isah user cannot be used for another Isah user. If you do, an error message is displayed.

   Repeat this step for every user. Make sure all Isah users are linked to a Windows user before you perform the next step, otherwise the users you have skipped are unable to log in to Isah.

2. Enable the Integrated Login option in Isah License Server. All Isah users that have a Windows user linked to them can now log in to all Isah databases automatically.

If you are going to use Integrated Login, the user rights will not change, which means you do not have to reset or change these rights.

Tip: If the Integrated Login functionality is used, it is possible to abort the automatic login in Isah and to log in as an Isah user instead of using a Windows account, provided that this Isah user is an application administrator. Aborting the integrated login is possible only if on the Users form the Windows user name field is empty. If you want to manage only Windows accounts, fill in the Windows user names for all users, including the application administrators. If a user is appointed as application administrator (the Has application administrator rights check box on the Users form is selected), that user will automatically have all rights to certain forms.

An application administrator manages user accounts and assigns rights to users or user groups in Isah. A user for whom the Application administrator check box is selected, automatically has all rights to particular forms, to allow him to perform application administrator tasks. If the check box is deselected, the user may still have application administrator rights if he or she belongs to a user group for which the Application administrator check box is selected. If a user has these rights (whether or not based on a group membership), the Application administrator based on user/group settings check box is selected.

There should be at least one user with application administrator rights.

Tip: If the Integrated Login functionality is used, it is possible to abort the automatic login in Isah and to log in as an Isah user instead of using a Windows account, provided that this Isah user is an application administrator. Aborting the integrated login is possible only if on the Users form the Windows user name field is empty. If you want to manage only Windows accounts, fill in the Windows user names for all users, including the application administrators.

Rights of an application administrator

Resetting passwords

To reset passwords, for example when users have forgotten their password, follow these steps:

1. Log in to Isah as an application administrator (as a user for whom the Application administrator based on user/group settings check box is selected).
2. On the Users form, select the user whose password you want to change.
3. Open the Change password process.
4. Do not enter the current password, but do enter the new password.

If your organization is using the Integrated Login functionality and only Windows accounts are being managed, refer to the Microsoft Help.

An application administrator in Isah automatically has all rights to certain forms. If the Application administrator based on user/group settings check box is selected for a user, then that user has the rights associated with the role of application manager. Application administrator rights are assigned to a user if the following conditions are true:

• The Application administrator check box on the Users form is selected.

  and/or

• The user has application administrator rights due to his membership of one or more user groups. This is the case if all of the following conditions are true for the group(s) to which the user belongs:
  • The Application administrator check box on the User groups form is selected.
  • At least one group is active (the Active check box on the User groups form is selected).
  • The user is an active member of that group (the Active check box on the Groups by user form is selected).

The Groups by user form lists all groups to which the user belongs.

Rights of an application administrator