Skip to main content

Lock and Unlock Feature

S
Written by Support
Updated this week

This guide explains how to use the Lock and Unlock feature when creating a Deckbox and a Landing.

1. Lock and Unlock Feature on Dropbeams (Deckbox)

When creating a Deckbox, the system may require you to include a Dropbeam, depending on the depth entered. You can also choose to include dropbeams manually.

Steps:

  1. Open the Deckbox modal and enter the required deck details.

  2. Locate the “Include Dropbeam?” radio button (grey by default).

  3. Click the radio button to enable dropbeams.

  4. The field “How many dropbeams?” will appear.

  5. Next to this field, click the lock icon to unlock it.

    • The lock changes from blue to white when unlocked.

  6. Enter the quantity of dropbeams by:

    • Typing the number directly into the textbox, or

    • Use the Numeric Up/Down arrows to increase or decrease the value by one.

  7. After entering the desired quantity, click the lock icon again to lock it.

    • The lock changes back to blue when locked.

  8. Click Save to keep the changes, or Cancel to discard them

Important:

  • Below the textbox, you will see a “Dropbeam minimum required” information icon.

  • This guides you on the minimum number of dropbeams required for that specific deckbox.

2. Lock and Unlock Feature on Height (Landing)

When creating a Landing, the Lock and Unlock feature is available for the Height field.

Steps:

  1. Open the Landing modal and enter the required details.

  2. Locate the Height field.

  3. Click the lock icon next to the Height field to unlock it.

    • The lock changes from black to white when unlocked.

  4. Edit the Height value as needed.

  5. Once done, click the lock icon again to lock the value.

    • The lock changes from white to black when locked

Summary

  • Blue lock (Dropbeam) = Locked

  • White lock (Dropbeam) = Unlocked

  • Black lock (Landing Height) = Locked

  • White lock (Landing Height) = Unlocked

The Lock and Unlock feature ensures that values remain fixed unless intentionally edited.

Did this answer your question?