|
| 1 | +--- |
| 2 | +id: Device-reservation |
| 3 | +title: Device Reservation on Private Cloud Devices |
| 4 | +description: Learn how to reserve private cloud devices in LambdaTest to ensure uninterrupted testing, fair access, and conflict-free usage across your team. |
| 5 | +keywords: |
| 6 | +- device reservation |
| 7 | +- private cloud |
| 8 | +- device booking |
| 9 | +- lambdatest devices |
| 10 | +- test scheduling |
| 11 | +url: https://www.lambdatest.com/support/docs/device-reservation/ |
| 12 | +site_name: LambdaTest |
| 13 | +slug: Device-reservation/ |
| 14 | +--- |
| 15 | +import CodeBlock from '@theme/CodeBlock'; |
| 16 | +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; |
| 17 | + |
| 18 | +import Tabs from '@theme/Tabs'; |
| 19 | +import TabItem from '@theme/TabItem'; |
| 20 | + |
| 21 | +<script type="application/ld+json" |
| 22 | + dangerouslySetInnerHTML={{ __html: JSON.stringify({ |
| 23 | + "@context": "https://schema.org", |
| 24 | + "@type": "BreadcrumbList", |
| 25 | + "itemListElement": [{ |
| 26 | + "@type": "ListItem", |
| 27 | + "position": 1, |
| 28 | + "name": "Home", |
| 29 | + "item": "https://www.lambdatest.com" |
| 30 | + },{ |
| 31 | + "@type": "ListItem", |
| 32 | + "position": 2, |
| 33 | + "name": "Support", |
| 34 | + "item": "https://www.lambdatest.com/support/docs/" |
| 35 | + },{ |
| 36 | + "@type": "ListItem", |
| 37 | + "position": 3, |
| 38 | + "name": "Python With Appium", |
| 39 | + "item": "https://www.lambdatest.com/support/docs/appium-python/" |
| 40 | + }] |
| 41 | + }) |
| 42 | + }} |
| 43 | +></script> |
| 44 | + |
| 45 | +# Device Reservation on Private Device Cloud |
| 46 | + |
| 47 | +**LambdaTest Device Reservation** enables users to reserve private cloud devices in **advance**, ensuring uninterrupted access during critical testing windows. By scheduling devices ahead of time, teams can **prevent conflicts**, eliminate last-minute delays, and run both manual and automated tests with greater reliability. This becomes particularly valuable for time-sensitive releases, large-scale regression cycles, and continuous integration pipelines, where guaranteed device availability is essential. |
| 48 | + |
| 49 | +Beyond preventing scheduling conflicts, Device Reservation also helps organizations **optimize resource utilization**, enforce fair usage policies, and gain clearer visibility into device allocation across teams, leading to more efficient and predictable testing operations. |
| 50 | + |
| 51 | +> Device Reservation feature is currently in **closed beta** and continuously improving based on user feedback. please reach out via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat**</span> or email us at **[email protected]** to enable it for your organization and try it out. |
| 52 | +--- |
| 53 | + |
| 54 | +## Use Cases |
| 55 | + |
| 56 | +- **Release-Day Reliability**: Reserve devices in advance to guarantee uninterrupted testing during production releases or hotfix rollouts. |
| 57 | +- **Parallel Test Execution**: Secure multiple devices for running automated test suites in parallel, speeding up regression cycles. |
| 58 | +- **Cross-Team Coordination**: Schedule device bookings across QA, Dev, and Ops teams to align on shared testing timelines. |
| 59 | +- **Peak Hour Management**: Prevent conflicts during high-demand periods by ensuring fair access and availability through reservations. |
| 60 | +- **Optimized Resource Utilization**: Track and manage reservations to avoid idle devices and maximize the ROI of your private cloud setup. |
| 61 | + |
| 62 | +--- |
| 63 | +## Device Reservation Workflow |
| 64 | + |
| 65 | +### Accessing the App Live Dashboard |
| 66 | +1. Open the [App Live Dashboard](https://applive.lambdatest.com/app). |
| 67 | +2. Enable the toggle for Private Devices (**Available only for private device customers**). |
| 68 | +3. The User will see two buttons: |
| 69 | + - **My reservations** – View all ongoing and upcoming reservations with filter options. |
| 70 | + - **Go to Reservations** – Open the calendar view to explore and manage bookings. |
| 71 | + |
| 72 | +First-time visitors will see an empty calendar and must create a reservation to begin scheduling devices. |
| 73 | + |
| 74 | + |
| 75 | + |
| 76 | +::: |
| 77 | + |
| 78 | +### Admin Privilege |
| 79 | + |
| 80 | +Admins have additional controls to manage device reservations, accessible inside **Go to Reservations** under the settings button (as shown below): |
| 81 | + |
| 82 | +- **Advance Booking Window** – Define how far in advance members can schedule reservations. |
| 83 | +- **Max Reservation Duration** – Set the maximum duration allowed for a reservation (1–48 hours). |
| 84 | +- **Active Reservations per Member** – Limit the number of active reservations per member (1–99). |
| 85 | +- **Devices per Reservation** – Define how many devices can be booked in one reservation. |
| 86 | + |
| 87 | + |
| 88 | + |
| 89 | +### Calendar View and Permissions |
| 90 | + |
| 91 | +The **calendar** view differs for members and admins: |
| 92 | + |
| 93 | +- **Members:** |
| 94 | + - The member view shows a calendar with reservation blocks for devices. |
| 95 | + - `Blue blocks` represent the member’s own reservations, which can be edited or deleted. |
| 96 | + - `Grey blocks` represent reservations made by other team members. Members cannot edit or delete these. |
| 97 | + |
| 98 | +  |
| 99 | + |
| 100 | +- **Admins:** |
| 101 | + - Admins can view and manage all reservations on the calendar. |
| 102 | + - They have full control to create, edit, or delete any reservation. |
| 103 | + |
| 104 | +### Creating a Reservation |
| 105 | + |
| 106 | +To create a reservation, click **Reserve Device** from the calendar view. Then choose the type of reservation: |
| 107 | + |
| 108 | +- **Immediate Reservation** – Reserve a device instantly for 1 to 12 hours. |
| 109 | +  |
| 110 | +- **Future Reservation** – Schedule a reservation for a later date/time within the allowed scheduling window. |
| 111 | +  |
| 112 | + |
| 113 | +Select **one or multiple devices** based on availability and confirm the reservation. |
| 114 | + |
| 115 | +### Viewing and Editing Reservations |
| 116 | + |
| 117 | +After adding reservation slots, the user can view them under **My Reservations** and make edits or cancellations if required. |
| 118 | + |
| 119 | + |
| 120 | + |
| 121 | +### Session Expiry and Extensions |
| 122 | + |
| 123 | +These rules apply to both admins and members, except admins can still override reservations. |
| 124 | + |
| 125 | +- In the last **15 minutes** of a reservation, a pop-up appears notifying the user that the session is about to end. |
| 126 | +- If no pre-booked reservation exists for the device, the user will have the option to extend the session. |
| 127 | +- If another booking is already scheduled for the device, the extension option will still appear, but the request will **fail**. |
| 128 | +- Once the reserved time ends, the device session is automatically closed and released. |
| 129 | + |
| 130 | +:::tip |
| 131 | +- Reservation cannot be edited after the slot has been started. |
| 132 | +- If an **admin** deletes any reservation, it is **cancelled** immediately. |
| 133 | +- In automation, reservations cannot be extended automatically in the last 15 minutes. Extensions must be handled manually. |
| 134 | +::: |
0 commit comments