Docs

Nox Documentation

10 things to know about Nox

The essentials worth knowing before you configure anything.

Nox does not request message content

Commands and configured interactions use Discord application commands, buttons, and modals instead of reading member message text.

Features are configured from the dashboard

Features start disabled. You choose the channels, roles, schedules, and messages each enabled feature should use.

Commands respect Discord permissions

Slash commands have default member permissions, and server admins can adjust access in Discord's integration settings.

Every permission is accounted for

Each Discord permission the invite requests is documented, along with which feature relies on it and why.

Activity history keeps a rolling year

Dashboard logs and insights use a rolling 365-day activity window. Older activity entries are deleted automatically.

Members own their profiles

Levels, currency, and birthdays are member-scoped. A member's profile is deleted when they leave your server.

Bot removal has a grace window

After Nox leaves a server, there is a seven-day grace window before the full wipe. Re-inviting during that window restores the existing configuration.

Members can see the feed and calendar

The community activity feed and the events calendar on the dashboard are visible to members, not just staff.

Scheduled features use shared controls

Events, posts, timers, giveaways, and polls all run on schedules, including recurring series with exclusions and end dates.

Errors and health checks are visible

The Errors page records feature failures, and the settings health check flags common channel, role, and permission problems.

The features that give a new community the most value quickly.

Great commands to start with

Member-facing commands that work as soon as their feature is enabled.