--- title: 'CADLY Introduction' slug: 'Welcome' category: 'Getting Started' order: 1 description: 'Learn what CADLY does and how to start configuring your ER:LC community.' --- # 1 - Introduction CADLY is an ER:LC Discord bot and web panel for communities that need staff tools, live CAD operations, ER:LC integration, records, applications, and department workflows in one place. This documentation is written for server owners and staff leadership. It explains what each feature does, which settings matter, and how to avoid common setup mistakes before your staff begin using CADLY. The best way to learn CADLY is to configure it in layers. Start with server type and permissions, then enable the features your community actually needs. You do not need to enable every module on day one. ## 1.1 - Table of Contents | Section | What it covers | | ----------------------------------------------------- | --------------------------------------------- | | [What CADLY Is](#2---what-cadly-is) | Main purpose and feature areas | | [Setup Order](#3---recommended-setup-order) | A safe path for first-time setup | | [Core Concepts](#4---core-concepts) | Server types, permissions, ER:LC, and records | | [Troubleshooting](#5---troubleshooting-common-issues) | Common first-run issues | ## 1.2 - Links to Related Documents - [Host vs Department Servers](/docs/server-types) - [Server Settings](/docs/server-settings) - [Verification](/docs/verification) - [ER:LC Integration](/docs/erlc) - [Dispatch & CAD](/docs/dispatch) - [CADLY PRO](/docs/cadly-pro) # 2 - What CADLY Is CADLY combines Discord staff management with ER:LC operations. It can track shifts, manage LOA, store logs, issue promotions and infractions, run applications, connect to ER:LC, and coordinate dispatch calls. The web panel gives staff a structured interface for settings and records. The Discord bot provides slash commands and interactive messages for workflows that happen inside Discord. ```cadly-mock type: status title: CADLY operating picture meta: Host server overview status: Configured items: - Discord Staff Tools | Shifts, LOA, logs, promotions, infractions - ER:LC Operations | Live data, commands, sessions, action rules - Department Workflows | Linked departments, dispatch, deployments - Public Intake | Verification and applications ``` ## 2.1 - Main Feature Areas | Area | What it helps with | | ------------ | ------------------------------------------------------------------ | | Verification | Links Discord users to Roblox accounts and applies roles. | | Shifts | Tracks staff duty time, breaks, leaderboards, and shift waves. | | Logs | Stores moderation, RP, BOLO, and custom incident records. | | LOA | Manages temporary inactivity exemptions. | | Promotions | Records rank grants and promotion revocations. | | Infractions | Tracks staff discipline, suspensions, demotions, and terminations. | | Applications | Builds public forms and review workflows. | | ER:LC | Reads live server data and sends approved in-game commands. | | Dispatch | Coordinates units, calls, assignments, and CAD map context. | | Departments | Links Department Servers to a Host Server. | ## 2.2 - Core Values CADLY's core feature set is designed to remain free. [CADLY PRO](/docs/cadly-pro) exists to support development and unlock higher limits or customization, not to block normal server operation. CADLY also tries to keep records auditable. Revoking a promotion or infraction does not erase history, and logs are meant to explain what staff did and why. # 3 - Recommended Setup Order ## 3.1 - Invite the Bot Invite CADLY from [cadly.me/invite](https://cadly.me/invite). Make sure the bot role is above any roles CADLY needs to assign, remove, or manage. Discord role hierarchy is one of the most common setup blockers. If CADLY cannot assign a role, the setting may be correct but Discord is refusing the action. ## 3.2 - Open the Dashboard Use the dashboard flow from Discord or the CADLY website, then select your server. You need appropriate Discord permissions to configure the server. During setup, choose whether this guild is a **Host Server** or **Department Server**. Read [Host vs Department Servers](/docs/server-types) before choosing if your community has separate department guilds. ## 3.3 - Configure Identity and Roles Set the server name, short name, theme color, and basic server settings. Then create CADLY roles that map Discord roles to CADLY permissions. Do this before enabling advanced features. Most pages depend on CADLY permissions, and testing is easier when the role model is already clear. ## 3.4 - Enable Features One at a Time Start with the modules your staff need immediately. Common first modules are [Verification](/docs/verification), [Shifts & Duty](/docs/shifts), [Logs](/docs/logs), and [ER:LC Integration](/docs/erlc). After enabling a module, test it as both an administrator and a normal staff member. This confirms that permissions, channels, and Discord role hierarchy are correct. # 4 - Core Concepts ## 4.1 - Server Types Host Servers are the main community hub. Department Servers are linked guilds that belong to a host. The type controls which settings and pages appear. If you run everything in one Discord guild, you usually want a Host Server. If this guild is one unit under another CADLY-managed community, you usually want a Department Server. ## 4.2 - Permissions CADLY permissions are assigned through CADLY roles, which map to Discord roles. Discord administrator and server owner status can also grant built-in access. Permissions are often feature-specific and sometimes server-slot-specific. For example, logs and ER:LC commands can differ between Server A and Server B. ## 4.3 - ER:LC Server Slots CADLY supports Server A and optional Server B. Mono Server Mode keeps only Server A active. The toggle is at the bottom of **Settings > General**; turn it off only if you actually run two ER:LC server slots. Server-slot separation matters for API keys, duty roles, logs, command permissions, dispatch, and CAD access. ## 4.4 - Records and Audits CADLY records are meant to be reviewed later. Promotions, infractions, logs, LOA requests, applications, and dispatch calls all create history that helps leadership understand what happened. Use clear reasons and notes. Good records make appeals, staff reviews, and policy enforcement much easier. # 5 - Troubleshooting Common Issues ## 5.1 - A Page Is Missing Check your server type and permissions. Some pages are Host-only, some are Department-focused, and most require View Server plus feature-specific access. ## 5.2 - Roles Are Not Assigned Move the CADLY bot role above the target role. Discord blocks bots from managing roles at or above their highest role. ## 5.3 - ER:LC Data Does Not Load Confirm ER:LC is enabled, the correct server slot has a valid key, and the panel has recently requested data. CADLY refreshes idle server slots less often than actively viewed slots. ## 5.4 - Staff Cannot Use a Feature Check three things: the module is enabled, the member has the correct CADLY permission, and any required channel or role setting is configured. # 6 - 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.