Discord Moderation Guide: Difference between revisions

From DisNCord Community Wiki
Jump to navigation Jump to search
mNo edit summary
Line 27: Line 27:


== Actions ==
== Actions ==
Moderators on DisNCord can take various actions in regards to tickets and incidents. Actions, unless noted, should be done through either Tickets or YAGPDB as is necessary.
=== Note ===
Sometimes a ticket comes in, or a borderline action is witnessed, that warrants an official comment from a moderator, but doesn't reach the point that an actual warning should be raised.
In these cases, a ticket should be opened by the moderator, and pull in any relevant offending users. If a moderator is acting on another ticket, the reporter should not be pulled in. Exposing a reporter of an issue opens them up to retaliation; a moderator speaking in a ticket is speaking on behalf of the server. Any relevant conversation should be held, and then the moderator should close ticket should be closed with a comment explaining why no action was taken. The log will be saved.
These actions represent "we talked to someone about X", and will essentially be forgotten if the issue doesn't come up again


=== Warnings ===
=== Warnings ===


=== Timeouts ===
=== Timeouts/Mutes ===


=== Kicks ===
=== Kicks ===


=== Bans ===
=== Bans ===

Revision as of 16:18, 5 January 2023

DisNCord uses a large set of moderation tools, and guidelines to ease the burden of server administration. The intent is to make moderation quick and easy to review, while still being able to handle large scale raids and other server events are handled. At the moment, this document only covers the Discord server, but should probably be expanded in time to cover YouTube, Fediverse, and this wiki.

Workflow

Moderator Permissions

Volunteers and Active Users

Half-Ops

Channel/Project Manager

Server Moderator

Bot Wrangler

Server Administrator

Founder/Owner

Bots

YAGPDB.yxz

Tickets

Actions

Moderators on DisNCord can take various actions in regards to tickets and incidents. Actions, unless noted, should be done through either Tickets or YAGPDB as is necessary.

Note

Sometimes a ticket comes in, or a borderline action is witnessed, that warrants an official comment from a moderator, but doesn't reach the point that an actual warning should be raised.

In these cases, a ticket should be opened by the moderator, and pull in any relevant offending users. If a moderator is acting on another ticket, the reporter should not be pulled in. Exposing a reporter of an issue opens them up to retaliation; a moderator speaking in a ticket is speaking on behalf of the server. Any relevant conversation should be held, and then the moderator should close ticket should be closed with a comment explaining why no action was taken. The log will be saved.

These actions represent "we talked to someone about X", and will essentially be forgotten if the issue doesn't come up again

Warnings

Timeouts/Mutes

Kicks

Bans