> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/cradle-lock-screen.md).
# Cradle Lock Screen
## Overview
This feature displays critical information when the device is cradled. The screen provides the following:
* Device Name
* Site ID
* Battery Percentage
* Battery Health
* Remaining Time to Fully Charge
* Last Logged-in User
* Timestamp When Cradled
## User Guide
1. If this feature is enabled in the configuration, the device will enter Lock Screen mode as soon as it is cradled and no user is logged in.
2. When the device is cradled, the Cradle Lock Screen will display the following information: device name, site ID, battery percentage, battery health, remaining time to fully charge, last logged-in user, and timestamp when cradled.
3. The device will exit Lock Screen mode once it is uncradled and a user logs in.
## Feature Configuration
To enable this feature, set the `useCradleLockedMode` to true within the Launcher configuration file. Cradle Lock Screen feature is disabled by default.
```json
"settings": {
...
"useCradleLockedMode": true
...
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/cradle-lock-screen.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
