Control Passes & Shared Control Links
Control Passes let visitors use selected controls on an active lock through a shared link. A pass defines the available powers, visibility, and limits. A power is a button that can perform one action or a bundle of actions. A share link gives visitors access to that pass for the current session.
The wearer and keyholder keep their existing roles. To transfer ownership of a self-lock to a keyholder, use Invite a Keyholder instead.
For a shared page with Add, Remove, and optional Random time votes, see Public Voting. Its cooldowns and link lifecycle are separate from Control Passes.
Created Control Pass links cannot be individually revoked through the current interface and have no separate expiry timer. Treat each link as permanent for the active session. Anyone who receives a copied link can open it; requiring an account does not restrict it to a particular person. Hiding a community-chat listing does not invalidate copied links.
Configure a Pass
Open Control Passes in lock setup, or choose Configure in its active-session panel when that control is available to your role.
- Choose Start from a preset → Add preset pass, or Add blank pass. Presets include Starter, Daily control, Crowd link, Strict control, Relief only, and High trust.
- Give the pass a clear title and description, then open Edit powers & limits.
- Review every power. Use New power action → Add power to add another button, and Bundled actions → Add action to add another effect to the same button.
- Set durations, any Visitor chooses duration range, and device intensity limits where applicable.
- Review Visible on the shared link, Link access, Power behavior, and Global limits.
- Save the configuration. Acceptance and share-link creation happen after the lock starts.
Start with a small set of powers whose effects are easy to understand. A preset is an editable starting point: review its actual buttons and limits before accepting it.
Choose What Visitors Can Do
| Power group | Available controls and important distinctions |
|---|---|
| Time | Add or remove a duration, double or halve remaining time, or clear remaining time. Clearing time does not itself end the session or satisfy other unlock requirements. |
| Freeze and timer | Freeze, unfreeze, or toggle freezing; reveal, conceal, or toggle the timer. Powers can be unavailable while frozen or available only while frozen. |
| Unlocking | Block unlocking adds a Control Pass restriction. Allow unlocking removes that restriction; other unlock requirements can still apply. Unlock now ends the session immediately, bypassing ordinary unlock requirements, and asks the visitor to confirm. |
| Hygienic unlock | Offer a break for the wearer to accept. Grant expires after is the acceptance deadline; Break duration is the time allowed after the break starts. See Hygienic Unlock. |
| Pillory and cards | Send the lock to Pillory or let visitors add/remove remaining cards. These powers need their corresponding lock features. Manage cards gives broader control than a fixed time adjustment. |
| Devices | Request shock, primary-device vibration, accessory vibration, or stop device activity. The required device must be configured, and delivery depends on its connection and current state. |
For device powers, review the pass's own duration and intensity settings. Do not assume limits configured in another device-control screen also limit this link. Shock queued means the request entered the queue; it does not mean output has started. See Shock Delivery & Queues.
Unlock now ends the Chastify session; it does not send a physical-device unlock command. In a bundle, it also stops execution of any actions listed after it.
One button can run several actions. A later failure does not roll back effects that already happened, and an attempted execution can still consume a use. After an error, refresh and inspect the lock before pressing the button again. Separate powers are easier to check than bundles containing several unrelated effects.
Review and Accept
On the active lock, open Control Passes → Overview → Review and accept. Check the complete power list, limits, access settings, and shared-link visibility. The wearer uses Sign and accept pass; an authorized keyholder uses Approve pass.
| Action | Self-lock | Shared lock |
|---|---|---|
| Accept a pass | The wearer accepts. | The wearer accepts. The keyholder can approve if the wearer enables Allow keyholder approval for this session. |
| Create a share link | The wearer can create links after acceptance. | The keyholder can create links after acceptance. The wearer also can if the keyholder enables Allow wearer-created links for this session. |
| Change those permissions | No separate keyholder permission is needed. | The wearer controls keyholder approval; the keyholder controls wearer-created links. |
Acceptance allows link creation; it does not create or publish a link by itself. The panel records who accepted or approved the pass and when. These permissions concern Control Passes and do not transfer lock ownership or grant general trusted-keyholder status.
Visitor Access and Privacy
Under Link access, enable Require Chastify account if visitors must sign in before using powers. Enable Block wearer from using links to prevent the signed-in wearer from using them; this option requires signed-in visitors.
Requiring an account checks who can act. The shared page and its permitted details can still be viewed by someone who has the link without signing in. There is no named-recipient allowlist in these settings.
Under Visible on the shared link, review:
- Show wearer details and Show keyholder details: usernames and avatars when available.
- Show lock status: the current lock-state panel.
- Show remaining time: reveals the countdown only when the lock allows it.
- Show locked-for duration: how long the current session has been active.
- Show pass details: the pass explanation and power descriptions.
Card counts, green-card progress, and remaining-time estimates are hidden when Show remaining time is off, the timer is hidden, or lock information is hidden. Turning off Show lock status hides the whole lock-state panel. These restrictions also apply to the shared-page API response.
Hide unavailable powers hides most unavailable buttons. A power with an already-pending hygienic-unlock grant can remain visible. When this setting is off, visitors can see unavailable powers disabled with a reason. This affects presentation; it does not grant access to an unavailable action.
Limits and Reset Times
The configuration is shared by links created from a pass, but usage is counted separately for each link. All powers on one link share that link's counters. Creating another link gives it separate counters; the label Global limits does not mean one combined allowance across all links.
| Limit | How to read it |
|---|---|
| Limit powers per day | The daily execution allowance for this link, across its visitors and powers. A bundled power consumes one use. |
| Limit powers per user per day | The daily allowance for a signed-in account on this link. It does not identify anonymous visitors; require an account if this limit matters. |
| Limit maximum time added / removed | Separate cumulative addition and removal allowances for this link. These do not reset with the daily use allowance. |
Daily counters reset at 00:00 UTC, which may differ from the wearer's local midnight. A value of 0 means unlimited, not disabled. An accepted attempt can consume a use even if an action later fails or its outcome is uncertain.
Time allowances count each reached action's requested duration, even if a lock's minimum or maximum duration limits the applied change. Additions and removals count separately, including inside one bundle. Double, halve, and clear-remaining actions calculate their requested change from the current timer, including adjustments accumulated while frozen. Halving an odd number of seconds keeps the extra second.
Each time change and its allowance charge are recorded together. Actions run in order; Unlock now stops the bundle. A later failure or concurrent change can stop a bundle after earlier effects have completed. Earlier effects and their charges remain, and the execution use is not refunded. Refresh and inspect the lock before trying again. Existing usage recorded before this fix is retained; earlier accounting gaps cannot be reconstructed automatically.
Change Limits During a Session
If available, open an accepted pass's limits, choose Edit, then Save limits. Existing links immediately use the saved settings.
- Self-lock wearer: can increase the maximum-added allowance, decrease the maximum-removed allowance, and increase daily use allowances. The reverse changes are not allowed through this editor.
- Shared-lock keyholder without keyholder approval enabled: can reduce allowances, but cannot increase them.
- Shared-lock keyholder with keyholder approval enabled: can increase or decrease allowances.
- Shared-lock wearer: cannot edit the accepted pass's limits through this control.
Remember that changing a value to unlimited increases the allowance. Reducing a daily allowance below the uses already recorded does not erase those uses.
Create and Share a Link
- Accept or approve the intended pass.
- Choose Create share link and read the permanence confirmation.
- Confirm, then use Copy to share the address or Open to inspect the visitor page.
Opening the link does not run a power. Pressing a power can change the real lock immediately; most actions do not have a second confirmation. Inspect the displayed settings before using it, including any visitor-selected duration or device settings.
The link operates against the current active session and enabled Control Pass configuration. An ended session or unavailable module can make it unusable. Do not treat temporary unavailability as revocation, or expect a copied link to disappear when you stop sharing it.
Show a Link in Community Chat
Choose Show in chat beside a link to list it in your selected community channel, subject to community access and posting restrictions. Choose a listing duration from 15 minutes to 7 days, then confirm.
Anyone with access to that channel can open and copy the link. Stop showing, or the listing reaching its deadline, removes the listing only. The original link can still work for the active session.
Activity and Troubleshooting
Use Activity log → Refresh for recent pass approvals, link creation, and commands used from links. The overview also shows each link's recorded uses and time totals. Treat this as recent activity; a recorded request or queued shock is not proof of physical device output.
| Problem | What to check |
|---|---|
| Cannot create a link | The lock must be active, the pass accepted, and your role allowed to create links. On a shared lock, check the wearer-created-links permission. |
| Waiting for wearer acceptance | The wearer must accept, or enable keyholder approval so the keyholder can approve. |
| Sign-in required or wearer blocked | Follow the pass's account rules. Copying the same link does not change them. |
| Power is unavailable or missing | Check daily limits, frozen state, available device, and required lock features. Unavailable powers may be hidden. |
| A time control did not change a frozen lock | Check the time allowance and minimum/maximum duration. Frozen adjustments are retained and applied when the timer resumes. |
| Action failed after something changed | A bundle may have partly run. Check current state and activity before repeating it. |
| Shock has not started | Check the wearer's queue and device connection. Shock queued is not a delivery confirmation. |
| Link stopped working | Check that the address is complete and that the original session and Control Pass module are still active. |
For an unresolved problem, see Contacting Support. Include the error, time, and power name. Avoid posting a live control link publicly when asking for help.