Settings

This guide explains how to configure ProximityLock's settings to work best with your device and environment.

Do I Need to Read This? Only if you want to fine-tune! We set the defaults to work for most people. Just select your device and enable monitoring. You can come back here later if you need to adjust anything.

First Launch - Granting Permissions

When you first launch ProximityLock, macOS will request several permissions. All of these are required for ProximityLock to function properly.

1. Bluetooth Permission

ProximityLock needs Bluetooth access to scan for and monitor your devices.

When prompted: Click OK to allow Bluetooth access. Without this permission, ProximityLock cannot detect any devices.

2. Notification Permission

ProximityLock will request permission to send you notifications.

When prompted: Click Allow to enable notifications. You'll want these alerts, especially if something goes wrong with the locking process.

Checking Permissions Later

If you need to review or change permissions after initial setup:

Bluetooth: System Settings → Privacy & Security → Bluetooth → ProximityLock
Notifications: System Settings → Notifications → ProximityLock

Configuring ProximityLock

Once permissions are granted, you're ready to configure ProximityLock. The screenshots below show you exactly what to expect.

Note: We set the defaults to be intentionally relaxed. Better to be patient than to lock your computer while you're still sitting there. Once you see how ProximityLock behaves in your environment, you can adjust the threshold and timeout to match your workspace and security needs.

Step 1: Open Settings

In the main window, click the Settings... button located to the right of your selected device name.

Step 2: View the Signal Graph

The settings window opens with a real-time signal strength graph at the top. This graph is your key to understanding ProximityLock's behavior:

The blue line shows your device's RSSI (signal strength) over time
The graph displays up to 200 readings or 10 minutes of signal history (whichever is less)
Green-shaded area = signals strong enough to keep your computer unlocked
Red-shaded area = signals too weak, will trigger a lock if sustained
The red dashed line is your adjustable threshold

Step 3: Select Your Device

In the device list at the bottom of the settings window:

Look for your device (e.g., "mks-iPhone", "Michael's Apple Watch")
Click the selection indicator next to your device name
The selected device will show a blue checkmark
Note the device's current RSSI value and quality indicator (Good/Excellent)

Can't find your device? Make sure Bluetooth is enabled on both your computer and the device. Some devices only advertise when they're not connected to other Bluetooth accessories. Try disconnecting other devices temporarily.

Step 4: Adjust the Signal Threshold

The threshold determines how weak the signal must be before ProximityLock considers your device "out of range":

Look at the right side of the signal graph
Find the draggable threshold indicator (circular handle on the red dashed line)
Drag it up or down to adjust the threshold
The red dashed horizontal line shows your threshold across the graph

Understanding threshold values:

Lower values (e.g., -80 dBm) = Less sensitive, need to be farther away to trigger lock
Higher values (e.g., -60 dBm) = More sensitive, triggers lock sooner

Need a quick refresher? See the Threshold FAQ entry.

Best Practice: Watch your device's signal on the graph to see where it typically sits when you're at your desk. Set your threshold a few dBm below this typical signal strength to account for normal fluctuations.

Step 5: Adjust the Signal Timeout

Below the graph, find the "Signal Timeout" slider. This setting determines how long ProximityLock waits before deciding you've actually left:

Drag the slider left for shorter timeout (2-5 seconds) = faster locking but more false alarms
Drag the slider right for longer timeout (15-30 seconds) = more patient, fewer false alarms

Why Timeout Matters

Bluetooth devices don't broadcast constantly. They advertise themselves periodically (like shouting "I'm here!" every few seconds). Sometimes these signals get missed due to:

Interference from other Bluetooth devices
Wi-Fi router interference
Your body blocking the signal
Other people moving between your device and computer

The timeout setting prevents ProximityLock from mistaking these temporary signal hiccups for you actually leaving.

Need a quick refresher? See the Timeout FAQ entry.

Environment Matters: Clean environment with few devices? Shorter timeout works well. Busy office with lots of Bluetooth devices and Wi-Fi? Go longer (15-20 seconds).

Step 6: Understanding Lock Events

ProximityLock Settings Showing Lock Event

The signal graph shows historical "lock events". Times when ProximityLock would have locked (or did lock) your screen based on your current settings:

Vertical dotted line - Marks the exact time when a lock would be triggered
Orange/tan shaded region (before the line) - Your timeout window where the signal stayed below threshold
Dark red shaded region (after the line) - The "locked" period after the lock was triggered

What this tells you:

If you see lock markers when you were at your desk → threshold too high or timeout too short
If you don't see lock markers when you walked away → threshold too low or timeout too long
Multiple lock events clustered together → noisy Bluetooth environment, increase timeout

Step 7: Save Your Settings

Click the blue OK button at the bottom right of the settings window to save your configuration.

Step 8: Enable Monitoring

Back in the main window:

Locate the Enable Monitoring toggle switch
Click the toggle to turn it ON (it will turn blue)

Step 9: Verify Protection

Look at the top of the main window. You should see:

A green background with a shield icon
"Protected" status
Subtitle: "Your computer will lock when the device goes out of range"
Your selected device showing "Ready for proximity monitoring"

Important Security Configuration

Critical: ProximityLock can start your screen saver, but macOS controls whether that screen saver actually locks your computer. For real security, you must enable:

System Settings → Lock Screen → "Require password immediately after sleep or screen saver begins"

Without this setting, ProximityLock will activate your screen saver, but anyone can wake it up without a password. Don't skip this step!

ProximityLock uses the screen saver mechanism because macOS doesn't provide an officially approved API for directly locking the computer. We chose this approach to use only Apple-approved, documented APIs, ensuring reliability and App Sandbox compliance. The screenshot above shows where to find this critical setting in System Settings.

Testing Your Configuration

Before trusting ProximityLock with your security, test it:

Test Notifications: Use Help → Test Notification to verify notification permissions work
Test Locking: Use Help → Test Lock to verify screen locking functionality (save your work first!)
Test Walking Away: Walk away from your computer with your device and verify it locks when expected

Tuning Your Settings

We set reasonable defaults, but every environment is different. Your desk setup, the number of nearby Bluetooth devices, building materials, and even how you carry your device all affect performance.

Our Recommendation: Live with the defaults for a few days, then fine-tune based on your experience:

Open Settings occasionally to watch the signal graph
Look for patterns in when locks occur
Adjust threshold and timeout based on what you observe
The graph tells you everything you need to know about what values work best for your situation

← Troubleshooting Help Topics How It Works →