Skip to content

Rollout / Going Live

ScreenStop is designed to deploy silent-first: it watches and logs before it ever interrupts a user. This keeps the initial rollout frictionless and lets you tune detection against your environment before enforcing anything.

The golden rule

Install → verify it all works in silent mode → review false positives → only then enable enforcement. Never turn on enforcement on day one.

Step 1 — Deploy in silent mode (default)

New installs start silent automatically — the out-of-box General department ships with Audit Mode on. Stations begin detecting and reporting events the moment they connect, with no screen locks, blur, USB eject, or print cancellation, and zero user disruption.

Nothing to configure for this step — it's the default.

Step 2 — Verify everything works

Before changing anything, confirm the deployment is healthy:

  • [ ] Stations appear in Dashboard → Stations and show as online
  • [ ] Events appear in Dashboard → Events (e.g. phone, shoulder_surfing)
  • [ ] Events from silent stations show the Mode flag in the Events Explorer (detected, not enforced)
  • [ ] Users report no interruption (no unexpected locks/blur) — confirming silent mode is in effect

Step 3 — Baseline and review false positives

Let it run in silent mode for 1–2 weeks. Use the dashboard to review, per threat type, what's firing:

  • Which detections are accurate vs. noisy in your environment?
  • Phone, shoulder-surfing, and unattended detectors can each behave differently depending on lighting, camera placement, and desk layout.
  • Tune detection sensitivity (see Configuration Reference) where needed.

The goal: know your false-positive rate for each threat before any of them can interrupt a user.

Step 4 — Enable enforcement (the checkbox)

Only once you trust the data, turn on enforcement:

  1. Go to Departments → select the department
  2. Open the Audit & Capture Policy card
  3. Toggle Audit Mode off (this switches the department to enforcement)
  4. Click Save — stations switch within ~5 seconds

Enforcement turns the same detections into actions: screen lock/blur on phone or shoulder-surfing, USB eject, print cancel.

Go gradually

Don't flip your whole fleet at once. Enable enforcement on one pilot department first, confirm it behaves as expected for a few days, then roll it out to the rest. You can keep different departments at different stages (some silent, some enforcing) for as long as you like.

Rolling back

If anything misbehaves after going live, switch the department's Audit Mode back on — it returns to silent (log-only) within ~5 seconds, with no reinstall and no user impact.