Security

PSV and terminal passwords, local policy, and USB/HID

bg-dots
bg-dots

Security settings affect different objects. The personal PSV account password, terminal password, browser password generation, and USB/HID profile have different scopes.

Setting locations

Mechanism Location Purpose
Personal PSV password Configurations → Security → Account Change the password used to sign in to PSV
Local password policy Configurations → Security Requirements for generating device passwords from this browser
Terminal password Device details → user operations Separately change the terminal web interface password
USB/HID profile Configurations → Security; assignment in device details Restrict peripherals connected to the terminal

Personal account

The form contains the current password, new password, and confirmation. The interface warns that other sessions will end; confirm the exact sign-in procedure for the site version.

The administrator provides account provisioning instructions and available actions. These pages do not define a completed role model or a procedure for creating users in the interface.

Local policy and terminal password

The interface states Saved in browser. The policy defines requirements for device passwords generated from that browser. It is not a shared server policy for PSV accounts; changing it does not change existing passwords.

Generating a terminal password and applying it are separate actions. Confirm the target device and the agreed access method after the change. The terminal password is not the PSV user’s password.

USB/HID profiles

The form offers Allow all, Media only, and Block all. These are interface mode names; supported device classes and restrictions depend on compatible firmware.

Before applying a restrictive mode, agree on the test terminal, required peripherals, and a method to restore control. Saving a profile does not confirm its actual effect on the terminal; verify the result separately.

Sharing information

Transfer passwords, tokens, and keys through a protected channel. Send support the necessary identifiers and a description of the action without secrets. Ask the administrator about missing interface actions rather than bypassing them with direct requests.

Integrations Work scenarios