Getting Started
How /settings is organised, and what each area controls.
Settings are configured per Discord server. Run /settings in the server you want to change. Exact control labels can vary by version; this page describes the areas and what they are for without inventing parameter names.
/settingsOpen the per-server configuration surface./configInspect or work with configuration.Server-wide options that are not tied to a single module: whether Oxy is active in the guild, default locales or display choices if offered, and other baseline behaviour. Start here after a fresh invite.
Controls whether staff actions create cases, how case IDs are used, and where moderation results are written. Pair this with a log channel. See Moderation.
Per-server automatic enforcement: triggers, actions, bypasses, and whether AutoMod events create moderation cases. See AutoMod.
Choose channels for moderation, AutoMod, staff, tickets, applications, and other module logs. Oxy must be able to send messages in each selected channel. Do not point logs at a public chat if they include staff context.
Ticket categories, staff access, channel creation behaviour, and closing. See Tickets.
Which application forms exist, who may review them, and where submissions are logged. See Applications.
The suggestion channel, voting, staff responses, and status changes. See Suggestions.
Reaction role behaviour that is server-wide rather than panel-specific. Individual panels are still created with /reactionroles. See Reaction Roles.
Staff roles, additional roles, who may promote or demote, and staff audit logging. See Staff Management.
Store the Oxford server key and any connection options your version exposes. The key is a secret. See Oxford Response.
Whether shifts are required, whether Roblox verification is involved, and how records are stored. Periodic check timing is defined by the implementation — this page does not invent an interval. See Shifts.
Whether the server allows template installation, who may apply a template, and any confirmation behaviour. Installation still requires an explicit confirm step. See Templates.