---
title: 'Server Settings'
slug: 'server-settings'
category: 'Servers'
order: 12
description: 'Master reference for every CADLY settings tab and setting.'
---

# 1 - Introduction

Server Settings control CADLY's identity, roles, permissions, feature modules, ER:LC integration, dispatch, departments, and dangerous owner-only actions.

Settings are saved per Discord server. Some advanced areas, such as sessions, deployments, ER:LC restrictions, and reminders, have their own dedicated settings and management screens.

Most setup problems come from settings being configured in the wrong order. A good setup path is: choose server type, configure general identity, create CADLY roles, assign permissions, connect ER:LC if needed, then enable feature modules one at a time.

Avoid changing many high-impact settings at once on a live server. Save, test the feature as a normal staff member, then continue. This catches missing Discord role hierarchy, channel permissions, and server-slot permission mistakes early.

```cadly-mock
type: setting
title: Server configuration overview
meta: Settings > Server A
status: Draft saved
items:
- Server Name | River City Roleplay
- Server Mode | Host server
- ER:LC Integration | Enabled
- Dispatch | Enabled
```

## 1.1 - Table of Contents

| Section                                               | What it covers                                             |
| ----------------------------------------------------- | ---------------------------------------------------------- |
| [General Settings](#2---general-settings)             | Server name, type, theme, bot profile, server-slot mode    |
| [Role Settings](#3---role-settings)                   | CADLY roles and permissions                                |
| [Feature Settings](#4---feature-settings)             | Verification, shifts, logs, LOA, ER:LC, dispatch, and more |
| [Dangerous Settings](#5---dangerous-settings)         | Disable, reset, delete, and change type                    |
| [Troubleshooting](#6---troubleshooting-common-issues) | Common settings problems                                   |

# 2 - General Settings

## 2.1 - Basic Configuration

### Server Name

Display name for your server.
**Default:** blank | **Requires:** none

### Short Name

Abbreviation or acronym, max 10 characters.
**Default:** blank | **Requires:** none

### Description

Brief server description, max 500 characters.
**Default:** blank | **Requires:** none

### Bot Prefix

Custom prefix for prefix-style bot commands, max 5 characters.
**Default:** `!` | **Requires:** none

### Theme Color

Primary panel theme color.
**Default:** `#3498db` | **Requires:** none

### Server Mode

Controls whether this guild is a Host Server or Department Server.
**Default:** department until setup completes | **Requires:** owner after setup

This setting controls feature availability. Host Servers get sessions and department management; Department Servers get deployment-focused workflows. Review [Host vs Department Servers](/docs/server-types) before changing it.

### Mono Server Mode

Located at the bottom of **Settings > General**. On means only Server A is active. Off enables Server A and Server B across ER:LC keys, role assignments, logs, dispatch, and ER:LC permissions.
**Default:** on | **Requires:** none

## 2.2 - Bot Customization

### Bot Profile Customization

Custom bot nickname and avatar controls are available from the Bot Profile settings area.
**Default:** CADLY default bot profile | **Requires:** Server PRO for custom profile

## 2.3 - CAD Settings

### Custom Buttons

Adds CAD panel buttons. Types include URL, remote command, preset command, and text holder.
**Default:** none | **Requires:** none; higher limits may require PRO

Use custom buttons for repeated actions staff need during active operations. Avoid creating buttons for rare actions because crowded panels slow staff down.

### Event Log

Controls which action engine event types appear in the CAD feed.
**Default:** common player, command, kill, mod call, zone, and restriction events | **Requires:** none

### Chat Module

Turns CAD chat on or off.
**Default:** on | **Requires:** none

### Slowmode

Seconds between chat messages for regular users. Owners and admins bypass it.
**Default:** 0 | **Requires:** none

### Blocked Words

Words blocked in CAD chat.
**Default:** none | **Requires:** none

### Chat Presets

Reusable chat snippets with optional hotkeys.
**Default:** none | **Requires:** none

### Chat Placement

Controls where chat appears in the CAD layout.
**Default:** middle bottom | **Requires:** none

### Chat Logging

Channel for CAD chat messages and moderation events.
**Default:** none | **Requires:** none

# 3 - Role Settings

## 3.1 - Permission Roles

### CADLY Roles

CADLY roles map Discord roles to CADLY permissions. Each role has a Discord role, name, order, optional color, and permission set.
**Default:** none | **Requires:** none

CADLY roles do not replace Discord roles. They interpret Discord roles into CADLY permissions. If a member has several mapped roles, CADLY resolves the effective permissions from those mappings and built-in owner/admin checks.

### Role Permissions

Permissions include server view, CAD view, ER:LC command tiers, shifts, logs, LOA, promotions, infractions, applications, settings, dispatch, departments, User PRO, and Server PRO.
**Default:** all false until assigned | **Requires:** none

Start with least privilege. Give ordinary staff view and create permissions for the tools they use, then reserve manage, delete, settings, departments, and ER:LC owner-tier commands for leadership.

## 3.2 - Staff Roles

### Shift Type Allowed Roles

Each shift type can limit who can start that shift type.
**Default:** empty means all eligible users | **Requires:** none

### Log Type Allowed Roles

Each log type can limit which roles can create that log type.
**Default:** empty means all users with create permission | **Requires:** none

# 4 - Feature Settings

## 4.1 - Verification Settings

### Enable Verification

Turns verification on or off.
**Default:** off | **Requires:** none

### Verified Role

Role added after successful verification.
**Default:** none | **Requires:** none

### Unverified Role

Role removed after successful verification.
**Default:** none | **Requires:** none

### On Join Role

Optional role used during join handling.
**Default:** none | **Requires:** none

### Auto Verification

Automatically applies verification state for already-linked members on join.
**Default:** on | **Requires:** none

This reduces repeated onboarding for returning members. Disable it only if every join should be manually reviewed.

### Username Template

Nickname format after verification.
**Default:** `{roblox_username}` | **Requires:** none

### Alt Account Detection

Device-fingerprint alt matching (on verify) and a Discord account risk score (on join). See [Verification → Account Safety](/docs/verification#account-safety) for how each check works.
**Default:** Nothing / Nothing | **Requires:** an alert channel once either action is set

## 4.2 - Shift Settings

### Enable Shifts

Toggles the shifts module.
**Default:** on | **Requires:** none

### Shift Types

Configures shift types, allowed roles, and max on-duty counts.
**Default:** Default Shift, unlimited | **Requires:** none

### Staff Request Channel

Channel where staff requests are posted.
**Default:** none | **Requires:** none

### Staff Request Ping

Optional role pinged by staff requests.
**Default:** none | **Requires:** none

### Staff Request Cooldown

Minimum minutes between requests per user.
**Default:** 30 | **Requires:** none

### On-Duty and On-Break Roles

Roles assigned for active and break states on Server A and Server B.
**Default:** none | **Requires:** none

### Shift Waves

Controls wave duration, requirement mode, required hours, enforcement action, new-member grace, LOA skip, and wave log channel.
**Default:** enabled, manual duration, per-role requirements, manual enforcement, skip new members and LOA | **Requires:** none

Configure LOA before enforcing shift waves. Otherwise legitimate leave may be counted as missed duty time.

## 4.3 - LOA Settings

### Enable LOA

Toggles the LOA module.
**Default:** on | **Requires:** none

### Allow Future Requests

Allows planned LOAs.
**Default:** on | **Requires:** none

### Max Future Days

Maximum days in advance an LOA can start.
**Default:** 30 | **Requires:** none

### Minimum and Maximum Length

Configured LOA duration bounds.
**Default:** 1 to 30 days in settings; CADLY currently accepts requests up to 14 days | **Requires:** none

### Cooldown

Days between LOA requests.
**Default:** 0 | **Requires:** none

### Reason Required

Requires LOA reasons.
**Default:** on | **Requires:** none

### LOA Logging

Channel for LOA events.
**Default:** none | **Requires:** none

### LOA Role

Role assigned during active LOA.
**Default:** none | **Requires:** none

## 4.4 - Promotions Settings

### Enable Promotions

Toggles promotion records and commands.
**Default:** on | **Requires:** none

### Promotions Channel

Channel for promotion logs.
**Default:** none | **Requires:** none

### Revoke Behavior

Controls role changes when a promotion is revoked.
**Default:** none | **Requires:** none

### Hierarchy Block Policy

Controls fail versus confirm partial when hierarchy blocks role changes.
**Default:** confirm partial | **Requires:** none

## 4.5 - Infractions Settings

### Enable Infractions

Toggles infractions.
**Default:** on | **Requires:** none

### Log Channel

Channel for infraction logs.
**Default:** none | **Requires:** none

### Warning Expiry and Strike Expiry

Days until active warnings or strikes expire. `0` means never.
**Default:** 0 | **Requires:** none

Expiry changes active discipline counts, not history. Expired records remain available for audit.

### Default Suspension Duration

Default suspension length in days.
**Default:** 1 | **Requires:** none

### Suspension Stacking

Controls whether suspensions stack or reset.
**Default:** stack | **Requires:** none

### Tier Role Stacking

Controls whether multiple tier roles remain at once.
**Default:** off | **Requires:** none

### Tier Roles

Roles for warning tiers, strike tiers, suspended state, and termination.
**Default:** none | **Requires:** none

## 4.6 - Logs Settings

### Enable Logs

Toggles incident logging.
**Default:** on | **Requires:** none

### Logging Channels

Channel where logs are posted.
**Default:** none | **Requires:** none

### Log Types

Configures type name, description, allowed roles, BOLO status, color, location mode, custom fields, and user DM.
**Default:** Note, Roleplay Log, Warning, Kick, Ban BOLO, Ban | **Requires:** none

Keep your log type list small enough that staff can choose quickly. Add custom fields only for information you consistently need.

## 4.7 - ER:LC Settings

### Enable ER:LC

Turns on ER:LC data panels.
**Default:** off | **Requires:** none

### API Keys

Encrypted ER:LC keys for Server A and Server B.
**Default:** none | **Requires:** none

### Feedback Channel

Channel for ER:LC notifications.
**Default:** none | **Requires:** none

### Bloxlink Integration

Saves the Bloxlink key and controls automatic Roblox-to-Discord matching. Only required when
Verification is disabled - verified accounts already resolve players without it.
**Default:** not configured, auto-convert on | **Requires:** Verification enabled, or a Bloxlink key

### Discord Reminder PMs

Periodically PMs in-game players who are not in your Discord, grouped as `:pm user1,user2,... {message}`
(10 per message). Skips staff and anyone whose Discord membership cannot be confirmed. Per A/B slot,
every 10-30 minutes (PRO: from 5).
**Default:** off | **Requires:** Verification enabled, or a Bloxlink key

### Welcome Message

Sends a message to players when they join.
**Default:** off | **Requires:** none

### Log Webhook Processing

Processes ER:LC `:log` webhook messages.
**Default:** off | **Requires:** none

### Off-Duty Detection

Detects off-duty command usage and punishes, warns, or pings HR.
**Default:** off | **Requires:** none

### Restrictions, Limits, Reminders, and Action Engine

Vehicle restrictions, livery restrictions, team limits, role restrictions, play zones, reminders, permission sync, and action rules are managed from the ER:LC settings area.
**Default:** none | **Requires:** PRO for some higher caps and permission sync

These settings can affect live players. Test detection-only or logging workflows before adding automatic kicks, bans, or other in-game commands.

## 4.8 - Sessions Settings

### Sessions Module

Toggles sessions for Host Servers.
**Default:** on | **Requires:** Host Server

### Session Channel

Channel for session vote, startup, full, low player, and shutdown posts.
**Default:** none | **Requires:** Host Server

### Action Cooldown

Minimum seconds before repeating the same session action.
**Default:** normalized to safe minimums | **Requires:** none

### Resume Window

Seconds a stopped session remains resumable.
**Default:** feature default | **Requires:** none

### Vote Defaults

Required votes, auto-start window, auto-run SSU, and show voters button.
**Default:** no required votes, no deadline | **Requires:** none

### PlayerGuard

Runs per-player actions and optional PM messages during sessions.
**Default:** off | **Requires:** none

## 4.9 - Deployments Settings

### Deployments Module

Toggles deployments for Department Servers.
**Default:** on | **Requires:** Department Server

### Profiles

Deployment profiles define channel, ping roles, messages, vote settings, and analytics behavior.
**Default:** none | **Requires:** PRO for higher profile caps

## 4.10 - Dispatch Settings

```cadly-mock
type: setting
title: Dispatch behavior
meta: Settings > Dispatch
status: Server A
items:
- Default Priority | medium
- Require Postal Code | On
- DM on Assign | On
- PM on Assign | On
```

### Enable Dispatch

Turns dispatch features on or off.
**Default:** on | **Requires:** none

### Require Roblox Link

Requires dispatch users to have a linked Roblox account.
**Default:** on | **Requires:** none

### Sync In-Game Calls

Creates dispatch calls from ER:LC emergency calls.
**Default:** on | **Requires:** ER:LC key

### Auto-Complete Idle Calls

Auto-completes calls after configured idle minutes.
**Default:** on, 5 minutes | **Requires:** none

### Default Call Priority and Type

Pre-selected values for new calls.
**Default:** medium, standard | **Requires:** none

### Max Units Per Call

Maximum assigned units. `0` means unlimited.
**Default:** 0 | **Requires:** none

### Require Description and Postal Code

Makes those fields mandatory when creating a call.
**Default:** off | **Requires:** none

### Notifications

Panic call, high priority call, call completed, and unit status change notifications each support channel, ping role, and custom message.
**Default:** no channels | **Requires:** none

Use separate channels for high-noise and high-urgency notifications if your server is busy. Panic calls deserve a different channel or ping than routine unit status changes.

### Unit Behavior

Hide off-duty units, auto-remove unavailable units, auto-enroute on assign, DM on assign, and PM on assign.
**Default:** hide off-duty off, auto-remove off, auto-enroute on, DM on, PM on | **Requires:** ER:LC key for PM

## 4.11 - Departments Settings

### Linked Departments

Host Servers can view active, pending, and revoked links.
**Default:** none | **Requires:** Host Server

### Invite Tokens

Host Servers can generate and cancel department invite tokens.
**Default:** none | **Requires:** departments.manage

### Share Dispatch

Controls whether a linked department participates in shared dispatch.
**Default:** off per link until enabled | **Requires:** departments.manage

### Share ER:LC Key

Shares the host ER:LC key with a linked department.
**Default:** off per link until enabled | **Requires:** departments.manage

# 5 - Dangerous Settings

## 5.1 - Reset Options

### Disable Server

Locks the server from CADLY access without deleting data.
**Default:** active | **Requires:** owner

### Reset Server

Resets settings, roles, shift types, and custom buttons to defaults.
**Default:** not run | **Requires:** owner

## 5.2 - Data Management

### Delete Server Data

Deletes saved server data.
**Default:** not run | **Requires:** owner

### Change Server Type

Switches between Host Server and Department Server.
**Default:** selected during setup | **Requires:** owner after setup

Changing type can hide or reveal whole tabs. Review staff permissions and linked department state after switching.

# 6 - Troubleshooting Common Issues

## 6.1 - Settings Do Not Save

Check for validation limits such as max name length, max role count, max log types, or required fields. For ER:LC sub-settings, use the Save button after editing advanced sections.

## 6.2 - A Setting Is Hidden

Some tabs are type-specific. Sessions are Host Server features, while Deployments are Department Server features.

## 6.3 - Role Settings Do Not Take Effect

Make sure the member has the Discord role mapped in CADLY Roles and refresh permissions by reloading the panel.

# 7 - Getting Support and Resources

If you need help, several resources are available:

- [CADLY Documentation](/docs): Detailed reference for all features.
- [CADLY Support Server](https://discord.gg/cadly): Join for **fast help** from the team.
- [CADLY Email Support](mailto:admin@cadly.me): Reach out **via email** for direct support.