What members need in Discord

CoGM posts signups, LFG groups, auctions and panels in your Discord channels. This page says what a role, or @everyone, needs in each channel to use them, and what CoGM decides on its own.

Seeing and pressing CoGM's posts

View Channel lets a member see the channel. Read Message History lets them see posts made before they opened it. Without it, an older CoGM post stays hidden.

Buttons and menus need nothing more. Members can press Attending, Join or Bid in a channel where they can't type, so a read-only channel works for signups, LFG, auctions and similar posts.

Typing CoGM's commands

Discord lets a member run a bot's slash command only in a channel where they have both Use Application Commands and Send Messages. Missing either, CoGM's commands don't show in the / menu there.

Admins can also limit CoGM's commands by role, member or channel in Server Settings > Integrations > CoGM. Members with Administrator can always use every command.

If you set Command Channels (community Settings > Discord Servers > Command Channels), CoGM answers typed commands only in the listed channels. A channel routed to a guild follows that guild's list. Buttons work in every channel.

Tickets and threads

A ticket opens as a private thread in the ticket channel. Send Messages does not carry into threads, so members need Send Messages in Threads in that channel to write in their ticket.

What each channel needs

Channel	Members need	Why
Event signups, LFG, absences, loot auctions, polls	View Channel, Read Message History	They press buttons and menus
Upload channel and Command Channels	View Channel, Read Message History, Use Application Commands, Send Messages	They type commands
Ticket channel	View Channel, Read Message History, Send Messages in Threads	They write in their ticket thread

Seeing a post is not signing up

Discord permissions decide what people can see. CoGM decides who can use its posts. Event signups and LFG groups take people on your roster and anyone with the guild's member role, picked in guild Settings > Discord > Discord Role Mapping. Loot auctions take bids from the roster.

Someone with the member role joins the roster when they get the role, or the first time they press a signup or LFG button. Anyone else who presses Attending gets a private reply: "To sign up for your guild's events you need the @Member role in this server. Ask an officer for it, then click the button again." If the guild is recruiting with an active form, the reply adds "New here? You can also apply to join." and an Apply to join button.

An event's Required Role limits signups for that one event to members with that role.

These work for anyone in the server, on the roster or not: the Apply button and /apply, reaction role panels, Gate Keeper verification, and voting in polls.

Guests and pugs

There are three ways to bring a guest or a pug to your events:

Give them the member role. They join the roster when they get it.
Have them apply. Approving the application puts them on the roster.
Add them as a guest seat with Add guest in the event's party builder. A guest seat is a name only, with no account.

Setting the member role to your pug role makes every pug a roster member.

Keep your application review channel hidden from applicants. Each application is a thread that anyone who can see that channel can read.

Check a role

Guild Settings > Discord > Role access check lists the channels CoGM uses for the guild and says what a role, or @everyone, is missing.

More on the member role and applications: Get Your Members In.