Staff Roles & Hierarchy
Overview of the staff structure, responsibilities, and promotion path inside CodeVerse Hub.
This page explains how the staff team at CodeVerse Hub is structured, what each role does, and how responsibilities are divided.
Entry Level
Trial Staff
The Trial Staff role is the first step into the staff team. It is given to selected or voted‑in applicants and is designed as a probation period.
Progression
- Performance is evaluated based on consistency, attitude, and initiative.
- After proving reliability, Trial Staff members can be promoted into either the Moderation or Community/Technical branches.
Moderation Branch
Moderator
Moderators are the first full moderation role and form the backbone of day‑to‑day moderation.
Moderators are expected to maintain a steady, sustainable level of activity rather than showing up for a single intense burst and then disappearing. Being present and engaged a few times each month helps them stay in touch with the community, build rapport with the rest of the team, and keep up with changes to moderation policy.
Key Responsibilities
- Enforce server rules and basic moderation actions (warnings, timeouts, etc.).
- Monitor chats for spam, harassment, or rule‑breaking behaviour.
- Escalate complex or sensitive cases to Senior Moderators or above.
- Participate in moderation discussions in the moderators channel and stay aligned with current guidelines.
Moderators are not required to also meet the separate "helper" criteria, though it is always welcome if they choose to contribute in that way as well.
Senior Moderator
Senior Moderators review and support the work of Moderators.
Key Responsibilities
- Handle stronger actions such as kicks and bans (via bots and native tools).
- Review moderator decisions, give feedback, and correct mistakes where needed.
- Act as an escalation point for difficult moderation cases.
Head Moderator
Head Moderators oversee the entire moderation team.
Key Responsibilities
- Make final calls on permanent bans in coordination with upper staff.
- Resolve disputes between staff members regarding moderation decisions.
- Coordinate moderator priorities and ensure coverage across time zones.
Community & Technical Branch
Technical Staff
Technical Staff focus on bots, automation, and internal tools.
Key Responsibilities
- Maintain and monitor community bots and integrations.
- Watch logs and alert channels for potential security or stability issues.
- Propose and test improvements to moderation and utility tools.
Community Team
The Community Team is focused on engagement and overall member experience.
Key Responsibilities
- Plan and run events, challenges, and community activities.
- Help structure threads, channels, and content for clarity and ease of use.
- Keep conversations active and welcoming across the server.
Community Manager
The Community Manager leads both Community and Technical Staff.
Key Responsibilities
- Owns the structure of non‑staff channels, categories, and permissions.
- Oversees partnerships, listings (such as Discboard/Top.gg), and external visibility.
- Coordinates changes to roles, channels, and long‑term community strategy.
Executive Branch
Head Staff
Head Staff oversee the full staff team.
Key Responsibilities
- Ensure smooth day‑to‑day operations across all branches.
- Review weekly staff activity and performance, and recommend promotions or demotions to the Owner.
- Coordinate cross‑team initiatives and decisions in management channels.
Admins
Admins are responsible for high‑impact work that directly improves the community and its infrastructure on an ongoing basis.
Key Responsibilities
- Regularly take on tasks that move the community forward (not just react to incidents).
- Review staff applications, help recruit new staff, and support onboarding.
- Review and merge pull requests that affect community resources or infrastructure.
- Participate in and help run events and community initiatives.
- Oversee road map items and track progress on longer‑term goals.
- Take ownership of critical issues, including handling raids and urgent incidents.
- Join staff/admin meetings when reasonably possible, especially if in a compatible timezone.
- Action issues raised on the organisation repository and improve internal tools or infrastructure.
- Write and maintain documentation and guides that staff and members rely on.
- Call staff votes for nominees and support fair, transparent decision‑making.
- Hold regular one‑on‑one check‑ins with Moderators when needed.
- Keep fellow Admins updated on the status of the work they are handling.
Head Admin
The Head Admin is the primary executive decision‑maker below the Owner.
Key Responsibilities
- Join staff/admin meetings as often as possible and lead those meetings.
- Help identify the most important and urgent tasks each week and distribute them across the Admin team.
- Ensure no staff member is blocked on work by missing information, decisions, or resources.
- Keep an eye on the bigger picture so that important responsibilities are not forgotten or neglected.
- Lead crisis management for major incidents (raids, mass spam, threat situations, and similar events).
- Coordinate large‑scale actions such as mass cleanup, pruning, or emergency lockdowns.
- Manage partnerships and sponsorships and act as a public representative of the community when needed.
- Serve as final point of escalation for staff issues before the Owner.
Additional Staff Roles
These roles support staff coordination and visibility.
Staff (Common Tag)
A shared role applied to all staff members to simplify pings and give access to staff‑only channels.
Management
A combined tag used for leadership roles (Head Moderator, Head Staff, Community Manager, and similar positions) to access management discussions.
If you have questions about staff roles or are interested in applying, check the staff‑applications channel or open a ticket so we can help you understand the requirements.