---
title: "Logging"
slug: "logs"
category: "Servers"
order: 8
description: "Create, search, edit, delete, and audit moderation and incident logs."
---

# 1 - Introduction

CADLY tracks two practical categories of logs: **moderation logs** created by staff and **automated audit records** created by CADLY actions and automations.

Moderation logs document incidents, RP situations, warnings, kicks, bans, and BOLOs. Automated audit records are used by features such as the Action Engine and settings activity where available.

Logs are the main evidence trail for non-staff incidents. They are flexible enough for roleplay notes, player discipline, BOLOs, and custom record types. Unlike infractions, logs are usually tied to Roblox players or incidents rather than staff rank discipline.

Good logs are specific. Include the target, server slot, what happened, what action was taken, and any useful details such as location or evidence reference. This makes later appeals and staff reviews easier.

## 1.1 - Table of Contents

| Section | What it covers |
|---|---|
| [Creating Logs](#2---creating-logs) | Slash command and panel fields |
| [Searching and Managing](#3---searching-and-managing-logs) | Filters, edit, delete, stats, BOLOs |
| [Settings](#4---settings--configuration) | Log types and permissions |
| [Troubleshooting](#5---troubleshooting-common-issues) | Common log problems |

## 1.2 - Links to Related Documents

- [Moderation Panel](/docs/moderation)
- [Action Engine](/docs/action-engine)
- [Server Settings](/docs/server-settings)

# 2 - Creating Logs

Use **/log create** with `server`, `log_type`, `reason`, and one target identifier: Roblox ID, Roblox username, or a linked Discord member. The optional `details` argument accepts JSON or key-value pairs.

The panel Logs page provides filters and forms for staff with matching permissions. Default log types are Note, Roleplay Log, Warning, Kick, Ban BOLO, and Ban.

Use Roblox ID when possible because usernames can change. Roblox username is convenient when staff are working quickly, and linked Discord member is useful when the target has completed verification.

Custom details are best for structured facts such as location, vehicle, evidence URL, or officer notes. If your log type has custom fields, use those instead of putting everything in the reason.

```cadly-mock
type: record
title: Roleplay Log
meta: Logs > Server A
status: Open
items:
- Target | RiversideUnit_42
- Location | Springfield Gas
- Log Type | Roleplay Log
- Evidence | Attached URL
```

## 2.1 - Required Fields

| Field | Purpose |
|---|---|
| Server | Server A or Server B. |
| Log type | Configured log type ID or name. |
| Reason | Main description of the incident. |
| Target | Roblox ID, Roblox username, or linked Discord member. |
| Details | Optional structured fields. |

# 3 - Searching and Managing Logs

Use **/log view** to search by server, log ID, Roblox ID, Roblox username, Discord user, log type, and limit. Use **/log edit** to update reason or details. Use **/log delete** to delete a log.

Use **/log stats** to view log statistics for a target. BOLO log types can be marked complete when staff have the complete BOLO permission for the matching server slot.

Editing should correct mistakes or add missing details. Deleting should be rare because it removes an audit record. If a log was made in error but you still want history, edit the reason or add details explaining the correction.

## 3.1 - Server-Scoped Permissions

Log permissions are server-scoped:

| Permission | Server A | Server B |
|---|---|---|
| View logs | `server.logs.view.a` | `server.logs.view.b` |
| Create logs | `server.logs.create.a` | `server.logs.create.b` |
| Edit logs | `server.logs.edit.a` | `server.logs.edit.b` |
| Delete logs | `server.logs.delete.a` | `server.logs.delete.b` |
| Complete BOLOs | `server.logs.complete_bolo.a` | `server.logs.complete_bolo.b` |

# 4 - Settings / Configuration

## 4.1 - Logs Module

### Enable Logs
Turns incident logging on or off. When disabled, no logs can be created and the logs page is hidden.
**Default:** on | **Requires:** none

### Logging Channels
Channel where log messages are posted.
**Default:** none | **Requires:** none

## 4.2 - Log Types

### Log Types
Configures available log types, descriptions, colors, allowed roles, BOLO status, location mode, custom fields, and optional DM behavior.
**Default:** Note, Roleplay Log, Warning, Kick, Ban BOLO, Ban | **Requires:** none

Keep log type names short and obvious. Staff should not need to guess whether an incident is a Warning, RP Log, or BOLO during an active scene.

### Location Mode
Controls whether a log type has no location, optional location, or required location.
**Default:** off unless configured | **Requires:** none

### Custom Fields
Adds up to three custom number or text fields to a log type.
**Default:** none | **Requires:** none

### PM User
Sends a Discord DM to the target user when a log of that type is created.
**Default:** off | **Requires:** none

# 5 - Troubleshooting Common Issues

## 5.1 - A Staff Member Cannot Create Logs

Assign the `server.logs.create.a` or `server.logs.create.b` permission through CADLY roles. The selected server slot matters.

## 5.2 - The Log Type Is Not Found

Use the log type ID or exact name. If the type was deleted in settings, existing history remains but new logs cannot use that type.

## 5.3 - User Resolution Fails

If using a Discord member target, the member must be linked to Roblox. Otherwise use Roblox ID or Roblox username directly.

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