Skip to main content
Venon Security slash commands
What is the /report-config slash command for in Venon Security for Discord?
/report-config belongs to the administration category and is part of the Zgconfig module. An administrator or a moderator reaches for it when the action has to be fast, fully traceable in the logs and in line with Discord's permissions.
Administration
Category
Manage Guild
Permissions
4
Subcommands
What it does
What is the /report-config command for?
Report settings: card channel, team and automatic assignment
When to use it
Reach for /report-config when you need a repeatable administrative action without clicking through Discord's settings by hand. Venon Security watches the syntax, the permissions and the context, and the execution can later be tied to the moderation logs or the module's configuration.
Required permissions
The command requires the scope: Manage Guild. If Discord rejects the action, check the bot role's position in the hierarchy, the permissions on the channel and whether the module is enabled in the dashboard.
Syntax
Syntax of the /report-config command
Format
/report-config show · /report-config channel · /report-config team · /report-config auto-assignAngle brackets mark required parameters, square brackets optional ones. In slash commands Discord suggests the fields for you, so it is best to fill them straight from the suggestion list.
Example usage
/report-config showTreat the example as a template. Swap the member, channel, role, reason or duration for the real situation on your server.
Parameters
Command parameters
/report-config show
Show the report settings and their status
/report-config show/report-config channel
Channel where cards for new reports are posted
/report-config channel channel:#channel/report-config team
Add or remove a role of the team handling reports
/report-config team action:add role:@role/report-config auto-assign
Oldest case for a moderator who just came online on the server
/report-config auto-assign enable:yesProblems
The most common problems
Missing permissions
Check whether the member and the bot both hold the required scope: Manage Guild.
Role hierarchy
For actions on members, the bot's role has to sit above the target's role.
Module disabled
If the command depends on a module, enable it in the dashboard and check the channel configuration.
Ready?
Add Venon Security and use /report-config with the full context
Slash commands work best alongside the dashboard, the logs and the protection modules. Add the bot to your server, read the documentation and set up your team's permissions.