---
title: "Departments"
slug: "departments"
category: "Departments"
order: 1
description: "Link Department Server guilds to a Host Server and manage shared 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.

Either side can select the other server and create a private invitation link. An administrator or owner of the selected server accepts the request before the relationship becomes active.

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 dispatch context can flow between guilds and who owns ER:LC settings. An actively linked department inherits its host's ER:LC access, while Action Engine remains available to every department.

## 1.1 - Table of Contents

| Section | What it covers |
|---|---|
| [Linking Flow](#2---linking-flow) | Targeted invitations, acceptance, and revocation |
| [Shared Data](#3---shared-data) | Dispatch sharing and ER:LC authority |
| [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

A Host Server administrator can select a department from Departments and create a private invitation. A Department Server administrator can start the same flow from Server Linkage by selecting a host. The resulting link is locked to the selected recipient server, expires after 48 hours, and activates only after the recipient accepts it.

```cadly-mock
type: flow
title: Department link request
meta: Host and department setup
status: Awaiting acceptance
steps:
- Initiator selects server | The host or department chooses the other CADLY server.
- CADLY creates a private link | The request is locked to that selected server.
- Recipient accepts | An authorized administrator verifies both identities and activates shared dispatch.
```

## 2.1 - Department-Side Actions

Department Servers can select a host, create or accept a targeted invitation, view their current link, and unlink from a host.

## 2.2 - Host-Side Actions

Host Servers can list department links, create or accept targeted invitations, 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 - ER:LC Authority

An actively linked department inherits the Host Server's ER:LC key and configuration authority. It cannot change ER:LC settings. Remote command buttons remain Host Server-only for every department, whether linked or standalone. Linked departments may consume the read-only context required by dispatch and deployments.

A Department Server without an active host link is independent: it can configure its own ER:LC key and settings. Action Engine is available to both linked and standalone departments. When a department is unlinked, CADLY removes the inherited host key so the department can safely add its own.

## 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
- ER:LC Authority | Host only
```

# 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

### Link Invitations
Creates a private, single-recipient URL after an administrator selects the other server.
**Default:** none | **Requires:** departments.manage

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

### ER:LC Access
There is no per-department ER:LC sharing control. While the link is active, ER:LC authority stays with the Host Server.

## 4.2 - Department Server Settings

### Request a Host Link
Selects a Host Server and creates a private invitation URL for one of its administrators.
**Default:** none | **Requires:** Department administrator or owner

### Current Link

Shows the active host's Discord icon, name, server ID, and the date the link was approved. In regular Settings, the unlink control stays visible so members can see that the connection is protected; only the department's Discord owner or an administrator can use it.

To unlink, hold **Unlink server** for five seconds, then confirm the action. Unlinking stops the department from using the host connection and removes inherited ER:LC access, after which the department can configure its own integration.

Pending requests continue to show their approval state until the selected host accepts or the request is replaced.
**Default:** none | **Requires:** Department Server

# 5 - Troubleshooting Common Issues

## 5.1 - Invitation Is Invalid

Invitations expire and only work from the selected recipient server. Ask the initiator to select the correct server and create a fresh link.

## 5.2 - Invitation Cannot Be Accepted

Confirm the recipient is viewing the exact server named in the request and has the required administrator or department-management permission.

## 5.3 - ER:LC Settings Are Missing

ER:LC settings are hidden only while the department has an active host link. Unlinked departments can configure their own ER:LC integration; add an ER:LC key after unlinking.

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