Required user privileges to run InTouch HMI

Application Manager

Elevated privileges are not required to open the Application Manager. Certain operations within Application Manager do require running the Application Manager with elevated privilege.

The following operations must require Application Manager to be run as administrator:

• Open the Security configuration.

• Enable or disable WindowViewer as a service.

• Memory settings.

• Performance settings.

• Security settings.

If the Application Manager is not running with administrative privilege and when any of the above operations is requested, you will be notified with appropriate steps to follow.

Different login scenarios

• Logged in without InTouchDevelopers Operating System user group membership

  When a user is logged in on a machine and launches Application Manager, it will be launched without elevated privileges.

  • All toolbar items and menus, which require user to be a member of InTouchDevelopers OS user group, will be disabled.

  • All toolbar items and menus, which do not require user to be a member of InTouchDevelopers OS user group, will be enabled.

  • When WindowViewer is launched from Application Manager, WindowViewer will run without elevated privileges.

• Logged in with InTouchDevelopers Operating System user group membership

  When a user who is a member of the InTouchDevelopers OS user group is logged in on a machine and launches Application Manager without elevation, it will be launched without elevated privileges. In this case, all toolbar items and menus will be available.

• When executing toolbar or menu actions which require administrator privileges, the user will be prompted with a UAC (User Access Control) dialog to elevate the privilege. If user confirms on elevation, then the operation will be carried on with elevated privilege. The UAC dialog will be prompted for each operation that requires elevation.

  • Example 1: Modify the node properties and confirm when asked to elevate. The node properties will be updated.

• When executing toolbar or menu actions which do NOT require administrator privileges, the command will be carried on with non-admin privilege.

  • Example 1: Run WindowViewer from Application Manager. In this case, WindowViewer without elevated privileges.

• Run Application Manager with Elevated Privilege.

When either standard or administrator is logged in on a machine, if Application Manager is run with elevated privilege (run as administrator), it will be launched with administrator privileges.

• Any process launched from Application Manager will be run with elevated privilege.

  • Example 1: Run WindowViewer from Application Manager. In this case, WindowViewer will be run as administrator and with “elevated” privilege.

Application Manager operations allowed for a non-administrator user

The operations allowed for a non-administrator users are a subset of the operations allowed for a administrator. The following table lists the operations under each tab of the InTouch HMI Application Manager:

InTouch Tab

Web Client Tab

WindowMaker

Beginning with System Platform 2026, WindowMaker runs without requiring elevated privileges. The User Account Control (UAC) prompt is no longer displayed during startup.

You can launch the following applications from WindowMaker. Running these applications requires administrator privileges, and the operating system may prompt the user to elevate privileges when they are opened.

• Alarm printer

• Alarm DB logger manager

• Alarm DB purge-archive

• Alarm DB restore

• Alarm hot backup manager

• Recipe manager

WindowViewer

Elevated privileges are not required to run WindowViewer. Even when an administrator is logged in on a machine, WindowViewer runs with the least possible privileges unless explicitly run as an administrator.

Note: When running InTouch, you cannot launch the InTouch Application Manager or WindowMaker with administrator privileges using a different user account than the one currently logged in. In other words, if you are logged in as User A, you cannot run the application as an administrator using User B’s credentials. The currently logged-in user must be a member of the Administrators group to run with administrative privileges.