Base Admin Guide

Role and responsibilities

Base Admin controls the overall EoP.life Discord platform. This is separate from a Guild Admin role. Base Admins protect the communal server structure, oversee guild spaces, maintain verification and moderation, recover broken guild configurations and manage platform-wide security.

Base server roles

• Owner
• Admin
• Moderator
• EoP.life Bot
• Verified
• Public

Guild-specific roles should sit below the EoP.life Bot role when the bot needs to manage them. Guild administrators should not receive global Discord Administrator permission.

Communal channels

Guild provisioning

Each guild receives scoped roles such as <TAG> Owner, Admin, Officer and Member, plus a private category. Default channels include a lobby, general chat, voice, leadership and officers areas, with optional announcements and recruitment.

Global protections

Treat the EoP.life bot role, global administration/moderation roles, Verified/Public roles, communal channels and audit infrastructure as protected resources. Guild-level tools must not rename or remove them.

Guild onboarding

1. Confirm the intended guild and owner.
2. Provision scoped roles, category and channels.
3. Assign the owner.
4. Run the bot self-test/status checks.
5. Verify private channel visibility.
6. Publish the guild profile and recruitment state.

Recovery

Use Base Admin recovery authority when an owner leaves, bot hierarchy is broken, required resources were manually deleted, membership records drift from Discord, or a guild needs emergency deactivation. Prefer repair over rebuilding.