z-dev Logoz-devv4.2
FeaturesDemoPricingDocsStatus
Introduction
What is Z-UCP?The SaaS ConceptGetting StartedFeature Overview
Concepts
Architecture & ConceptsTier System
Player Hub
Player GuideZ-Property & Housing System
Admin Control
Audit Logs & SecurityAdmin OverviewPermissions in DetailRoles & Permissions (RBAC)CMS & Whitelabeling
Modules & Integrations
CMS Block ReferenceDatabase Best PracticesDiscord BotStatus PageGlobal BansDatabase Module
Technical & Security
Bridge TroubleshootingFiveM Bridge SetupPrivacy & GDPRAPI Reference
z-dev Logoz-dev

Das Management Panel fuer FiveM RP Server. Professionell, zuverlaessig, DSGVO-konform.

Produkt
  • Features
  • Discord Bot
  • Preise
  • Changelog
  • Roadmap
  • Status
Ressourcen
  • Dokumentation
  • Setup Guide
Projekt
  • Ueber
  • Kontakt
Rechtliches
  • Datenschutz
  • Impressum
  • AGB
  • Cookie Policy
© 2026 z-dev.appStatusv4.2.0

Audit Logs & Security

Maximize your team's security with complete logs.

Audit Logs & Security

Audit Logs are a crucial tool for managing your team. In Z-UCP, every administrative action is irrevocably logged.

What is logged?

1. Player Management

  • Kicks, bans, warns (including reason and duration).
  • Notes on players (creation, editing, deletion).
  • Reports (status changes, assignments).

2. CMS & Design

  • Every change to the landing page.
  • Changes to colors, logos, or custom CSS.
  • Navigation changes.

3. Database Module

  • Writing SQL queries via the console.
  • Manual changes to values in the DB editor.
  • Creation and restoration of backups.

4. System & Billing

  • Role and permission changes.
  • Project settings (domain, whitelist).
  • API key generations.

Reading the Log Entries

An audit entry consists of:

  • Timestamp: When was the action performed?
  • User: Who performed the action?
  • Action: What was done? (e.g., player.ban)
  • Target: Which player or object was affected?
  • Details: A JSON object with the exact values before and after the change.

Examples of Audit Analysis

Case 1: "A player was banned without reason"

Search the audit log for the action player.ban and the target identifier. You will immediately see the performing administrator and the reason given.

Case 2: "Database values were manipulated"

Filter for the action database.write. You can see exactly which admin changed which cell in which table from 5000 to 1000000.

Important: Audit logs cannot be deleted by administrators (except for the SuperAdmin in the Enterprise tier). This prevents team members from covering their tracks.

PreviousZ-Property & Housing SystemNext Admin Overview