This page is about the staff code of conduct. For the user code of conduct, see Project:Code of Conduct.
The Staff Code of Conduct outlines specific rules for the staff members of Robloxiapedia. These guidelines are in place because the staff team also serves as representatives of the project.
Team members must always be accountable for their actions and are expected to be familiar with the Staff Code of Conduct at all times. All staff members are prohibited from violating this code. Violations of the code of conduct can also include forcing a staff member to violate the code of conduct. Failing to comply with the code may lead to consequences, which can include reminders, strikes, or demotions.
This staff code of conduct was created as a response to a set of specific events in 2026 that demonstrated that not all staff members were mature, professional, and faithful as they once seemed at the time of their promotion, and the recent increase in abuse of staff permissions.
Please note that anything not covered by the Staff Code of Conduct is covered by Fandom's Admin Code of Conduct, effective April 15, 2025 onward.
Behaviour policies
Following rules and instructions
- As staff members, all standard rules outlined on Robloxiapedia and the project's Discord server remain in effect. This includes compliance with the Terms of Service and any global policies of the platforms we use.
- If you believe a request is unreasonable, illogical, or violates some standard rule outlined in Robloxiapedia, the Discord server, the Fandom Terms of Service, and any global policy, you have the right to ignore the request. In general, no staff member should ever be compelled to do anything they are uncomfortable with.
Treating others with respect
- Every team member is expected to treat others with respect at all times. This fundamental principle must be upheld consistently.
- Discrimination against any individual based on gender, race, sexual orientation, nationality, religion, or any other identifying characteristic is strictly prohibited. Not only does it violate the staff code of conduct, but also it violates the user code of conduct.
Using permissions fairly
- Permissions should be used appropriately and not abused. Moderation against users or their actions should only be carried out when necessary.
- All users must be treated fairly and equally. A user or a set of users should not receive unfair or unequal treatment over other users, and should be moderated just like everyone else.
- No staff member is allowed to take advantage of another user through deception, abuse of privileges, misuse of information obtained from these privileges, or any other form of unfair treatment.
- All materials provided to staff members that are not accessible to users outside the staff team must not be shared with individuals who are not part of the designated group.
Acting on behalf of the team
- Staff members should refrain from expressing opinions or similar statements on behalf of the project unless they are based on established rules or have received authorization.
- Under no circumstances may a staff member attack any individual or group in the name of the project or the staff team.
- Staff members are not allowed to change any aspects of staff rules, procedures, or settings without proper permission.[1]
Being active and communicative
- If a staff member knows they will be inactive for an extended period, they should inform the other staff members using the provided communication methods.
- If a personal activity, interest, or relationship could interfere with their ability to perform their duties as a staff member, the affected individual must notify a staff member.
- These communications are confidential and may only be shared with other a staff member or higher-level personnel (bureaucrat) if necessary to address the conflict of interest. Sharing this with other personnel and external encyclopedias without permission would result in a sanction for violating confidentiality and non-disclosure agreements. Not only is this not allowed, but also it can get you sanctioned, blocked, or banned on the encyclopedias.
Activity policies
Reaching requirements
- There are basic requirements for most positions. While the aim is for these requirements to be easily achievable, they can be reduced by submitting a Letter of Absence (LOA) notice and obtaining approval.
- The types of activities counted toward these requirements vary depending on the position and division. You can find a complete list of the base requirements on the project's staff page.
- Requirements are reviewed on the first of every month whenever possible. If that is not feasible, they will be checked as soon as possible and backdated to the first of the month.
Other policies
Rehiring of staff members
If the staff member was departed voluntarily
- All users who have voluntarily left the staff team without being demoted have a three-month period during which they can choose to rejoin the Robloxiapedia staff team.
- Within this period, they have the option to return in their previous rank without having to go through the application process again. Once this three-month period expires, they will need to follow the regular application process to rejoin.
- Bureaucrats may be able to keep their position for longer.
If the staff member was demoted
- All users who have been demoted from the staff team have the option to undergo retraining (trial moderator) within three calendar months of their demotion, during which they do not have to go through the application process, but they have to go through the training process. If the training process is passed, they get their original rank back. For lighter cases, it might be possible to apologize to the public and get a majority vote from the public before being repromoted.
- If they fail the training process while in training, reject the retraining process, or are still deciding by the time the three calendar month period expires, to get their original rank back, they have to go through the application process and the training process to get their original rank back. They will not have the option to go straight to the training process at this point.
- Users are recommended to use a part of the time to reflect on their abusive actions they performed as a staff member, and not to blame it on the demoter.
- If the user gets three demotions, at the Robloxiapedia bureaucrat's discretion, the user may be blacklisted from getting staff membership.
- Do note that if any staff member is attacked during a staff member's time as a normal user, the Robloxiapedia bureaucrat may blacklist a user without prior warning. Those blacklists can usually be resolved via an apology to the staff members affected.
If the staff member is blacklisted
- All users who have been blacklisted from staff membership cannot get staff membership on Robloxiapedia.
Sanctions for violations
Giving out sanctions
- Violations of staff rules or the Staff Code of Conduct are typically punished with staff warnings (like strikes).
- In rare or severe cases, staff strikes may be issued for other reasons if deemed necessary.
- In severe instances, individuals may also face suspension or demotion from their positions.
- In rare or severe cases, staff strikes may be issued for other reasons if deemed necessary.
- Warnings may be issued by any staff members, following this guideline:
- Staff members can warn staff members that are below their rank.[2]
- Three warnings to a staff member will usually result in them being demoted to user rather than blocked. If user keeps on accumulating warnings after this, they will be subject to sanctions that will ultimately cumulate in a block, ban, or referral.
- Receiving a strike during a trial staff membership will result in them being demoted.
- Strikes expire after six months, and to help the bureaucrat, strikes posted to an account that are >6 months old can be deleted without consequence.
- If deemed unfair, strikes may be appealed by contacting any staff member. If there is no resolution after a given period of time, the bureaucrat might settle it.