Corporate mode for NVDA

[gerald-hartig]

Is your feature request related to a problem? Please describe.

Corporate (security) mode for NVDA. This mode is intended to enhance security while allowing certain configuration settings to be saved, providing a balance between security and customisability for enterprise environments.

Describe the solution you'd like

The solution involves developing a new mode called "Corporate Mode" which is based on the current "Secure Mode". The development plan includes the following features for version 1.0:

• Save configuration for most settings.
  • Allow changing and saving of settings related to speech, braille, audio and vision preferences, keyboard preferences and mouse settings, review cursor, input composition and object presentation.
  • Essentially exclude advanced settings and any settings that require administrative privileges to modify.
• Save gesture map / custom keyboard shortcuts and gestures for NVDA functions.
• Allow users to create, save and switch between different configuration profiles.
• Provide access to user documentation from within NVDA without requiring elevated privileges.
• Disable any features that require admin or elevated access.
• Addons are enabled, but disable installation of new addons.
• Disable the Python console.
• Disable custom configuration loading (-c).
• Disable creating portable installations.
• Rebrand existing "Secure Mode" to "Kiosk Mode".
• Creation of documentation for Corporate Mode (eg: setup guide, usage scenarios, enterprise troubleshooting tips).

This is essentially Secure Mode with a few punch-outs.

Describe alternatives you've considered

We could soften the existing "Secure Mode" by adding the required features directly into it. However, creating a distinct "Corporate Mode" allows for clearer differentiation and there is still a need for a fully locked-down mode. To avoid confusion with NVDA's elevated security during sign-on screens, the existing Secure Mode will be renamed Kiosk Mode.

Additional context

Features that are likely not to be included in version 1.0 but can be considered for future updates based on user feedback include:

• Checking for updates & auto-updates.
• Updating addons.
• Configurability of policy whitelist/blacklist.
• Allowing admins to enable/disable the log viewer.
• Allowing users to install/update specific addons from a whitelist.
• Integration with Active Directory / Group Policy
• Admin dashboards