Admin Commands

Complete reference for all administrator commands available in Clocky. These commands require Manage Server permission.


Server Configuration

/admin-set-autoclose

Configure how long work sessions remain active before automatically closing.

/admin-set-autoclose hours:12

Parameters:

  • hours (required): Number of hours before auto-close (1-24)

Description: Sets the automatic session closure duration for the server. When a user checks in, their session will automatically close after this many hours if they forget to check out.

Cooldown: 30 seconds

Notes:

  • Existing sessions use the setting from when they were created
  • New sessions use the updated setting immediately
  • Break time doesn't count toward auto-close duration
  • Changes don't apply retroactively

Recommended values:

  • 8 hours: Standard workday (9-5 schedule)
  • 12 hours: Default, includes overtime flexibility
  • 16 hours: Extended shifts (healthcare, emergency services)
  • 24 hours: Maximum, for 24-hour operations or very flexible schedules

Example response:

βœ… Auto-close updated to 12 hours

New sessions will close automatically after 12 hours of activity.
Existing sessions will use their original setting.

See Auto-close Settings for detailed guidance.


User Management

/admin-close-session

Manually close a user's stuck or forgotten work session.

/admin-close-session user:@username

Parameters:

  • user (required): The Discord user whose session to close

Description: Immediately closes the specified user's active work session, calculates their worked time (excluding breaks), and records it to their history. The user is notified that their session was closed by an admin.

Cooldown: 10 seconds

Use cases:

  • User forgot to check out before leaving
  • User's Discord client crashed and they can't check out
  • Session appears stuck or corrupted
  • Bot was offline during checkout attempt

Shows:

  • Check-in time
  • Check-out time (admin closed)
  • Total session duration
  • Break time (if any)
  • Net worked time

Example response:

βœ… Session closed for @johndoe

Check-in: 9:00 AM
Check-out: 5:30 PM (admin closed)
Duration: 8 hours 30 minutes
Break time: 1 hour 0 minutes
Net worked: 7 hours 30 minutes

User has been notified.

Notes:

  • User must have an active session in THIS server
  • Break time is automatically subtracted
  • Session is recorded in user's history
  • User receives DM notification (if DMs enabled)

See User Management for detailed documentation.


/stats (Admin view)

View any user's work statistics for different time periods.

/stats user:@username range:week

Parameters:

  • user (required for admin): The Discord user whose stats to view
  • range (optional): Time period - today, week, month, or all-time (default: today)

Description: Admins with Manage Server permission can view any user's statistics, not just their own. This is useful for team management, performance reviews, payroll verification, and identifying issues.

Cooldown: 10 seconds

Shows:

  • Total worked time for the selected period
  • Number of sessions completed
  • Average session duration
  • Longest session
  • Time breakdown by day (for week/month ranges)

Privacy: Users are notified when admins view their statistics for transparency.

Example:

# View user's weekly stats
/stats user:@alice range:week

# View user's monthly stats
/stats user:@bob range:month

# View user's today stats
/stats user:@charlie range:today

Example response:

πŸ“Š Statistics for @alice (This Week)

Total worked: 32 hours 15 minutes
Sessions: 10
Average: 3 hours 13 minutes
Longest: 5 hours 30 minutes

Daily Breakdown:
Monday: 6h 30m (2 sessions)
Tuesday: 7h 15m (2 sessions)
Wednesday: 5h 45m (2 sessions)
Thursday: 6h 0m (2 sessions)
Friday: 6h 45m (2 sessions)

See Viewing User Stats for detailed documentation.


Deletion Management

/admin-configure-deletion view-config

View the current data deletion policy configuration.

/admin-configure-deletion view-config

Description: Displays your server's current deletion policy settings, including policy type, grace period (if applicable), legal retention status, and pending deletion request count.

Cooldown: None

Shows:

  • Current deletion policy (immediate, grace period, or requires approval)
  • Grace period duration (if grace period mode)
  • Legal retention status and duration
  • Number of pending deletion requests

Example response:

βš™οΈ Deletion Policy Configuration

Policy: Grace Period
Grace period: 30 days
Legal retention: Enabled (7 years)
Pending requests: 2

Users can delete their data, but it will be removed after 30 days.
Data within legal retention period cannot be deleted.

/admin-configure-deletion set-policy

Configure the data deletion policy for your server.

/admin-configure-deletion set-policy policy:immediate

Parameters:

  • policy (required): Choose from:
    • immediate - Delete data instantly when requested
    • grace_period - Delay deletion for recovery window
    • requires_approval - Admins must approve requests

Description: Sets how user data deletion requests are handled in your server. This is critical for balancing GDPR compliance with organizational needs.

Cooldown: 60 seconds

Policy details:

Immediate:

  • Data deleted instantly with no recovery
  • Best GDPR compliance
  • Simplest to manage
  • No admin overhead

Grace Period:

  • Deletion delayed for configurable days
  • Allows recovery from accidental deletions
  • User can cancel during grace period
  • Requires setting grace period duration

Requires Approval:

  • Admins must manually approve each request
  • Maximum control and oversight
  • May conflict with GDPR timelines if slow
  • Requires active admin management

Example:

# Set to immediate deletion
/admin-configure-deletion set-policy policy:immediate

# Set to grace period (then set duration)
/admin-configure-deletion set-policy policy:grace_period
/admin-configure-deletion set-grace-period days:30

# Set to requires approval
/admin-configure-deletion set-policy policy:requires_approval

See Deletion Policies for comprehensive guidance.


/admin-configure-deletion set-grace-period

Set the grace period duration for delayed deletion.

/admin-configure-deletion set-grace-period days:30

Parameters:

  • days (required): Grace period duration (1-365 days)

Description: When using grace period deletion mode, this sets how many days to wait before permanently deleting user data. During this period, users can cancel their deletion request.

Cooldown: 60 seconds

Recommended durations:

  • 7 days: Quick recovery, low-value data
  • 14 days: Standard business cycle
  • 30 days: Monthly reporting cycles (recommended)
  • 90 days: Quarterly audits, high-value data

Notes:

  • Only applies when policy is set to grace_period
  • GDPR requires deletion within 30 days - periods longer than 30 days may require justification
  • Users receive notification 24 hours before deletion
  • Users can cancel anytime during grace period with /data-cancel-deletion

/admin-configure-deletion enable-legal-retention

Enable or disable legal retention requirements.

/admin-configure-deletion enable-legal-retention enabled:true

Parameters:

  • enabled (required): true to enable, false to disable

Description: Legal retention prevents data deletion for a specified period due to legal requirements (employment law, tax regulations, etc.). When enabled, deletion requests for data within the retention period are denied.

Cooldown: 60 seconds

Legal basis examples:

  • Employment records: 7 years (labor law, tax law)
  • Financial records: 7 years (tax regulations)
  • Healthcare records: 10 years (HIPAA)
  • Contract obligations: Varies

GDPR compliance: Legal retention is allowed under GDPR Article 17(3) when required by law or necessary for legal claims. You must have a valid legal basis and document it.

Example:

# Enable legal retention
/admin-configure-deletion enable-legal-retention enabled:true

# Disable legal retention
/admin-configure-deletion enable-legal-retention enabled:false

See Legal Retention for detailed documentation.


/admin-configure-deletion set-retention-years

Set the legal retention duration.

/admin-configure-deletion set-retention-years years:7

Parameters:

  • years (required): Retention period in years (1-99)

Description: Sets how many years data must be retained for legal compliance. Data within this period cannot be deleted, even if requested by users.

Cooldown: 60 seconds

Common retention periods:

  • 7 years: Most common (employment, tax records)
  • 10 years: Healthcare, medical records
  • 5 years: Some financial records
  • Varies: Government contracts, litigation holds

Notes:

  • Only applies when legal retention is enabled
  • Must have documented legal basis
  • Users are informed when deletion is denied
  • Retention period starts from session date, not user creation

Example response:

βœ… Legal retention set to 7 years

Data from the past 7 years cannot be deleted.
Ensure this complies with your legal obligations.

/admin-review-deletion-requests list

List all pending deletion requests requiring approval.

/admin-review-deletion-requests list

Description: When deletion policy is set to "requires approval", this command shows all pending user deletion requests awaiting admin review. Only available when policy is requires_approval.

Cooldown: 10 seconds

Shows for each request:

  • User name and ID
  • Request date
  • Data scope (current-server or all-servers)
  • Request ID
  • Days pending

Example response:

πŸ“‹ Pending Deletion Requests (3)

1. @alice (ID: 123456)
   Requested: 2 days ago
   Scope: current-server
   Request ID: 1001

2. @bob (ID: 789012)
   Requested: 5 days ago
   Scope: all-servers
   Request ID: 1002

3. @charlie (ID: 345678)
   Requested: 1 day ago
   Scope: current-server
   Request ID: 1003

Use /admin-review-deletion-requests review to approve or deny.

Notes:

  • Only shows requests for THIS server
  • All-servers requests show in all servers where user has data
  • GDPR requires processing within 30 days

/admin-review-deletion-requests review

Review and approve or deny a specific deletion request.

/admin-review-deletion-requests review request-id:1001

Parameters:

  • request-id (required): The ID of the deletion request to review

Description: Opens a detailed view of the deletion request with approve and deny buttons. Admins can review the user's information and data before making a decision.

Cooldown: None (decision is permanent)

Shows:

  • User information (name, ID)
  • Request timestamp
  • Data scope (current-server or all-servers)
  • Data summary (session count, total hours)
  • Approve and Deny buttons

Approval workflow:

  1. Verify user identity
  2. Check if legal retention applies
  3. Export data if needed (use /stats user:@username range:all-time)
  4. Click Approve or Deny
  5. User is notified of decision

Valid reasons to deny:

  • Data subject to legal retention
  • Under active audit or investigation
  • Contractual obligation to retain
  • Request appears fraudulent

Invalid reasons to deny:

  • "We might need it later"
  • "It's useful to have"
  • Administrative convenience

Example response (when approved):

βœ… Deletion request approved

Request ID: 1001
User: @alice
Data has been permanently deleted.

User has been notified.

GDPR warning: You must have a valid legal ground to deny deletion requests. Document all denials with legal basis. Process requests within 30 days.

See Requires Approval Mode for detailed guidance.


System Information

/rate-limit-stats

View rate limiting statistics for your server.

/rate-limit-stats

Description: Displays detailed rate limiting statistics including commands per minute, throttled requests, per-user usage, and circuit breaker status. Useful for identifying abuse patterns and monitoring server health.

Cooldown: 30 seconds

Shows:

  • Commands executed per minute
  • Throttled request count
  • Top users by command usage
  • Circuit breaker status (if tripped)
  • Rate limit tier (Free/Premium/Pro/Lifetime)

Example response:

πŸ“Š Rate Limit Statistics

Current load: 45 commands/minute
Capacity: 180 commands/minute (Premium)
Throttled: 3 requests in past hour

Top users (past hour):
1. @alice: 120 commands
2. @bob: 95 commands
3. @charlie: 67 commands

Circuit breaker: Healthy

Use cases:

  • Identify users hitting rate limits frequently
  • Monitor server command usage patterns
  • Detect potential abuse or bot attacks
  • Decide if tier upgrade is needed

Notes:

  • Admin users bypass most rate limits
  • Premium/Pro/Lifetime tiers get higher limits (2x, 3x, 5x respectively)
  • Statistics reset every hour

See Rate Limiting for detailed documentation.


/billing

View current subscription tier and billing information.

/billing

Description: Shows your server's current subscription tier, user count, data retention settings, and provides upgrade options.

Cooldown: 30 seconds

Shows:

  • Current tier (Free, Premium, Pro, Lifetime)
  • Active user count and limit
  • Data retention period
  • Monthly/annual pricing
  • Upgrade button (if applicable)

Example response:

πŸ’³ Billing Information

Tier: Premium
Active users: 18 / 25
Data retention: 365 days
Rate limits: 180 commands/min

Monthly: $4.99
Next billing: March 1, 2025

[Manage Subscription] [Upgrade to Pro]

Notes:

  • Only admins can view billing information
  • Upgrade takes effect immediately
  • Downgrade takes effect at next billing cycle

See Subscription Management for detailed documentation.


Command Permissions

All admin commands require Manage Server permission in Discord.

Granting admin access

To grant admin access to a user:

  1. Go to Server Settings β†’ Roles
  2. Find or create a role with Manage Server permission
  3. Assign the role to trusted users
  4. They can now use all /admin-* commands

Security best practices

DO:

  • Only grant Manage Server to trusted users
  • Review admin list quarterly
  • Remove access when no longer needed
  • Document who has admin access and why

DON'T:

  • Grant admin to all moderators by default
  • Share admin accounts
  • Leave admin access active for inactive users

Command Cooldowns

Admin commands have cooldowns to prevent abuse:

CommandCooldownReason
/admin-set-autoclose30 secondsPrevent configuration spam
/admin-close-session10 secondsDatabase writes
/admin-configure-deletion60 secondsCritical setting changes
/admin-review-deletion-requestsNone/10sOne-time decisions
/rate-limit-stats, /billing30 secondsSystem queries

Note: Admins bypass standard user rate limits but still have per-command cooldowns for configuration changes.


Quick Reference

Initial Server Setup

/admin-set-autoclose hours:12
/admin-configure-deletion set-policy policy:grace_period
/admin-configure-deletion set-grace-period days:30

User Management

/admin-close-session user:@username
/stats user:@username range:week

Deletion Policy Management

/admin-configure-deletion view-config
/admin-review-deletion-requests list
/admin-review-deletion-requests review request-id:123

Monitoring

/rate-limit-stats
/billing

Was this page helpful?