What a Guild Admin controls
A Guild Admin manages one guild's EoP.life space. Typical capabilities include adding/removing normal members, managing permitted promotions, creating and editing custom channels, changing channel visibility, editing guild profile and recruitment settings, reviewing applications, managing events and running membership diagnostics.
What a Guild Admin does not control
- Other guilds
- EoP.life communal channels
- Global EoP.life roles
- Global Administrator permissions
- Guild ownership
- Verification or platform security controls
Guild authority
The standard hierarchy is Guild Owner → Guild Admin → Guild Officer → Guild Member → Trial/Applicant. Only the Guild Owner or Base Admin recovery authority should grant Guild Admin.
Members
Use bot commands instead of manually assigning guild roles where possible. This keeps Discord roles and EoP.life membership records aligned. Run the membership audit after unusual manual changes.
Channels
Custom text, forum and voice channels can be scoped to Member+, Officer+, Admin+ or Owner-only access. Required/default guild resources should not be removed through generic custom-channel tools.
Recruitment
When recruitment is open, the guild can appear in the recruiting directory and users can submit applications. Guild Owner/Admin can review applications and approve or reject them.
Events
Guild Owner, Admin and Officer roles can create and manage guild events. Mark an event public only when verified EoP.life members outside the guild are genuinely welcome.
Ownership and recovery
Use the ownership transfer workflow instead of manually changing roles. If the owner disappears, use the ownerless-guild recovery process or contact Base Admin.