Server Configuration

Advanced configuration options for server administrators.

Auto-close settings

Configure how long work sessions remain active before automatically closing.

Set auto-close duration

/admin-set-autoclose hours:12

Recommended durations

How auto-close works

1. Timer starts: When a user runs /checkin, the auto-close timer begins
2. Duration tracked: Clocky monitors how long the session has been active
3. Auto-close triggers: When the configured duration is reached, the session closes automatically
4. Break time excluded: Only active work time counts, breaks don't extend the duration
5. No notification: Users are not notified when sessions auto-close

Example scenarios

Scenario 1: Forgot to check out

• User checks in: Monday 9:00 AM
• User forgets to check out
• Auto-close setting: 12 hours
• Session closes: Monday 9:00 PM
• Recorded time: 12 hours (minus breaks)

Scenario 2: Working overtime

• User checks in: 8:00 AM
• Auto-close: 8 hours
• Session closes: 4:00 PM automatically
• User must check in again if continuing work

Changing auto-close

When you change the auto-close duration:

• Existing sessions: Use the old duration (set when they started)
• New sessions: Use the new duration immediately
• No retroactive changes: Past sessions are not affected

Deletion policies

Configure how user data deletion requests are handled in your server.

View current policy

/admin-configure-deletion view-config

Shows your current deletion policy configuration.

Available policies

1. Immediate deletion

Data is deleted instantly when requested by users.

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

Pros:

• User has instant control
• Simplest to manage
• No admin overhead

Cons:

• No recovery period
• Accidental deletions are permanent

Best for: Small teams, low-risk data, GDPR compliance priority

2. Grace period deletion

Data deletion is delayed, allowing for recovery.

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

Then set the grace period:

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

Pros:

• Recovery window for accidental deletions
• Time to back up if needed
• User can cancel deletion

Cons:

• Data still stored during grace period
• Requires tracking pending deletions

Best for: Medium teams, valuable historical data

3. Requires approval

Admins must manually approve deletion requests.

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

Pros:

• Full admin control
• Prevent accidental or malicious deletions
• Time to export data before deletion

Cons:

• Requires active admin management
• May delay legitimate deletions
• Could conflict with GDPR timelines

Best for: Large organizations, compliance requirements, sensitive data

Legal retention

Enable legal retention to prevent deletion for a specific period:

/admin-configure-deletion enable-legal-retention enabled:true
/admin-configure-deletion set-retention-years years:7

When to use:

• Legal requirements (employment law, tax records)
• Contract obligations
• Audit requirements

Reviewing deletion requests

If using "requires_approval" mode:

/admin-review-deletion-requests list

Shows all pending deletion requests.

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

Review a specific request with approve/deny options.

See Deletion Policies for detailed guidance.

Rate limiting

Clocky includes built-in rate limiting to prevent abuse and ensure fair usage.

View rate limit stats

/rate-limit-stats

Shows:

• Commands per minute
• Throttled requests
• Per-user statistics
• Circuit breaker status

Rate limits by tier

Per-command cooldowns

Commands have individual cooldowns to prevent spam:

Admin exemptions

Users with "Manage Server" permission bypass rate limits for:

• All admin commands
• Viewing other users' stats
• Manual session management

This ensures admins can always manage the server effectively.

Handling rate limit hits

If a user hits rate limits:

1. They receive an error message with wait time
2. Their request is logged in /rate-limit-stats
3. No action is taken against the user
4. Rate limits reset automatically

Configuration commands reference

Quick reference for all admin configuration commands:

Auto-close

/admin-set-autoclose hours:12

Set session auto-close duration (1-24 hours).

Deletion policy

# View current configuration
/admin-configure-deletion view-config

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

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

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

# Set retention duration
/admin-configure-deletion set-retention-years years:7

Deletion request management

# List pending requests
/admin-review-deletion-requests list

# Review specific request
/admin-review-deletion-requests review request-id:123

Rate limiting

# View statistics
/rate-limit-stats

Session management

# Close user's stuck session
/admin-close-session user:@username

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

Best practices

Initial configuration

When first setting up Clocky:

1. Set auto-close to match your longest typical shift + 2 hours buffer
2. Configure deletion policy based on your data retention needs
3. Test with yourself before rolling out to team
4. Document your policies and share with users
5. Review /rate-limit-stats weekly to spot issues

Regular maintenance

Weekly:

• Check /rate-limit-stats for abuse patterns
• Review any pending deletion requests (if using approval mode)

Monthly:

• Review auto-close duration - adjust if needed
• Check for inactive users with /admin-user-management
• Verify deletion policy still meets requirements

Quarterly:

• Audit data retention compliance
• Review and update documentation
• Check for feature updates

Security recommendations

1. Limit admin access: Only grant "Manage Server" to trusted users
2. Enable legal retention: If required for compliance
3. Document policies: Keep written records of configuration decisions
4. Regular backups: If using grace period deletion
5. Monitor rate limits: Watch for unusual patterns

Troubleshooting

Auto-close not working

Check:

• Session age with /status
• Current auto-close setting
• Session was created after setting change

Fix:

• Existing sessions use old setting - wait for new check-ins

Deletion requests piling up

Cause: Approval mode enabled but requests not reviewed

Solution:

1. Run /admin-review-deletion-requests list
2. Review each pending request
3. Consider switching to grace period mode if overwhelmed

Rate limits too restrictive

Symptoms: Users frequently hitting rate limits

Solutions:

1. Check /rate-limit-stats to identify patterns
2. Consider upgrading to Premium (3x higher limits)
3. Educate users on command cooldowns
4. Spread out automated scripts/bots

Related pages