> ## Documentation Index
> Fetch the complete documentation index at: https://learn.biq.li/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the Biqli lock screen

> Require reauthentication before returning to a protected session.

The lock screen protects an already signed-in Biqli session when it is left idle or manually locked. Configure it from account security where available.

Unlocking confirms the current user's access without creating a separate account session. It is useful on a trusted shared workspace, but it does not replace your device lock, full sign-out, or two-factor authentication.

Sign out completely on a device you no longer control.

## Lock and unlock

Use the account lock action when stepping away from an active dashboard. Return
through the unlock prompt using the authentication requested by Biqli. The
underlying session remains associated with the same account.

## Understand the boundary

The lock screen protects against casual use of an open dashboard. It does not
encrypt the device, remove downloaded files, revoke API keys, or stop someone
who controls the browser profile and account recovery methods.

Use the operating-system screen lock as well. On shared or unmanaged hardware,
sign out and remove saved browser credentials instead of depending only on the
Biqli lock screen.

If unlock behavior is unexpected, sign out fully, clear the untrusted session,
and review the sessions page.

## Frequently asked questions

### Does locking revoke the session?

No. It protects the open interface until unlock. Use sign-out or remote session
revocation when the session itself should end.

### Does it protect downloaded exports?

No. Files already saved to the device follow the device's own access controls.