Managed Lockdown for organizations
Understand Managed Lockdown capabilities, user controls, security boundaries, and how to request enterprise deployment guidance.
What Managed Lockdown offers
Managed Lockdown lets an organization make Whisperstream's Lockdown master control administrator-owned on managed Windows devices. It keeps Lockdown on and limits enhancement to Local, so cloud providers and Ollama remain unavailable.
When the administrator's management assignment remains in place, the control is reapplied across configuration changes, restarts, updates, app-data deletion, and reinstalls. Whisperstream shows Managed by your organization instead of offering the user a way to turn Lockdown off or perform its destructive reset.
Managed Lockdown is designed to resist changes by a standard Windows user. It is not a security boundary against someone who controls a local administrator account, device policy, or the installed application. Organizations should manage administrator access through their normal Windows security and endpoint-management practices.
What users can still control
Management changes authority over the master control, not the ordinary transcript-history choices inside Lockdown. Users can still:
- choose whether to save transcripts;
- manage their transcript password and recovery code;
- choose the transcript-history idle-lock interval; and
- export local support diagnostics.
A newly managed setup starts with transcript history off. Existing history, password, recovery, and idle-lock settings are preserved when management is applied. See Lockdown Mode for the user workflow and Settings and data locations for Export logs.
Plan an enterprise deployment
IT teams can assign Managed Lockdown through supported Windows device-management tooling or during managed installation. Deployment details depend on how the organization controls devices, administrator access, policy refresh, and application rollout.
Email support@whisperstream.io to request the private deployment and network appendix. It includes the validated installer and machine-policy procedures, removal and restart behavior, operational boundaries, and the verification checklist for a managed rollout.
Understand the boundary
Managed Lockdown controls Whisperstream's transcription, enhancement, and history behavior. It does not control the destination app that receives inserted text. Apply the organization's own storage, sync, sharing, and network rules to that app.
Safe diagnostics remain local unless a user deliberately saves and shares an export. The export excludes transcript and audio content, credentials, recovery codes, and the Lockdown access log.