Skip to content
Tutorials

Discord and Web: Which Workflow Fits?

Decide when to use Discord commands, Discord threads, dashboard pages, exports, Web Inbox, and notifications.

Start Here
Who uses it
Owners, moderators, build editors, members
Where it lives
Discord and the GearCheck dashboard
Goal
Staff and members know which surface to use for each job instead of fighting the wrong tool.
On This Page5 sections

Before You Start

  • A guild with GearCheck installed.
  • At least one staff member with dashboard access.
  • Members who primarily interact through Discord.

Steps

  1. Use Discord for member actions

    Normal members usually live in Discord. Build selection, evidence submission, support tickets, and personal notification opt-in/out should stay easy from Discord.

  2. Use the dashboard for staff operations

    Build editing, review queue triage, analytics, notifications, settings, stored data, bot messages, server emojis, and bot status are dashboard workflows because they need space, filters, and context.

  3. Use both for review and support

    A staff member may start from a Discord thread, jump to the dashboard gear check detail, then return to Discord to follow up with the member. Good links make this normal, not awkward.

  4. Use exports when data leaves GearCheck

    CSV/JSON exports are for spreadsheets, handoffs, audits, and external planning. Do not use screenshots of dashboard tables when an export exists.

Check It Worked

  • Members can complete their flow without dashboard access.
  • Staff can jump from alerts to the relevant dashboard page.
  • Dashboard-only configuration is documented before staff need it.
  • Exports are used for external workflows instead of copy/paste.

Common Pitfalls

  • Expecting normal members to use the staff dashboard.
  • Trying to configure complex notification or build rules through Discord commands.
  • Keeping important staff decisions only in a Discord chat with no dashboard/audit trail.