Skip to main content

Create a Shared Lock

A shared lock template lets other people start sessions with your rules and you as their keyholder. Any user can create one, subject to their account's template and module allowances.

If you already have a self-lock and want someone else to control it, follow Invite a Keyholder instead.

Create a Template​

  1. Open the shared-lock template editor.
  2. Add a title, description, and cover image. A cover is required.
  3. Choose a timer or card-game lock, then configure its starting duration, rules, and modules.
  4. Review Duration & Limits, trust, and the safety options before publishing.
  5. Choose Create shared lock and share the resulting link with a wearer. Each person who starts from it gets their own session with you as keyholder.

Editing the published template changes the configuration for future starts. It does not rewrite sessions that people have already started.

You can save up to 3 personal presets per lock type for loading settings into the editor. This is separate from your account's limit on published shared templates.

LinkWhat the recipient does
Published shared-lock linkStarts a new session with the template creator as keyholder.
Saved personal-template linkLoads the configuration into an editor to review and use for their own lock or template.
Active self-lock share linkAccepts control of an existing wearer's session; see Invite a Keyholder.

Duration, Trust, and Requirements​

The initial duration, including a random duration's upper bound, is separate from the session's final time cap. Enable Limit lock time (cannot exceed maximum) and set Maximum Duration to impose a hard deadline. It applies to timer and card-game locks, including while frozen.

For timer templates, Minimum time locked sets the earliest release date that time reductions can reach, measured from each wearer's session start. Wearers see this as Minimum time enforced before joining. Set it to zero to disable it; an active session's minimum cannot be changed. See Minimum Time Enforced for an example and the release exceptions.

Force trust keyholder makes sessions from this template start with trusted-keyholder permissions. Explain this in your rules and review Trusted Keyholder before enabling it. Leaving it off normally starts the keyholder with limited permissions, but Trap Mode has separate powers.

Other requirements can narrow who can join:

  • Lock requires password from owner: give the wearer the password as well as the link.
  • Device requirements: require a supported QIUI or Lockink device if the template needs one.
  • Device Control: requires the wearer to complete the Android app's Device Control setup before starting.

Use Private lock template (Not visible in Explore) to keep the template out of Explore. People with its link can still open it; use the password setting when you also want a password required to start.

Emergency Release Options​

Under Safety & Advanced Features, configure Allow emergency release for wearers and Enable soft emergency release independently. Either, both, or neither may be enabled.

  • Ordinary emergency release permanently ends the wearer's session.
  • Soft emergency release is disabled by default. When enabled, set its slider to 1–5 uses per session or Unlimited. It permits temporary access and re-locking while preserving the session and its settings. Timers keep running by default, with no re-lock deadline. Optional settings can freeze the timer, require a new re-lock photo without an approval wait, and add unlocked time multiplied by a configured amount. See Emergency Release.

The wearer sees both settings and the soft allowance before joining. Keyholder lock details also show their status. Shared wearers select a reason for each soft release, and you receive a notification when they release and re-lock. Uses are logged and do not consume the hygiene allowance.

Editing these template settings affects future starts. For a session already running, its current keyholder can enable either disabled release option from Session Details, including restoring ordinary emergency release after the wearer disabled it. They can also increase an enabled soft release limit without resetting the used count. See Emergency Release for these controls, the wearer's combined release dialog, and re-lock steps.

Description and Media​

Describe the rules, expected interaction, enabled modules, and any payment or device requirements. Use the rich-text editor for headings, links, and formatting. Add up to 5 tags, then choose a Pixabay cover image or upload your own.

Welcome Message​

Enable the welcome message to show your instructions during setup. Use the editor's Confirm control to insert checkboxes for rules the wearer must acknowledge, and check the result with Preview welcome message.

Findom​

If you offer paid keyholding, complete Findom setup on your profile and enable This is a paid keyholding service on the template. Explain the payment expectations before someone starts. Asking wearers for payment without marking the template as a paid service can lead to account restrictions. See Financial Domination (Findom).

Trap Mode​

Trap Mode lets the keyholder add time or freeze the session through trap actions without trusted status. Its initial duration is capped at 60 minutes; the editor recommends 5–30 minutes. Trap Mode cannot be combined with the card-game module.

After the wearer starts, use the trap controls before the session expires. Trap actions can exceed the ordinary untrusted keyholder's time-addition budget and can freeze indefinitely.

Set the maximum separately

The short starting duration is not a final limit. Without a maximum duration, trap actions can keep adding time or freeze the session indefinitely, even without trust. An enabled maximum duration still caps the session, including while frozen.

Verification Photo Before Start​

Enable Enable verification photo before start to require a proof photo as part of the wearer's setup. This is separate from a photo that stores a lockbox combination.

In a supported Android or iOS app, the wearer can choose Camera - no handwritten note to take a live photo. Verified native captures show a Native camera label during review. Gallery uploads still need a handwritten note with the wearer's username and today's date, using the example shown in setup. If camera verification is unavailable, use a gallery photo with the note; if a capture expires, take a new photo before starting.

The wearer submits the photo when starting; you review it after the session has been created and receive a notification to approve or reject it. Rejection ends the session and makes release available. It does not physically open a combination box or guarantee that a connected device has received an unlock command. The wearer should complete the unlock flow.