Skip to main content
Documentation

Notifications & Nudges

Tabletop League keeps players informed automatically, and gives you a few deliberate tools to prod stragglers — without ever turning into a spam machine. This page covers what's sent automatically, how to dial it back per competition, and how to nudge players who've gone quiet.

The guiding principle: organizer controls drive consequences and reminders, never a "message everyone every day" firehose. You can quiet broadcast notifications and send bounded reminders, but you can never override a player's own notification preferences or raise the built-in rate limits.

Notification settings

Open Manage → Notifications. Below the notification log you'll find Notification settings — a per-channel on/off grid for the broadcast notifications your competition sends.

  • The switches are disable-only: turning a channel off stops your competition from sending that notification on that channel. They can never add reach, and they never override a player who has muted a channel in their own preferences. Think of it as a ceiling; each player's own settings are the floor.
  • Match-critical notifications are always delivered and never appear here: result verification, dispute and deletion alerts, round-deadline warnings, check-in reminders, and match nudges. A player can never be cut off from something they need to act on.

What you can currently toggle:

| Notification | Default channels | What it is | | ----------------- | ------------------------ | -------------------------------------------------------------- | | Round opened | In-app, push, Discord DM | Players are told a new round started and who they play | | Round halfway | In-app, push, Discord DM | A mid-round reminder to players with matches still outstanding |

More broadcast events (stream-live, ladder rank changes, milestones) will join this grid as they're wired up; until then they deliver on their default channels.

Nudging players

When a specific match has gone quiet, you can send a one-off reminder. Open the Matches tab, find the match, and use its row action menu (…):

  • Nudge players directly — sends the reminder through each player's normal channels (in-app, push, email, Discord DM), respecting their preferences.
  • Nudge in Discord thread — posts the reminder into a private Discord thread for that match instead of DMing (see Private Discord threads below).

A nudge is also one of the actions available on each entry in the Resolution Queue.

Rate limit: any single match can be nudged at most once every 12 hours, no matter how you trigger it. This cap is platform-owned — you can't shorten it. It's what keeps "nudge" from becoming the daily-harassment lever this design deliberately avoids.

Bulk nudge

To chase a whole batch of stragglers at once, use the Nudge players button at the top of the Matches tab:

  • Nudge unscheduled matches — every incomplete match that has no agreed time yet.
  • Nudge all incomplete matches — every match that hasn't been completed.

The nudge is scoped to whatever stage and round filters you have active on the table, so you can target "everyone still outstanding in Round 3." A confirmation dialog names the scope before anything is sent.

The same 12-hour per-match cap applies, so any match nudged recently is skipped automatically — re-running later picks up where it left off. Each run sends up to 50 nudges; if more remain, the toast tells you to run it again.

Private Discord threads

Thread-mode nudges keep coordination in a shared, organizer-visible space instead of scattered DMs. When you nudge a match in a Discord thread, the bot opens (or reuses) a thread for that match and posts the reminder there.

Set it up under Settings → Discord Threads:

  • Thread parent channel — the Discord text channel threads are created under. Enter the channel's ID (enable Developer Mode in Discord, then right-click the channel → Copy Channel ID). Leave it blank to fall back to the match's group channel when one is linked.
  • Thread visibility:
    • Private (default) — only the two match players and you (the organizer who nudged) are added to the thread. Nobody else in the server sees it.
    • Public — the thread is visible to everyone who can see the parent channel.

Graceful fallback: if no parent channel resolves, or none of the match's players have linked their Discord account, thread mode quietly falls back to a direct nudge so the reminder still lands. In-app and push copies are always sent alongside the thread, so a player without Discord still gets the message.

Threads are created on first use and reused after that. Discord auto-archives an idle thread after 7 days; a new nudge reopens it.

How this relates to other notifications

  • Announcements (the Updates tab on your public page) are a separate, manual broadcast with their own per-post channel picker — see Posting Updates.
  • Players control their own delivery in their account settings. Your notification settings can only narrow what your competition sends; they can't reach past a player's opt-out. See Notification preferences (player docs).
  • Round-deadline handling — the resolution queue, deadline grace period, and forfeit/dismiss verbs live in Managing Events → Resolution Queue.