This chapter explains WatchTower alerts, immediate actions, website-managed Block List rules, and staff permissions. The website is the rule authority; the in-world machine reports fresh land presence, receives a verified command, performs the supported action, and reports the result.
Alerts
An alert is an owner-important event, not every heartbeat or scanner packet. Useful alerts include a machine going offline, a location exceeding plan capacity, payment review, a watched avatar being seen, a failed action, Access Gate activity, or a delivery failure.
Warn and Kick Now
- Warn sends one private message to a fresh visitor UUID.
- Kick queues the verified land-eject action for a visitor currently reported on protected parcel or same-owner/group land.
- Region-only detections are view-only and never qualify for land actions.
- The result and requesting account user remain in the audit trail.
WatchTower Block List
The Block List is stored on the website and is independent of Second Life’s limited land access-list capacity.
- Block Here applies one avatar UUID to one selected protected location.
- Block Everywhere applies one avatar UUID to every active location on the same WatchTower account.
- When a blocked UUID is freshly detected on protected land, the website queues the same verified eject action used by Kick.
- Repeated scans during one visit are deduplicated. A later return starts a new presence session and can create a new enforcement event.
- A machine becomes ineligible ten minutes after its last heartbeat. Another eligible machine at that location may take over queued work.
- Removing a rule stops future enforcement but preserves removal and command history.
What the Block List does not do
It does not write to or synchronize Second Life’s native land access list. Enforcement requires an online WatchTower object with the Second Life land authority needed to eject at that location. No website can bypass parcel, group, estate, simulator, or LSL permission limits.
Access Gate
Access Gate compares the Second Life account age reported to the website against the selected 15, 30, 45, 60, 90, 120, 150, 180, or 360-day threshold. It can warn, wait for the configured 15-30 second window, then request eject. Owner, manager, and UUID exemptions are applied before enforcement. This feature is not real-world age verification.
Staff permissions
Owners have full account control. Staff permissions should separately control viewing security history, sending warnings, using Kick, adding Block rules, removing Block rules, and managing account settings. Every mutation remains account-scoped and audited.
Good owner-facing wording
WatchTower records what an eligible terminal reported, queues permission-dependent Warn/Kick actions, and can re-enforce website Block rules when the UUID returns to protected land. It cannot guarantee simulator behavior or bypass Second Life permissions.