Control Center Usage Policy

[- Alex - 36]

Control Center Usage Policy
Administrative Access, Security & Acceptable Use
Public GGU policy — subject to revision as systems, responsibilities, and operational practices change.

Public Transparency:
This policy is intentionally published so the community can understand GGU's standards and accountability. Credentials, recovery material, private personnel records, and active security-sensitive details remain restricted.

The GGU Control Center provides administrative access to game servers and related services. This policy defines how that access may be used, who may use it, and the minimum security and accountability standards expected of authorized users.

 

Scope

This policy applies to anyone granted access to the GGU Control Center, including Leadership, Development, approved contributors, and authorized partners.

Current GGU Leadership roles and holders are maintained at https://gguclan.com/ranks-and-roster/.

 

Authorized Use

• Start, stop, restart, or otherwise manage services within your assigned responsibility.
• View console output and logs for troubleshooting and administration.
• Manage files for servers you are authorized to maintain.
• Use backups, schedules, startup settings, and variables within your assigned scope.
• Perform approved maintenance, updates, configuration changes, and deployments.
• Use server administration features required to support GGU operations.

 

Least Privilege

Access must be limited to the servers and capabilities required for the person's responsibilities. Holding a Leadership title does not automatically require or grant access to every server or node.

 

Account Security

• Use your own account. Do not share Control Center credentials.
• Enable two-factor authentication where supported.
• Use a unique password and secure recovery methods.
• Do not share SFTP credentials, API tokens, or other access material through public or inappropriate channels.
• Report suspected compromise immediately.
• Do not remain signed in on shared or untrusted devices.

 

Server Boundaries

Administrative access is scoped. Do not access, inspect, or modify servers, files, databases, or services outside your assigned responsibility without authorization.

 

Production Actions

• Avoid unnecessary restarts or service interruptions.
• Use normal stop/restart procedures before using forceful termination unless immediate termination is necessary.
• Back up or ensure rollback capability before high-impact file or configuration changes.
• Do not delete backups, databases, or production files without authorization and a clear reason.
• Do not modify node, Wings, host, or organization-wide infrastructure from a game-server context unless specifically authorized.

 

Console & Command Use

• Run commands only for legitimate GGU operational purposes.
• Understand the expected effect before running destructive or high-impact commands.
• Do not experiment with privileged commands on production services when a safer test path exists.
• Preserve useful error output and logs when troubleshooting.

 

File Management

• Make the smallest change necessary.
• Do not overwrite large directories blindly.
• Keep configuration syntax valid.
• Verify ownership and permissions when transferring files.
• Do not upload unknown or untrusted executables/scripts to production systems.
• Do not store credentials or secret values in public repositories.

 

Backups & Recovery

High-impact changes should have a reasonable recovery path. Depending on the service, that may be a Control Center backup, database backup, repository rollback, previous configuration, container/image rollback, or another documented recovery method.

 

Auditing & Accountability

Control Center actions may be logged. Authorized users are expected to act in a way that can be understood after the fact. Do not attempt to conceal administrative actions, alter logs to avoid review, or misrepresent what changed.

 

Emergency Actions

Immediate intervention is allowed when necessary to stop active damage, abuse, data loss, compromise, or major service disruption. Emergency action should be limited to what is necessary to stabilize the situation and should be documented afterward.

 

Prohibited Use

• Using the Control Center for personal advantage, retaliation, harassment, or unauthorized experimentation.
• Accessing unrelated servers or private data without a legitimate operational reason.
• Sharing accounts or credentials.
• Granting panel access without approval.
• Deleting evidence or logs to conceal mistakes or misconduct.
• Intentionally disrupting GGU services.
• Bypassing access controls rather than requesting the permissions you actually need.

 

Access Reviews & Removal

Access should be reviewed after promotions, demotions, transfers, extended inactivity, security incidents, and departures. Permissions that are no longer required should be removed promptly.

 

Violations

Violations may result in corrective instruction, immediate access removal, suspension, demotion, removal from Leadership, removal from the community, or other action appropriate to the severity and circumstances.

 

Exceptions

Exceptions must have a legitimate operational reason and appropriate approval. High-risk exceptions should be documented.

 

Related Documentation

• Production Access & Change Management Policy
• Access Request & Permission Change Guide
• GGU Leadership Incident Response Guide
• GGU Control Center SFTP Guide

 

Use privileged access deliberately, securely, and only for GGU operations.