First Server Configuration

Use a small, understandable configuration first. A successful login or green status indicator does not validate every server feature.

Checklist

1. Confirm the selected server name and Fork’s presence.
2. Review the command-role policy. Keep sensitive commands limited to the intended staff roles.
3. Enable one AI channel and choose its response mode/cooldown.
4. Add only non-sensitive, current information to the server FAQ.
5. Enable only the AI tools your community actually needs.
6. Check a harmless response and inspect the saved settings again.

Before structural changes

Use Server Manager to draft channel and role changes. Review the exact resource names, inheritance and role visibility before approving. A “private” name does not create a private permission boundary by itself.

Keep a useful record

Record which settings you intentionally enabled, without copying secrets or session data. After a role change, recheck effective permissions. After a failed mutation, inspect its outcome before repeating it. Audit logs can help distinguish configuration writes from moderation records and actual Discord state.