Bot Protection and visitor blocks

Open Bot Protection to manage the default response and inspect activity. Bot protection complements admission rules and checkout validation; it does not guarantee that every unwanted visitor is identified.

Choose a response

Mode	Shopper behavior
Monitor only	Signed sessions, rate limits, and checkout validation remain; no shopper challenge
Low friction	Challenge access-code and other priority joins; ordinary joins use baseline rate limits
Balanced	Verify fresh sessions while trusted reconnects can continue without another challenge
Strict	Verify new and returning sessions before protected access

1. Review the current Store default and its description.
2. Select the intended mode and choose Save default.
3. Reopen the page and verify the saved mode.
4. Test the ordinary and priority shopper journeys you support.

Monitor only is not an emergency bypass. Turning off challenges does not remove the remaining checks.

Override one room

In Waiting Room overrides, choose the room’s Response and save. Use store default removes the custom choice and follows the store setting. A room override also applies to its linked waiting list; standalone lists use the store default.

Review visitor activity

1. In Protection console, choose Waiting Rooms or Waiting Lists.
2. Select the relevant room/list where offered.
3. Review challenge outcomes, attempts, rate limits, recent activity, and existing blocks.
4. Open a visitor’s details and read Why this score before deciding what to do.

Low, Review, and High are review signals, not proof of identity or misconduct. Empty activity can mean no recorded sessions; it is not a passed live test.

Apply or remove a block

For a room visitor, choose the Block scope: the session’s future queue access or the shared network. Choose a duration and optional internal reason, then Apply block. For list activity, Block network for this list affects future signups for that list. Review active blocks and use the offered removal action when the block is no longer appropriate.

Network blocks can affect multiple shoppers behind a household, office, or mobile carrier. Prefer the narrower scope when it addresses the problem. A room block does not cancel a checkout pass already issued; that pass follows its admission expiry.

If a legitimate shopper cannot pass

Check the relevant room override, challenge result, existing blocks, and the shopper’s visible error. Use any offered read-only preflight check to inspect configuration; it does not create a shopper session or prove an end-to-end launch. Avoid broadly weakening protection to resolve one unexplained failure. Escalate with the room/list, time, and redacted error.