Run a short Lockbox test session, verify release and emergency access, then prepare a reusable lock template.
Start with a short test lock. Do not make the first session a long lock, Permalock session, or public-voting session.
Test-lock preflight
- Read Lockbox Safety and Emergency Access.
- Confirm the Lockbox is paired and online.
- Keep the Lockbox open until you have reviewed every release path.
- Make sure the Lockee can physically reach the Lockbox and its buttons.
- If a Keyholder is involved, complete the Keyholder preflight.
Start a short self-lock
- Sign in to the dashboard and open Chastity Lockbox.

- Choose the self-lock option.

- Select a short duration and leave advanced features off for this test.
- Review the summary, then start the session.

- Put the key in the Lockbox, close the lid/backplate, and confirm the mechanism reaches the locked state without obstruction.
Confirm the test is active
The physical Lockbox and dashboard should both show an active session. If they disagree, do not continue to a longer lock; use Connectivity Troubleshooting.
Test every release path
During the short test:
- Confirm the normal end-session action works.
- If a Keyholder is involved, have them end a separate short test and confirm the physical device unlocks.
- Locate local Emergency Unlock and review its confirmation screen without treating it as a punishment.
- Keep the hardware backplate procedure available offline.
Create a reusable template later
After a successful test, you can create or edit a reusable lock template in the Lockbox dashboard.

Review each option with everyone affected before saving. Features such as breaks, hidden time, public voting, Keyholder control, and Emergency Unlock availability change the experience and recovery path.

Do not enable an option you have not tested or do not understand. The dashboard and available options can change; if a setting is different from this guide, stop and contact support before relying on it.