---
title: "Host vs Department Servers"
slug: "server-types"
category: "Getting Started"
order: 2
description: "Choose the CADLY server type that matches how your ER:LC community is organized."
---

# 1 - Introduction

CADLY supports two guild types: **Host Server** and **Department Server**. The type controls which pages, settings, and workflows appear in the panel.

Use a Host Server when the Discord guild is the main moderation and staff-management hub. Use a Department Server when the guild represents a police, sheriff, fire, EMS, DOT, or other unit that links into a host community.

This choice matters because CADLY uses it to decide which defaults are safe. Host Servers are expected to own community-wide authority, while Department Servers are expected to inherit some context from a host and focus on unit-level work. Picking the correct type keeps staff from seeing features they cannot use and prevents department guilds from accidentally acting like the main community server.

If your community is small and everything happens in one Discord server, choose **Host Server**. You can still use dispatch, shifts, logs, and ER:LC tools without creating separate Department Servers. Choose Department Server only when the guild is intentionally subordinate to another CADLY-managed host.

## 1.1 - Table of Contents

| Section | What it covers |
|---|---|
| [Host Servers](#2---host-servers) | Main community management features |
| [Department Servers](#3---department-servers) | Linked department workflows |
| [Changing Type](#4---changing-server-type) | How switching works and what is preserved |
| [Troubleshooting](#5---troubleshooting-common-issues) | Common setup problems |

## 1.2 - Links to Related Documents

- [Server Settings](/docs/server-settings)
- [Departments](/docs/departments)
- [Dispatch & CAD](/docs/dispatch)
- [ER:LC Integration](/docs/erlc)

# 2 - Host Servers

A **Host Server** is the main server for your ER:LC community. It owns staff management, moderation records, verification, ER:LC keys, sessions, linked departments, and most settings.

Host Servers are the right choice when your guild runs the overall roleplay server. Staff use it for **shift tracking**, infractions, promotions, logs, LOA, verification, and ER:LC server operations.

Think of the Host Server as the source of truth for the community. If a rule, staff rank, ER:LC key, session lifecycle, or department relationship applies to the full server, it belongs on the Host Server. This keeps global records in one place and avoids departments having different versions of the same staff or moderation history.

Host Servers can still operate without linked departments. Department linking is optional and is mainly useful when your community has separate Discord guilds for each unit.

```cadly-mock
type: setting
title: Host server setup
meta: Server type comparison
status: Primary guild
items:
- Owns ER:LC Key | Yes
- Runs Sessions | Yes
- Links Departments | Yes
- Shares Dispatch | Optional
```

## 2.1 - Host Server Features

| Feature | Host Server | Notes |
|---|---:|---|
| Verification | Yes | Links Discord users to Roblox accounts and applies roles. |
| Shifts | Yes | Tracks staff on duty for Server A and optional Server B. |
| Sessions | Yes | Handles SSV, SSU, FULL, LPPL, SSD, and session analytics. |
| Infractions | Yes | Internal staff discipline records. |
| Promotions | Yes | Staff rank grants and revocations. |
| LOA | Yes | Temporary inactivity exemptions. |
| Logs | Yes | RP, moderation, BOLO, and custom incident logs. |
| ER:LC keys | Yes | Host can own and optionally share keys with linked departments. |
| Departments | Yes | Host generates invite tokens, approves links, and controls sharing. |
| Dispatch | Yes | Can run CAD and shared dispatch. |
| Deployments | No | Deployments are department-side workflows. |

## 2.2 - Recommended Next Docs for Host Servers

Start with [Server Settings](/docs/server-settings), then configure [Verification](/docs/verification), [ER:LC Integration](/docs/erlc), [Shifts & Duty](/docs/shifts), [Logs](/docs/logs), and [Departments](/docs/departments).

# 3 - Department Servers

A **Department Server** is a linked guild that belongs to a host community. It focuses on department-level operations such as dispatch participation, unit management, CAD visibility, and deployments.

Department Servers can link to a Host Server using an invite token. Once approved, the Host can share dispatch and ER:LC access with the department.

Department Servers work best when each unit has its own command staff, roster, and deployment workflow. They do not replace the Host Server; they extend it. The host decides whether the department can share dispatch and whether it receives the host ER:LC key.

If a department needs its own independent ER:LC server and is not subordinate to another CADLY guild, it may actually be a Host Server. The Department type is for connected hierarchy, not just "a server that happens to be a department".

```cadly-mock
type: setting
title: Department server setup
meta: Server type comparison
status: Linked guild
items:
- Owns ER:LC Key | Usually no
- Runs Deployments | Yes
- Uses Host Sessions | Yes
- Department Records | Local to department
```

## 3.1 - Department Server Features

| Feature | Department Server | Notes |
|---|---:|---|
| Department link request | Yes | Uses a host-generated token. |
| Dispatch / CAD | Yes | Department units can participate in shared dispatch. |
| Deployments | Yes | Department deployment profiles and analytics live here. |
| ER:LC shared key | Optional | Controlled by Host Server link settings. |
| Shifts | Yes | Used for duty state and dispatch eligibility. |
| Logs | Yes | Department-side logs can exist, depending on permissions and links. |
| Sessions | No | Sessions belong to Host Servers. |
| Host department management | No | Only Host Servers approve, reject, or revoke department links. |

## 3.2 - Recommended Next Docs for Department Servers

Read [Departments](/docs/departments), [Dispatch & CAD](/docs/dispatch), [ER:LC Integration](/docs/erlc), and [Server Settings](/docs/server-settings).

# 4 - Changing Server Type

You choose the server type during setup. After setup, changing type is a **Danger Zone** action in [Server Settings](/docs/server-settings) and requires the Discord server owner.

Switching type updates `general.guildType` and applies type-specific defaults. Existing generic settings stay in the settings object, but pages that do not apply to the new type may be hidden.

Before changing type, tell staff who are actively using the panel. A type switch can change navigation immediately, and staff may lose access to pages that no longer apply. It is best to switch during a quiet period, then review the visible tabs and permissions.

## 4.1 - What Is Preserved

General configuration, roles, permissions, and most feature settings remain stored. CADLY does not delete your whole settings file just because the type changes.

## 4.2 - What Changes

When you switch from Department to Host, Host-only features such as department management and sessions become available. When you switch from Host to Department, Host-only workflows are hidden.

## 4.3 - When to Switch

Switch only when the guild's purpose changed. If you only need to connect a department to a host, keep the department as a Department Server and link it through [Departments](/docs/departments).

Good reasons to switch include merging a former department into the main community server, splitting a main community into separate host and department guilds, or correcting a setup mistake before staff have started relying on the panel. Avoid switching just to test a page; use documentation or a test guild instead.

# 5 - Troubleshooting Common Issues

## 5.1 - I Picked the Wrong Type During Setup

Open Settings, go to Danger, and use **Change Server Type**. Only the server owner can change type after setup.

## 5.2 - Department Features Are Missing

Confirm the guild is a Department Server and that the Host Server approved the link. Pending links do not provide shared dispatch or ER:LC key access.

# 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.