---
title: "Departments"
slug: "departments"
category: "Departments"
order: 1
description: "Link Department Server guilds to a Host Server and manage shared ER:LC and dispatch access."
---

# 1 - Introduction

Departments are linked Discord guilds connected to a Host Server. They let a host community keep central oversight while each department runs its own dispatch and deployment workflows.

The Host Server creates invite tokens, reviews link requests, approves departments, revokes links, and controls sharing.

This structure is useful when a community has one main ER:LC server but separate Discord guilds for law enforcement, fire, DOT, EMS, or other units. Each department can manage its own operations while the host keeps authority over shared systems.

Department links are not just cosmetic. They control whether data and access can flow between guilds, especially for dispatch and ER:LC keys. Only approve departments you trust to participate in shared operations.

## 1.1 - Table of Contents

| Section | What it covers |
|---|---|
| [Linking Flow](#2---linking-flow) | Tokens, requests, approvals, and revocation |
| [Shared Data](#3---shared-data) | Dispatch and ER:LC sharing |
| [Settings](#4---settings--configuration) | Department settings reference |
| [Troubleshooting](#5---troubleshooting-common-issues) | Common linking problems |

## 1.2 - Links to Related Documents

- [Host vs Department Servers](/docs/server-types)
- [Dispatch & CAD](/docs/dispatch)
- [ER:LC Integration](/docs/erlc)

# 2 - Linking Flow

Host Servers generate department invite tokens. A Department Server pastes the token into Server Linkage and submits a request.

The Host Server can approve, reject, or revoke the request. Link statuses include pending, active, and revoked.

Tokens are intentionally controlled by the host. This prevents random guilds from attaching themselves to your community. If a token leaks, cancel it and generate a new one.

Approval should happen after the host confirms the department guild is legitimate and configured as a Department Server. A pending request is safe because it does not grant active sharing until approved.

```cadly-mock
type: flow
title: Department link request
meta: Host and department setup
status: Pending approval
steps:
- Host creates token | The host generates an invite token from department settings.
- Department submits request | The department server pastes the token into Server Linkage.
- Host approves link | Shared dispatch and ER:LC access follow the host settings.
```

## 2.1 - Department-Side Actions

Department Servers can preview a token, request a link, view their current link, and unlink from a host.

## 2.2 - Host-Side Actions

Host Servers can list all department links, generate and cancel tokens, approve or reject pending links, revoke active links, and view department overviews.

# 3 - Shared Data

## 3.1 - Share Dispatch

When enabled, the department participates in shared dispatch. Units and calls can flow across linked guilds depending on dispatch settings.

Use this when department units should appear in a shared CAD environment. For example, a police department and fire department can both respond to calls created by dispatch.

## 3.2 - Share ER:LC Key

When enabled, the Host Server applies its ER:LC key to the department. This lets the department use ER:LC-powered features without owning its own key.

Key sharing is convenient but sensitive. A department using the host key can run ER:LC-powered workflows through its own permissions and settings. Keep ER:LC command permissions tight in linked departments.

## 3.3 - Department Overview

Host Servers can view department name, short name, theme color, member count, active shifts, link date, and recent logs.

```cadly-mock
type: status
title: Linked department overview
meta: Departments > Riverside Police
status: Active
items:
- Members | 86
- Active Shifts | 12
- Share Dispatch | On
- Share ER:LC Key | On
```

# 4 - Settings / Configuration

## 4.1 - Host Server Settings

### Linked Departments
Displays active, pending, and revoked department links.
**Default:** none | **Requires:** Host Server and departments.view

### Invite Tokens
Creates tokens that Department Servers can use to request linking.
**Default:** none | **Requires:** departments.manage

### Share Dispatch
Toggles dispatch sharing per active link.
**Default:** off | **Requires:** departments.manage

### Share ER:LC Key
Toggles ER:LC key sharing per active link.
**Default:** off | **Requires:** departments.manage

Enable this only after the department has correct CADLY roles and trusted administrators. If there is a dispute or security concern, turn sharing off or revoke the link.

## 4.2 - Department Server Settings

### Host Server Token
Token field used to request linking to a Host Server.
**Default:** blank | **Requires:** Department Server

### Current Link
Shows the department's active or pending link state.
**Default:** none | **Requires:** Department Server

# 5 - Troubleshooting Common Issues

## 5.1 - Token Is Invalid

Tokens expire, can be canceled, and can be used only by Department Servers. Ask the host to generate a fresh token.

## 5.2 - Request Stays Pending

The Host Server must approve it. Pending links do not grant shared ER:LC or dispatch behavior.

## 5.3 - Shared ER:LC Settings Are Locked

That is expected when the department is using a Host Server's shared key. The host controls the key.

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