Skip to content

Screening join requests

LogDog can screen every new join request automatically against rules you set: flagging suspicious requesters for your mods, or denying them outright before anyone has to look. Configure it with /screening in Discord or on the dashboard's Settings → Request screening card; both edit the same rules.

Flag first

Every rule has two severities. Flag adds a warning section to the join-request log listing exactly which checks failed; your mods still decide. Auto-deny answers for you. Most groups should run new rules as flags for a week or two before trusting them with auto-deny.

The rules

Rule What it checks
Account age The requester's VRChat account is younger than a number of days you pick. The classic throwaway-alt filter.
Trust rank Their VRChat trust rank is below a minimum you pick (Visitor up to Trusted User). Accounts VRChat itself flags as a nuisance fail any minimum.
Age verification Their verification state isn't one you accept; you choose which of Verified 18+ / Verified / Hidden / Not verified pass. Optionally, a bio statement counts: if their bio contains a phrase you set (like 18+), that passes the check too.
Group history This group has banned them before, or denied a previous request, both read from your group's own audit history.
Blocked keywords Their display name, bio, or status text contains a word from your list.

Each rule is independent: set the ones you want, leave the rest off, and give each its own severity.

What your mods see

A flagged request is the normal join-request log with one extra section:

Screening: 2 checks failed • Account younger than 30 days (7 days old) • Age verification not accepted (Hidden)

The Approve / Deny buttons work exactly as always; the flags are information, not a decision. See Approving join requests for the buttons.

An auto-denied request posts as a record instead: it shows which rule fired (plus any other failed checks), and carries no buttons because the denial has already been queued. It lands in your moderation history like any deny, credited to LogDog screening. If VRChat refuses the queued denial, the record corrects itself: the auto-denied note is removed, and when a retry could work (a permission problem, say) the Approve / Deny buttons come back for your mods. If the user requests again later, the new request is screened fresh (a requester your mods are still mid-action on is flagged rather than auto-denied, so nothing fights your staff).

Unverifiable never means denied

If LogDog can't check something, a profile it couldn't fetch or data VRChat didn't send, that rule can only flag ("Couldn't verify account age (profile unavailable)"), never auto-deny. Auto-deny requires a check that positively failed on real data.

Setting it up

With /screening (administrator-only):

  • /screening view: see every rule as currently configured.
  • /screening toggle: turn screening on or off; your rules are kept while paused.
  • /screening account_age <min_days> <severity>: 0 days turns the rule off.
  • /screening trust_rank <minimum> <severity>
  • /screening age_verification <accept> <severity> [bio_phrases]: <accept> picks a preset (Verified 18+ only / Verified 18+ or Hidden / Any verified (18+ or identity) / Off); the dashboard offers the full four-state checkbox picker. bio_phrases is a comma-separated list that counts as passing when found in the requester's bio.
  • /screening history <previously_banned> <previously_denied>: each Off / Flag / Auto-deny.
  • /screening keywords <keywords> <severity>: a comma-separated list; it replaces the stored list, and an empty list turns the rule off.

Or open the dashboard's Settings page: the Request screening card offers the same rules with the full checkbox picker for verification states.

Screening rides your request logs

Rules run when a join-request event is delivered, so Group Join Request events must be routed to a channel. If they aren't, both /screening view and the dashboard card warn you; fix the routing with /config or the dashboard's Routing page. And like manual responses, auto-deny needs the LogDog account to have Manage Group Invites (see Approving join requests).

Free and Premium

Flag severity, and up to 3 blocked keywords, are free for every server. Premium unlocks auto-deny severity and raises the keyword list to 15. If Premium lapses, stored auto-deny rules keep their setting but act as flags until it returns.