Wookieepedia:Administrators

This page or section is an official policy onWookieepedia. It has wide acceptance among editors and is considered a standard that everyone must follow. Please use theConsensus track to propose changes to this policy.

Wookieepedia administration
Administrators
Social Media Team
Rollback
Requests for user rights
Requests for removal of user rights
Administrators' noticeboard
Social Media Team noticeboard
Contact

Administrators are experienced and trustedWookieepedians who have been elected by the community to enforcesite policies and carry out a wide range of maintenance tasks. Administrators have "sysop rights," a set of tools that allow them todelete pages andblock users. Like every Wookieepedian, administrators are required to follow all policies, and as active community leaders, they can be contacted for advice and information about Wookieepedia.

Meet the team

Cade Calrayn administrator from September 2014 to July 2017 and since May 2023 talk page •Discord •Message Wall

---

Cade Calrayn, more commonly justCade, is an American administrator mostly known as a old wizard who lives in a tower in Texas and emerges irregularly with new dark science involving Regex, Python and Lua. He has edited the site since 2010, and primarily focuses on Old Republic era content and sitewide backend work. Since his return to the site in 2021, he has run theJocastaBot andC4-DE Bot bots that serve the Wookieepedia Discord, and plays a great deal of Final Fantasy XIV while working as a senior software engineer in his real life.

Cavalier One administrator since October 2008 talk page •Discord •Message Wall

---

Cavalier One is a British administrator who began editing Wookieepedia in 2007. A fan since seeing the original films as a kid, it was the wider Expanded Universe, starting withThe Thrawn Trilogy, that cemented his love ofStar Wars.

Cav currently focuses on working on subjects relating to the firstStar Wars roleplaying game by West End Games. The game might be over 30 years old, but Cav is still constantly finding new articles to create.

Responsibilities

Administrators are Wookieepedia users with "sysop rights," which are fully listed onSpecial:ListGroupRights. Administrators are expected to use these sysop tools to enforcesite policies on Wookieepedia, which are determined through a system ofcommunity consensus. The administration is responsible for acting in the interests of the Wookieepedia community as active leaders.

While administrators have access to certain features and are therefore responsible for maintaining them via sysop rights, the wider Wookieepedia community is encouraged to request changes, such as updating the site interface and adjusting protected templates; administrators should act on such suggestions as policies permit. Theadministrators' noticeboard is among various ways ofcontacting administrators.

TheAdministrators' how-to-guide,Administrators' reading list, andSpecial:AdminDashboard are also useful resources in carrying out administrative tasks.

AbuseFilter

• Manage the localAbuseFilter to moderate editing, such as preventing policy-breaking edits from being submitted.
• MonitorWookieepedia:Spamfilter problems and theSpecial:AbuseLog.

Blocking

• Block and unblock IP addresses, IP ranges, and user accounts for a specific time, or indefinitely, in accordance with theBlocking policy.
• CheckWookieepedia:Vandalism in progress and theSpecial:AbuseLog for situations that may require blocking users.
• Countersockpuppetry viaCheckUser.

Chat moderation

Administrators automatically receive server moderator status ("administrators" role) on Wookieepedia's officialDiscord server and have access to moderation tools on theDiscussions forum. Both platforms have additional rules, as listed onDiscord#Rules,Discussions#Rules, andDiscussions Guidelines.Bureaucrats additionally have full Discord server permissions during their tenure, including viewing and managing all private channels, but consultation channels shall be deleted upon archiving.

• Work withDiscussions moderators in moderating both the Discord server and Discussions.
• Manage bots and channel access and information on the Discord server, including use of the #announcements channel, consultation channels, andWookieeNights.
• Monitor the Discord server's audit log and #admin-help and #admin-requests channels.

Consensus

• Facilitate the democratic community consensus process by participating in theSenate Hall,Consensus track, andTrash compactor forums.
• Enforce thevoting eligibility policy on voting pages.
• Archive Senate Hall threads.
• Close votes in accordance with theConsensus policy.
• Maintain thePolicy and consensus updates page.
• Respecting and implementing community consensus and site policies, such as by updating relevant policy pages and adjusting site content as necessary.

Deletion

• Delete and restore content in accordance with theDeletion policy.
• CheckCategory:Candidates for speedy deletion for pages marked forspeedy deletion andCategory:Articles in need of verification for pages that, if left unverified, would be marked for speedy deletion as well.
• Hide edit revisions viaRevisionDelete (bureaucrats only).
• View deleted content.

Interface management

Administrators can manage theappearance and functionality of Wookieepedia to the extent allowed by Fandom'sCustomization policy by editingMediawiki pages.

• Maintain thestyle and functionality of the interface usingCSS andJavaScript (includingFandomdesktop.css,FandomMobile.css, andGadgets, accessible viaSpecial:Preferences).
• Maintain theMain Page and themain wiki navigation bar.
• Maintain theCommunity andWelcome, newcomers portals.
• Change the text ofsoftware messages seen on various pages, including thepage that blocked users see when attempting to edit, thefile upload form, and the Fandom platform–widesitedescriptions.
  • Site announcements send notifications to all users who have edited, upvoted, posted on Wookieepedia in the past 90 days.
  • Whensite notice is used, readers would see it in a pop-up box in the lower left corner across Wookieepedia.
  • WhenAnonnotice is used, logged-out readers would see it in the pop-up box instead, restricting the standard site notice (if in use) to logged-in users.

Managing partnerships

• Responsibly represent the Wookieepedia community and act in its interests, which may include coordinating with Wookieepedia'sSocial Media Team and collaborating with Fandom staff.
• Establish and promote partnerships with the widerStar Wars community, suchLucasfilm or its affiliates and charity initiatives.
• Modify the site interface, theme, and specially made pages (e.g.Wookieepedia:Star Wars: Uprising Super Walkthrough,comic previews onDiscussions, andPodathon) for the purposes of partnerships.

Moving pages

• Move pages to titles with /Legends suffix in accordance with theNaming policy.
• Automatically move all associated subpages when moving a page.
• CheckCategory:Files to be renamed and move files as appropriate.

Page protection

• Protect and unprotect pages and files in accordance with theProtection policy.
• Edit and move fully protected (sysop-only) pages and replace upload-protected (sysop-only) files.
• Check user requests for page protection onWookieepedia:Requests for protection.

Rollback

• Use theRollback tool.
• Mark Rollback editsas bot edits.
• Mentor elected Rollback users and work with them to combat vandalism.

User rights management

• Grant and remove thebot flag for users (bureaucrats only).
• Promote and demoteRollback users andDiscussions moderators in accordance withRequests for user rights andRequests for removal of user rights.
• Promote administrators andbureaucrats in accordance withRequests for user rights (bureaucrats only).
• Demote administrators in accordance withRequests for removal of user rights and theActivity requirements (bureaucrats only).

Becoming an administrator

Experienced and trusted Wookieepedians may be elected by the community to become administrators. ARequest for adminship ("RFA") lasts for two weeks and is subject to the voting requirements listed on that page, which include the nominee needing to have contributed to the site for at least one year with regular interactions with fellow users in a fair and constructive manner.

Administrators may choose to resign, be blocked due to policy violations, or be otherwise demoted in accordance withRequests for removal of user rights or theActivity requirements.

Becoming a CheckUser

CheckUsers are administrators with access to theCheckUser tool, which allows them to look up the IP addresses of registered user accounts for the purposes of combatingsockpuppetry. Fandom staff have the CheckUser tool as well.

CheckUsers are nominated throughRequests for CheckUser ("RCU") and then granted the CheckUser tool at the discretion of Fandom. The current CheckUsers are:

• DarthRuiz30
• Grunny
• OOM 224

Becoming a bureaucrat

Bureaucrats are administrators with additional powers and responsibilities. They use theRevisionDelete tool and manage user rights forbots and administrators in accordance with community consensus and policies.

Bureaucrats are elected throughRequests for bureaucratship ("RFB"). The current bureaucrats are:

• Ayrehead02
• Imperators II
• Master Fredcerique
• Spookywilloww

Activity requirements

Administrators should meet a regular level of productivity. Those who are unable should place the {{Vacation}} template or a similar message at the top of their userpage.

An administrator who does not makeat least 250 non-userspace, non–talk page edits and use their sysop tools at least once within a six-month span of their adminship is eligible for removal (bot edits count toward the edit total if the administrator is actively using a bot). However, the administrator must first be cautioned by another administrator among the administration if the requirements are not being met. They may explain their relative inactivity and provide an expected date for returning to the required activity levels. The administrator shall be warned about their activity levels if they fail to achieve the activity requirements by their specified date;demotion will occur if they fail to either provide or adhere to another explanation and expected date of return.

Also, if an administrator has not edited or used their sysop tools for four months, then attempts to communicate should be made, including a warning—which should be repeated at five months of absence—that they shall bedemoted at six months of absence.

Administrative autonomy

An administrator may not unilaterally overturn any administrative action by another administrator without a group consensus from the rest of the administration. The basis of thisadministrative autonomy policy is that administrators are responsible for enforcing site policies as a group, trusting each other with appropriately using their powers, such asdeleting articles andblocking users, to keep Wookieepedia running as smoothly as possible.

Rules

1. No single member of the administration may overturn any action by another administrator without a group consensus from the rest of the administration. The following exceptions apply:
   • Undeletion – An item may be undeleted if there iscanonical evidence to justify its existence, pursuant to theNotability policy, or if it was clearly deleted erroneously, such as a file being deleted for being unused despite the contrary. A file may also be undeleted by request if it is intended to be used.
   • Page protection – Administrative autonomy for permanent protection of any level or type expires six months after the protection's original institution. However, files and templates are partially exempt from the aforementioned requirement and may be temporarily unprotected at any time for routine maintenance and updates.
   • Partial blocks — Superseding an existingpartial block with a full block or a partial block of longer duration and/or wider scope does not count as overturning another administrator's decision under administrative autonomy.
   • Former administrators – Administrative autonomy does not apply to former administrators. With the exception ofblocks (see below), any decision by a former administrator may be overturned by a current administrator at any time.
2. Decisions approved by community consensus, such as page deletions voted through theTrash compactor process, are not affected by administrative autonomy (i.e. they should not be reversed without a community vote) as they are subject to theConsensus policy instead.

Reversing an administrator's decision

1. In the event an administrator feels that another administrator's decision should be overturned, a good-faith effort should be made to discuss the issue with them.
2. To determine whether to overturn any administrative decision, including blocks issued by a former administrator, the entire administration must be contacted (e.g. a ping onDiscord)—with each administrator asked to respond and given the opportunity to participate in relevant discussions—and come to a majority agreement. If an administrator is on a hiatus (e.g. using {{Vacation}}), the administration need not wait for outstanding responses after a period of 2 days, though a longer waiting time is recommended for non-urgent matters.

Administrative abuse

If you think an administrator has acted improperly against you or another user or otherwise violated site policies, you may express your concerns directly to the administrator responsible and attempt to resolve the issue with theDispute resolution guidance if you feel comfortable doing so. Otherwise, contact another administrator through any of the methods listed on theContact page, including via Message Wall on Fandom'sCommunity Central, which is regulated by its own staff rather than Wookieepedia administrators.

You may instead reach out to Fandom staff, such as Community ManagerSpongebob456 (Chris), in severe cases.

In extreme circumstances, administrators can be removed from their positions via aRequests for removal of user rights (RFRUR) vote.

If an administrator is blocked by another administrator, then, pursuant to administrative autonomy, the Wookieepedia administration shall vote among themselves on whether or not to overturn the block as soon as possible. The blocking administrator must not continue to issue blocks against other administrators while the vote is ongoing; otherwise, any more blocks by the blocking administrator are automatically considered invalid, and that user shall be blocked for violating this policy.

If the administration decides not to overturn the block with immediate effect, then an RFRUR must be immediately opened for the blocked administrator. Regardless of the block length, the blocked administrator shall have their user rights suspended and remain blocked for the vote's duration; if the RFRUR does not pass (i.e. the Wookieepedia communitydoes not agree on removing an administrator from their position), then the administrator should have their user rights restored and be unblocked immediately.

See also

• Wookieepedia:Administrators' how-to guide
• Wookieepedia:Administrators' reading list
• Fandom's Admin Code of Conduct
• Forum:CT:Merging Bureaucrat, CheckUser, and Administrative autonomy
• Forum:CT:Administrators page
• Forum:CT:Admin demotion loopholes follow-up
• Forum:CT:WP:AA and partial bans