Report a member
Ordinary members can use/report user or their server’s member portal. Include a clear reason of 10–2,000 characters and up to three HTTPS evidence links. Evidence pages are not fetched automatically by the bot.
Reports are private to their author and authorized reviewers. New reports are limited per author/server, including three per hour and ten per day, and duplicate open reports about the same target are restricted.
Use /report status or /servers/{guild_id}/reports to follow your own report. Eligible reports can be withdrawn through the website.
Review reports
Reviewers open/dashboard/{guild_id}/reports. Reading, reviewing, accepting, rejecting and assigning reports use separate AEGIS permissions. Record a reason for your decision. The report’s author or target cannot decide it.
Accepting a report awards its author once, subject to scoring limits. Acceptance does not itself punish the reported member. See Contribution points.
Apply a punishment
Use/punish user, select an active server rule, enter the reason and choose the action. The chosen action requires its corresponding AEGIS permission. Current staff rank and Discord hierarchy must allow the action against that member.
Ban requests are sent for the actual current owner’s decision. Only an approved request proceeds to execution. Ownership or access changes can stop execution.
/punish warn records a rule-based warning and attempts a DM notification. DM delivery is best-effort: a blocked DM does not automatically reverse a recorded decision or a confirmed action.
Correct a record
/punish revoke-record revokes the punishment record and its contribution eligibility. It does not undo a Discord ban or timeout. Reverse those Discord restrictions separately through an authorized operation.
If Discord did not confirm an action, check the member and audit log before submitting another request. A lost API response can leave an uncertain outcome.