Description

In general, SiteKiosk has no direct influence on external applications, but there are two settings that can restrict their execution:

1. Window filters:
SiteKiosk Online can use the built-in window filters to block certain dialogs based on the title and/or window class. This prevents, for example, a command line window or settings dialogs of external applications from being displayed.

If you want to allow a specific window / dialog that is blocked by default, you can create a new entry in the project under ">Settings>Security>Custom window filters" with "Add window filter" that allows the window.
Possible parameters are window title, window class and window path to the executable file.

If SiteKiosk blocks a specific window, you will also find a notification in the SiteKiosk log (>Monitoring>[Client]>Logfiles).
Example:
[SiteKiosk] Window has been blocked:
Rule: Deny (WindowMessageClose) - Title: 'xxxxxxxxxx' Class: 'xxxxxxxxxx' Module: 'xxxxxxxxxx'
Window: Handle: xxxxxxxxxx Module: 'xxxxxxxxxxe' Title: 'xxxxxxxxxx' Class: 'xxxxxxxxxx'

2. access rights of the SiteKiosk user:
In "Autostart" mode, the SiteKiosk Online Client is started within the restricted local SiteKiosk user account (unless you have manually selected a different user).

The SiteKiosk user account has restricted rights to folders and the execution of certain EXE programs is blocked.
To change the user rights for the SiteKiosk user, you can use the System Security Manager > Customize (e.g. require full access to the folder in which the EXE to be started is stored).
The System Security Manager can be found in the Start menu in the administration account on the client.
Further information can be found here:
https://sitekiosk.online/help/en/Security2.html

You may also want to test the application while you are logged in as a SiteKiosk user, especially if you want to change user-dependent settings.
Here is the information on how to gain access:
https://www.sitekiosk.com/web/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=26577