[Feature Request] Require connection reason/justification when using Permanent Password (logged in Server Pro audit logs)

Description:

For auditing and compliance purposes, we require a feature that logs the reason or justification whenever a remote session is initiated using a Permanent Password.

Currently, when connecting to a remote host, there are two primary authorization paths:

1. User Acceptance:

The end-user manually accepts the incoming connection request on the target machine.

2. Permanent Password:

The administrator/supporter connects directly using a predefined permanent password.

Proposed Feature:

When a connection is initiated using a Permanent Password, the client should prompt the user to enter a "Reason for Connection" (e.g., Ticket ID, Reason for Access, or Brief Notes).

Prompt:

A mandatory or configurable text field displayed during or immediately after permanent password entry.

Logging:

The entered reason must be sent to RustDesk Server Pro and stored alongside the session audit logs (Connection Logs / Session History).

Configurability:

Ideally, this prompt can be made mandatory via RustDesk Server Pro policy for unattended connections.

Use Case / Security & Compliance Benefit:

In corporate and managed environments, unattended access via permanent passwords creates compliance risks if unsupported or unauthorized sessions occur. Requiring a justification for every password-based connection ensures full traceability, aligns with internal auditing standards, and simplifies ticket-matching in support workflows.

The issue does not identify files, tests, or entry points. Start by locating the permanent-password connection flow and the Server Pro audit-log or session-history integration, then clarify how policy configuration should work. Done means a reason is collected for the specified connections, transmitted to Server Pro, stored with the audit record, and enforced when configured.