Documentation
Back to tutorials

Setup

Configuration: Channels, Roles, and Permissions

Configure the Settings page so GearCheck knows where to operate, who can manage it, and which roles/channels power each workflow.

Who uses it

Guild owners and managers

Where it lives

Dashboard > Settings and Dashboard > Setup

Goal

A guild where staff permissions, gearcheck channels, support/audit destinations, language, and module settings are understandable.

Before You Start

  • Manage Server or GearCheck manager access.
  • Discord roles/channels created for your desired workflow.
  • Bot role placed above assignable roles.

Steps

1

Start with staff access

Managers, assistants, and moderators should map to the people who actually operate GearCheck. Use roles for groups and user principals for exceptions where supported.

2

Configure channels by workflow

GearCheck channels are for member verification threads. Support channels are for tickets. Audit channels are for history. Notification channels are for rule-driven alerts. Avoid reusing one channel for every purpose unless your server is tiny.

3

Configure roles carefully

Verified roles, activity roles, role gates, moderator roles, and staff roles each do different jobs. Discord hierarchy still applies: the bot cannot assign roles above its own role.

4

Set language and evidence defaults

Dashboard, bot, game-data, and OCR language settings can be different. Evidence defaults should match the game and pack your members will actually use.

5

Re-run setup checks after changes

After Discord channel or role cleanup, revisit Settings or Setup. Deleted channels, renamed roles, and hierarchy changes are common causes of broken workflows.

Launch Checklist

  • Bot can read/send/manage threads in GearCheck channels.
  • Bot role is above roles it assigns.
  • Staff can access the pages they are expected to operate.
  • Support/audit/notification destinations are still reachable.

Common Pitfalls

  • Assuming Discord Administrator and GearCheck manager are the same thing.
  • Letting old channel IDs remain configured after Discord cleanup.
  • Giving broad staff access because a single person needs one permission.

Related