
NoPass™
Passwordless workforce access and approval checkpoints for sensitive actions in your applications.
Explore NoPassNoPass™ / Desktop Unlock
Use your enrolled phone to log in to or unlock a Windows workstation. NoPass Desktop Unlock brings passwordless authentication to an access point employees use throughout the day.

Employees lock their computers when they step away and need a straightforward way back. Desktop Unlock uses the phone as a trusted token, bringing the authentication decision to a device the employee already uses.
The NoPass app connects the person to the configured authentication service. The supported confirmation can use mobile approval and local biometrics. Full Duplex Authentication® supplies the mutual-verification approach behind that experience.
Application permissions remain with each application. Your Windows edition and endpoint configuration determine the Desktop Unlock setup.
| Access point | Product route |
|---|---|
| Windows login and workstation unlock | Desktop Unlock with the required Windows and phone components. |
| A business application or remote-access gateway | The corresponding NoPass federation or RADIUS integration. |
Explore the illustrated workstation and phone interaction below. For a managed fleet, the team can identify the edition and deployment guidance for your Windows environment.
NoPass · Windows access · interactive example
Start the configured NoPass sign-in or unlock request. Your enrolled phone serves as the trusted device.
Check the workstation request and use the confirmation configured for the device, such as a biometric or one-tap approval.
Waiting for device confirmation
Approve access to your workstation?
The workstation receives the authentication result and applies its configured access policy.
Try the highlighted button or use the controls below.
| Question | Deployment decision |
|---|---|
| Windows environment | Confirm supported Windows versions and the intended domain or local-account configuration. |
| Components and connectivity | Identify the Windows component, enrolled phone and connectivity required by the chosen flow. |
| Fallback and recovery | Define who restores access when the device or connection is unavailable. |
| Rollout ownership | Test login, unlock, decline and no response with IT and representative employees. |