Skip to guide
NightCrew Docs

Documentation›Security›Advanced Logging

Security

Advanced Logging

Send Discord changes to configurable log channels.

Updated October 21, 20262 min read

Getting started

1

Create log channels

Create private destinations for the groups you want to retain.

2

Apply a preset

Start with Balanced, Security, Minimal, or Full Audit, then tune individual events.

3

Choose destinations

Select category defaults and override individual events when one needs a dedicated channel.

4

Verify delivery

Send a destination test and review Permission Scanner before relying on a route.

5

Set evidence policy

Choose retention, duplicate suppression, privacy redactions, retries, filters, and critical alerts.

6

Investigate

Filter the log by member or channel, open an event for details, or export the results as CSV or JSON. New role permission events list each changed permission as Enabled → Disabled or Disabled → Enabled. Channel and category overrides show Allowed, Denied, or Inherited before and after; raw permission numbers are not displayed.

7

Connect security tools

Optionally forward signed JSON events to an HTTPS webhook or SIEM endpoint.

8

Enable audit access

Give NightCrew View Audit Log so embeds identify the administrator or moderator responsible.

Settings reference

Use this reference when you need to check what a setting does.

Message logs

Edits and deletions, including cached content when available.

Member logs

Joins, leaves, nickname changes, and member-role changes.

Moderation logs

Kicks, bans, unbans, and timeouts.

Server logs

Channel creation, edits, and deletion.

Role logs

Role creation, permission/name changes, and deletion.

Voice logs

Joins, moves, and leaves.

Group channel

Destination selected independently for each category.

How it works

Here’s what happens once you’ve finished setup.

  1. 1
    Discord event

    NightCrew receives the before/after event.

  2. 2
    Audit lookup

    For administrative actions, it requests the closest matching audit entry.

  3. 3
    Embed

    Posts the specific changes, affected role or channel, context, and actor footer to the configured destination. Permission changes use readable names and before/after states instead of raw permission numbers. Large channel permission changes continue across messages.

Example

EXAMPLE
Organized logs

Use #message-log, #member-log, #mod-log, and #server-log; send Role and Voice into #server-log if you want fewer channels.

Permissions

!
What NightCrew needs
  • View Audit Log
  • View Channels
  • Send Messages
  • Embed Links
  • Read Message History

Troubleshooting

Deleted content is missing

Discord does not provide uncached message text; ensure Message Content intent and Read Message History are enabled.

No actor footer

Grant View Audit Log and allow a few seconds for Discord audit propagation.

Logs loop

Ignore dedicated log channels if message-edit logging reacts to webhook or bot edits.

Common questions

Footer says unknown+

NightCrew lacks View Audit Log or Discord has not produced the matching entry yet.

Destination shows untested+

Run Send test for that channel; a successful delivery changes it to Delivered.

Deleted content is missing+

Discord can only provide cached content; enable Message Content intent and Read Message History.