Deluxe Administrators

Deluxe Administrators are a fictional user-group that would serve as an extension to the Administrator user-group. The intention was to come up with a fictional user-group that would have various tools that Administrators would benefit from when performing administrative tasks, but many of which could be abused easily. In any case, many of the abilities that Deluxe Administrators have could make them more subjected to abuse due to the large scope of influence the rights have.

Inspiration
The inspiration for the fictional user-group started sometime in late October 2016 when I was thinking about certain abilities that FANDOM Staff, FANDOM Helpers, and Volunteer Spam Task Force members had that Administrators didn't have. I was toying around with this question as to which abilities I could see being added to the Administrator user-group, or as a deluxe version of the Administrator user-group that Administrators didn't have currently.

Indeed, virtually all the abilities that I had in mind were abilities that Administrators either didn't have or abilities that Administrators once had but were removed from the group due to security reasons. But I had a pretty fun time putting together a list of various tools that could be beneficial for experienced Administrators, nonetheless.

Abilities that the Deluxe Administrator user-group has
Most of the abilities included in the Deluxe Administrator user-group are abilities that weren't already included in the Administrator user-group. But there are a few abilities already included in the Administrator user-group that were subsequently included in the Deluxe Administrator user-group.

Even though this ability is already included with the Administrator user-group, I subsequently decided that Deluxe Administrators should have this ability even as a standalone group. I was inspired to do this, since Bureaucrats have the ability as a standalone group as well, and also having the ability prevents abusive Bureaucrats and Administrators from taking advantage of Deluxe Administrators, and preventing them from doing their jobs.
 * Block

Having the ability to block as a standalone group prevents abusive Bureaucrats from taking advantage of Deluxe Administrators by revoking their Administrator rights, even though Deluxe Administrators are able to add their Administrator rights back without difficulty.

Since the Deluxe Administrator user-group is only granted to highly experienced and trusted Administrators, the likelihood of Bureaucrats and Administrators needing to block them are very small. Although Bureaucrats cannot demote Deluxe Administrators by default, having the option to demote them would be granted on request.

Even though this ability is already included with the Administrator user-group, I subsequently decided that Deluxe Administrators should have this ability even as a standalone group. I was inspired to do this, since Bureaucrats have the ability as a standalone group as well, and also it prevents Deluxe Administrators from falling victim to auto-blocks, regardless if they didn't have Administrator rights.
 * Ipblock-exempt

However since the Deluxe Administrator user-group isn't be granted to any user that did not currently have Administrator rights, and since Deluxe Administrators don't normally revoke their Administrator rights without revoking their Deluxe Administrator rights, the chances of this happening are very small.

Even though this ability is already included with the Administrator user-group, I subsequently decided that Deluxe Administrators should have this ability even as a standalone group. I was inspired to do this, since Bureaucrats have the ability as a standalone group as well, and also having the ability prevents abusive Bureaucrats and Administrators from taking advantage of Deluxe Administrators, and preventing them from doing their jobs.
 * Unblockself

Having the ability to unblock themselves as a standalone group prevents abusive Bureaucrats from taking advantage of Deluxe Administrators by revoking their Administrator rights and then blocking them, since Deluxe Administrators would otherwise be unable to unblock themselves.

Since the Deluxe Administrator user-group is only granted to highly experienced and trusted Administrators, the likelihood of Bureaucrats and Administrators needing to block them is very small. Although Bureaucrats cannot demote Deluxe Administrators by default, having the option to demote them would be granted on request.

In addition to the ability to limit actions that can be preformed for some groups for a limited time with the Protectsite permission, FANDOM Staff, FANDOM Helpers, and Volunteer Spam Task Force members have the ability to be exempted from site-wide action restrictions across all wikis.
 * Protectsite-exempt

Administrators were subsequently granted the ability in April 2019. The ability existed to allow global groups to edit wikis that had Protectsite enabled, and before Administrators were granted the ability, they were automatically exempted from these restrictions locally anyway.

Deluxe Administrators were granted the ability to be exempted from site-wide action restrictions in November 2018, even if they didn't have Administrator rights, but only on individual wikis. However since the Deluxe Administrator user-group is only granted to highly experienced and trusted users that currently have Administrator rights, it is largely redundant for Deluxe Administrators to have the Protectsite-exempt permission, since they are almost always flagged as Administrators anyway.

Even though the ListGroupRights special page implies that Administrators are able to block the emails of users when blocking them, this is at least partially incorrect. Since Administrators haven't been able to block the emails of users for years. Only FANDOM Staff, FANDOM Helpers, and Volunteer Spam Task Force members seem to be able to block the emails of users.
 * Blockemail

Unlike Administrators, Deluxe Administrators were subsequently granted this ability so that they are able to successfully block the emails of of users, although the ability to block the emails of other users is now deprecated, as the ability to send emails to other users has long since been disabled. So despite having the ability as a standalone user-group, it is therefore pointless for Deluxe Administrators to have it.

Administrators and FANDOM Helpers previously had this ability until August 2015. However it was removed from both user-groups due to security reasons. From then on, only FANDOM Staff had the ability to edit and delete the personal CSS pages belonging to other users. Having Deluxe Administrator rights reinstates a user's ability to edit and delete the personal CSS pages belonging to other users.
 * Editusercss

However Deluxe Administrators shouldn't use their powers to take advantage of the way other users edit their CSS pages. Deluxe Administrators should only minor changes to the CSS pages of other users such as fixing a broken code, though they are normally expected to ask the owner of the CSS pages before making changes.

The instances where Deluxe Administrators need to edit or delete CSS pages without asking is minimal, such as removing CSS messages that are deliberately intended to attack other users, or spam CSS pages containing offensive language.

Administrators and FANDOM Helpers previously had this ability until August 2015. However it was removed from both user-groups due to security reasons. From then on, only FANDOM Staff had the ability to edit and delete the personal JavaScript pages belonging to other users. Having Deluxe Administrator rights reinstates a user's ability to edit and delete the personal JavaScript pages belonging to other users.
 * Edituserjs

However Deluxe Administrators shouldn't use their powers to take advantage of the way other users edit their JavaScript pages. Deluxe Administrators should only minor changes to the JavaScript pages of other users such as fixing a broken script that causes a lot of links to show on Special:Wantedpages.

Aside from reducing the amount of wanted pages, Deluxe Administrators are normally expected to ask the owner of the JavaScript pages before making changes. The instances where Deluxe Administrators need to edit or delete JavaScript pages without asking is minimal, such as removing JavaScript messages that are deliberately intended to attack other users, or spam JavaScript pages containing offensive language.

Administrators, Content Moderators, Bots, and Content Volunteers previously had this ability until May 2018. However it was removed from all local user-groups and Content Volunteers, due to the ability becoming more conservative due to abuse.
 * Noratelimit

FANDOM Staff, FANDOM Helpers, and Volunteer Spam Task Force members are the only remaining user-groups with the ability to be exempted from rate limits. When the ability was removed from Administrators, Content Moderators, Bots, and Content Volunteers; Global Bots were granted with the ability to be exempted from rate limits. As of May 2018, there aren't any local user-groups with the ability, excluding a few custom user-groups on certain wikis.

As with all other permissions that have been removed from Administrators since August 2015 that are still in use by some global user-groups, the ability to be exempted from rate limits was subsequently included with the Deluxe Administrator user-group as of May 2018. Since only highly experienced and trusted Administrators would be entrusted with Deluxe Administrator rights, those users would be entrusted - at least in theory - with being exempted from rate limits.

Administrators, Bureaucrats, and Admin Mentors previously had this ability until sometime in 2015. However it was removed from all user-groups, most likely because the ability doesn't have any relevance to the current code base, since account registration was overhauled.
 * Override-antispoof

As of 2015, certain custom user-groups on certain wikis, such as Assistants, are the only remaining user-groups that have the ability to override spoofing checks when renaming accounts. As such, there are no local user-groups with the permission on any wiki.

Even though Deluxe Administrators have the ability to override spoofing checks when renaming accounts, the ability doesn't have any relevance to the current code base, since account registration was overhauled. So in practice it has largely considered to have outlived its use.

This is probably one of the abilities that many Administrators would want to have the most. Administrators, Admin Mentors, FANDOM Helpers, and FANDOM Staff previously had the ability to edit all MediaWiki messages until August 2015. However most of the pages inside the MediaWiki namespace were locked, and only white-listed messages could be edited, due to security reasons.
 * Editinterfacetrusted

Editinterfacetrusted was added in August 2015 and functions the same way Editinterface did up until then, allowing users with the permission to be able to edit any messages in the MediaWiki namespace. However only Volunteer Spam Task Force members and FANDOM Utilities were granted the ability to edit all MediaWiki messages. FANDOM Helpers were subsequently granted the ability in November 2016.

I remember how disappointed and irritated I got when I first heard that Administrators were no longer able to edit all MediaWiki messages, because I felt that editing MediaWiki messages was one of the good things about being an Administrator. And it seemed like Administrators couldn't be trusted to edit MediaWiki messages in general. I was also disappointed to learn that Volunteer Spam Task Force members could still edit and restore all MediaWiki messages.

Although my disappointment never vanished entirely, it did decrease with the passage of time, and upon hearing that Volunteer Spam Task Force members had a much more limited scope and couldn't edit non-white-listed messages whenever they felt like it. But Editinterfacetrusted is obviously a permission that Deluxe Administrators should have because the key to Deluxe Administrators is to reinstate all the abilities that Administrators used to have that still exist on FANDOM in some form, along with a few other permissions that would enhance the Deluxe Administrator's ability to administrate.

While Deluxe Administrators are able to edit and restore non-white-listed messages, they should still keep an open mind as to what MediaWiki messages are white-listed, and what messages are not white-listed. So that they can be cautious around editing and restoring certain non-white-listed messages to avoid any possibilities of raising security concerns. Deluxe Administrators should also be careful to avoid editing any system messages that change the appearance of the wiki's community header and global footer, since doing that would break the customisation policy.

In addition to the ability to delete message wall messages, FANDOM Staff, FANDOM Helpers, and Volunteer Spam Task Force members are able to delete message wall messages in one click. Administrators do not have this ability on FANDOM by default, as it is intentionally only meant to be used to combat message wall spam and vandalism. The ability would be abused too easily and too frequently if Administrators were to have it by default.
 * Wallfastadmindelete

Unlike Administrators, Deluxe Administrators were subsequently granted the ability to delete message wall messages in one click. This is because Wallfastadmindelete is generally perceived as a faster option than Walladmindelete. And since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have the ability to delete message wall messages in one click.

But like the other permissions that Deluxe Administrators have that are only extended to global user-groups, Deluxe Administrators should only use the ability against obvious spam and vandalism within the message wall namespace, and not use it for simple disagreements between users that are acting in good faith.

In addition to the ability to delete and undelete pages, Volunteer Spam Task Force members are able to show and hide the contents of individual or multiple revisions, the edit summaries of the revisions, the names of the users/IP addresses that made the edits, or any combination of those three. FANDOM Utilities also have this ability. Once a revision is hidden, users without the Deleterevision permission cannot view them.
 * Deleterevision

Administrators do not have this ability on FANDOM by default, as it is intentionally only used to deal with major legal and TOU concerns. And since Staff want to keep its use limited, it isn't something that they typically grant to communities on request.

I once requested to have the ability on this very wiki, under the impression that the purpose of the tool was to delete and restore individual revisions so that users without the Deletedhistory and Deletedtext permissions couldn't view them once deleted, and users without the Undelete permission couldn't restore them. I was under the impression that it was a combination of Delete and Undelete that only focussed on one revision at a time.

My request was turned down, and it was only a matter of time before I discovered what Deleterevision actually did, and how different it was from what I thought it was and how it was used. Unlike Administrators, Deluxe Administrators have the ability to show and hide the contents of individual or multiple revisions, the edit summary of the revisions, the names of the users/IP addresses that made the edits, or any combination of those three.

I decided that Deluxe Administrators should have the Deleterevision permission when I was still under the impression that it was used to delete individual revisions so that users without the Deletedhistory and Deletedtext permissions couldn't view them once deleted, and users without the Undelete permission couldn't restore them. By the time I found out what the ability actually did, it had basically stuck as a notable permission extended to Deluxe Administrators.

Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have the ability to show and hide the contents of individual or multiple revisions, the edit summary of the revisions, the names of the users/IP addresses that made the edits, or any combination of those three.

But like the other permissions that Deluxe Administrators have that are only extended to global user-groups, Deluxe Administrators should only use the ability against edits that break the TOU or are too sensitive for users without the Deleterevision permission to stumble across. It shouldn't be used for simple disagreements between users that are acting in good faith.

Deluxe Administrators were subsequently granted an ability to select individual or multiple revisions of pages to delete, rather than deleting the entire page history. It is basically the same as deleting an entire page history and then restoring the selective revisions.
 * Multirevisiondelete

This ability doesn't actually exist anywhere on the FANDOM network, but I got the idea to create a fictional ability that is exclusive to the Deluxe Administrator user-group since I knew that such an ability wasn't already extended to Administrators or indeed any user-group, something that I have frowned upon for years. The reason such an ability doesn't exist on FANDOM is likely due to the fact that such an ability would easily create serious attribution issues and Creative Commons licence violations.

The fictional ability to select individual or multiple revisions of pages to delete, rather than deleting the entire page history basically fulfills my want for the fictional Deluxe Administrator user-group to be able to delete individual or multiple revisions of pages without having to delete the entire page history. Up until late 2017, I was under the impression that such an equivalent to the ability was already taken by the Deleterevision ability, only that it couldn't focus on more than one revision at a time.

But I eventually discovered that that wasn't the case. And that it was necessary to create a fictional ability that would do what I originally thought Deleterevision did, only that it would be able to focus on any revision that wasn't currently deleted, including the current revision. Basically the opposite of what Undelete does.

Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have the ability to select individual or multiple revisions of pages to delete, rather than deleting the entire page history. Even though Deluxe Administrators have the Editinterfacetrusted permission and can therefore restore CSS pages, as well as JavaScript pages, and non-white-listed system messages.

Deluxe Administrators should only use Multirevisiondelete to remove revisions that contain information that is too sensitive for non-administrators to stumble across. It should also be used to remove revisions where a vandal has inserted offensive language, usually language that violates FANDOM's terms of use. It shouldn't be used for simple disagreements between users that are acting in good faith.

In addition to the ability to delete pages, FANDOM Staff, FANDOM Helpers, and Volunteer Spam Task Force members are able to mass delete pages and images created by a specific user. Admin Mentors were also able to mass delete pages and images created by a specific user, prior to the user-group's retirement.
 * Nuke

Administrators do not have this ability, likely because it is only meant to be used to combat spam and vandalism. The ability would be abused too easily and too frequently if Administrators were to have it by default. Although there is a script at the FANDOM Open Source Library that allows Administrators and Content Moderators to use a reverse engineered version of the default extension of the same name.

Unlike Administrators, Deluxe Administrators were subsequently granted the ability to mass delete pages and images by default. So they are able to use both the default extension and the reverse engineered version of the extension. Deluxe Administrators have the ability to mass delete pages and images, because Nuke is generally perceived as a faster option than deleting each specific page and image individually.

Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have more enhanced delete options than Administrators. Therefore it is obvious why Deluxe Administrators have the ability to mass delete pages and images.

But like the other permissions that Deluxe Administrators have that are only extended to global user-groups, Deluxe Administrators shouldn't use Nuke for simple disagreements between users that are acting in good faith. They should only use it to delete obvious spam and vandalism.

In addition to the ability to delete pages, Volunteer Spam Task Force members are able to quickly block users, and revert and delete spam and vandalism with quick tools. FANDOM Utilities also have access to Quicktools. FANDOM Helpers were subsequently granted the ability in July 2016. Administrators do not have this ability, likely because it is only meant to be used to combat spam and vandalism.
 * Quicktools

The ability would likely be abused too easily and too frequently if Administrators were to have it by default. Although there are two scripts of the same name at the FANDOM Open Source Library that allow Administrators to do the things that the Quicktools permission can do, as well as various other things that the normal extension doesn't do, such as mass blocking users instead of just blocking them individually.

Unlike Administrators, Deluxe Administrators were subsequently granted the ability to quickly block users, and revert and delete spam and vandalism with quick tools by default. So they are able to use both the default extension and the two scripts that cover all the abilities that the default extension does, and more.

Deluxe Administrators have the ability to quickly block users, and revert and delete spam and vandalism, because Quicktools is generally perceived as a faster option than blocking users, and reverting and deleting each specific page and image individually.

Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have more enhanced delete and block options than Administrators. Therefore it is obvious why Deluxe Administrators have the ability to quickly block users, and revert and delete spam and vandalism.

But like the other permissions that Deluxe Administrators have that are only extended to global user-groups, Deluxe Administrators shouldn't use Quicktools for simple disagreements between users that are acting in good faith. They should only use it to block obvious vandals, and quickly revert and delete obvious spam and vandalism.

In addition to the ability to modify abuse filters on wikis that have abuse filters enabled, FANDOM Staff have the ability to bypass all abuse filters on all wikis that have abuse filters enabled. Administrators do not have this ability, likely because it would take away the benefit of making Administrators think twice about the rules they're implementing.
 * Abusefilter-bypass

Unlike Administrators, Deluxe Administrators were subsequently granted the ability to bypass all abuse filters on individual wikis. Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have the ability to bypass all abuse filters on individual wikis.

Even though Deluxe Administrators are able to bypass all abuse filters on individual wikis, they are still expected to think twice about the rules they're implementing. Deluxe Administrators are able to bypass all abuse filters on individual wikis so they don't have to worry about modifying the abuse filters to prevent themselves from falling victim to them. They can have their rights revoked by Staff if they are found to have abused the privilege of bypassing abuse filters.

In addition to the ability to create and edit bronze, silver, and gold badges on wikis that have achievements enabled, FANDOM Staff have the ability to create and edit platinum badges on all wikis that have achievements enabled. The reason why Administrators aren't able to create and edit platinum badges on individual wikis is unclear. Though it may be so they can't gain platinum badges by editing pages that non-administrators can't edit.
 * Platinum

Unlike Administrators, Deluxe Administrators were subsequently granted the ability to create and edit platinum badges on individual wikis. Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have more enhanced creating and editing badge abilities on individual wikis.

FANDOM Utilities have the ability to suppress thread deletion events so that other users cannot see them. Since Utilities are the only user-group with this permission, any user without Utility rights won't be able to tell that the data was even there, let alone restore it. Administrators do not have this ability, as it is only used to deal with major legal and TOU concerns. And since Staff want to keep its use limited, it isn't something that they grant to users without Utility rights.
 * Walldelete

Unlike Administrators, Deluxe Administrators were subsequently granted the ability to suppress thread deletion events. Even though they were only granted access to the ability as of December 2018, I had been toying around with the idea of giving it to Deluxe Administrators for quite some time, even though I thought that Walldelete was an overlooked duplicate of Walladmindelete, an ability that deletes threads normally so non-administrators cannot see or restore them.

In fact many users confuse Walldelete with Walladmindelete, as they both have the same summary "Can delete message wall messages" as shown on ListGroupRights. The Walladmindelete permission is extended to Administrators, Volunteer Spam Task Force members, FANDOM Helpers, and FANDOM Staff. While Walldelete is most certainly not something Staff would grant to local users, by the time I found out that Walldelete and Walladmindelete were different, it had basically stuck as a permission that I was going to extend to Deluxe Administrators.

Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have more powerful thread deletion abilities. But like the other permissions that Deluxe Administrators have that are only extended to global user-groups, Deluxe Administrators should only use the ability against messages that break the TOU or are too sensitive for users without the Walldelete or Suppressrevision permissions to stumble across. It shouldn't be used for simple disagreements between users that are acting in good faith.

None of the user-groups on FANDOM have the ability to rename categories, as the feature has never existed on FANDOM. However such a feature does exist that is part of the default Media Wiki software. The feature has never existed on FANDOM, likely because the articles containing the name of the previous category would remain unaffected. And if the same category got renamed more than once, it would result in a lot of double redirects.
 * Move-categorypages

Although there is a script at the FANDOM Open Source Library that allows users to automatically replace categories and fix category links on other pages. So using the script is actually faster and easier than it would be to use the category rename feature. Unlike other user-groups, Deluxe Administrators were subsequently granted the ability to rename categories.

Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators are able to move category pages. However they should be careful when renaming categories, to make sure that any pages linking to the old name of the category are updated.

Abilities that Deluxe Administrators have on wikis with certain extensions added
The following abilities are only extended to Deluxe Administrators on certain wikis, as they rely on specific extensions that are not enabled or used by default.

None of the user-groups on FANDOM have the ability to merge the history of two pages by default. However the ability may be available to communities on request. On wikis that have the permission granted, the ability is extended to local Administrators and FANDOM Staff. If a user was granted Deluxe Administrator rights on a wiki with Mergehistory granted, the Mergehistory permission would also be granted to users in the Deluxe Administrator user-group.
 * Mergehistory

This means that Deluxe Administrators would have the ability to merge the history of two pages even if they don't have Administrator rights on wikis with the Mergehistory permission granted. However since the Deluxe Administrator user-group is only granted to highly experienced and trusted users that currently have Administrator rights, it is largely redundant for Deluxe Administrators to have the Mergehistory permission as a standalone user-group, since they are almost always flagged as Administrators anyway.

Abilities that Deluxe Administrators previously had
Most of the abilities that were previously included in the Deluxe Administrator user-group were abilities that were removed from the Administrator user-group, as well as all other groups on all wikis.

However they were subsequently removed from the Deluxe Administrator user-group after it was decided that Deluxe Administrators should only have abilities related to extensions that still exist on the FANDOM network.

A couple of abilities relating to extensions that have been removed from the FANDOM network were also removed from the Deluxe Administrator user-group.

Administrators previously had the ability to do string replacements on the entire wiki. However the ability was removed in July 2016.
 * Replacetext

Deluxe Administrators were subsequently given the ability to do string replacements on the entire wiki in January 2018, seeing as Administrators or indeed any user-group didn't have or no longer had the ability.

However they lost the ability in May 2018 after it was decided that Deluxe Administrators shouldn't have any abilities relating to features that no longer existed on the FANDOM network.

Administrators, FANDOM Helpers, and FANDOM Staff previously had the ability to view page view statistics. However the ability was removed from all user-groups in July 2017. The Pageviews permission was from the MediaWiki page views feature which was removed in newer MediaWiki versions and never really worked properly on FANDOM.
 * Pageviews

Deluxe Administrators were subsequently have been given the ability to view page view statistics in July 2017, seeing as Administrators or indeed any user-group didn't have or no longer had the ability.

However they lost the ability in May 2018 after it was decided that Deluxe Administrators shouldn't have any abilities relating to features that no longer existed on the FANDOM network.

Administrators, Vanguards, FANDOM Helpers, and FANDOM Staff previously had the ability to view parser performance statistics. However the ability was removed from Administrators, FANDOM Helpers, and FANDOM Staff in March 2017, and Vanguards in April 2017. Admin Mentors previously had the ability, prior to the user-group's retirement.
 * Parserspeed

The reason for Parserspeed being removed was due to it not being used much and not updating. However in spite of this, Deluxe Administrators were subsequently given the ability to view parser performance statistics in April 2017, seeing as Administrators or indeed any user-group didn't have or no longer had the ability.

However they lost the ability in May 2018 after it was decided that Deluxe Administrators shouldn't have any abilities relating to features that no longer existed on the FANDOM network.

FANDOM Utilities and Volunteer Spam Task Force members previously had the ability to delete pages and protect them from being recreated by non-administrators in one click. However the ability was removed from both user-groups in May 2017. Probably because there weren't many situations where a page needed to be protected right after deleting.
 * Powerdelete

Administrators did not have this ability, likely because it was only meant to be used to combat spam and vandalism. Or it could simply have been because they didn't need it. Although there is a script at the FANDOM Open Source Library that allows Administrators and Content Moderators to delete pages and protect them from being recreated in one click. The script was published shortly before the ability was removed from all user-groups.

Unlike Administrators, Deluxe Administrators were subsequently given the ability to delete pages and protect them from being recreated in one click by default. And they continued to have the ability after it was removed from VSTF and Utilities, so they would have been able to use both the script and the default version of the ability.

Since Deluxe Administrators are meant to be a more enhanced version of Administrators, it is obvious why Deluxe Administrators have more enhanced delete options than Administrators. Therefore it is obvious why Deluxe Administrators would have had the ability to delete pages and protect them from being recreated in one click.

But like the other permissions that Deluxe Administrators have that were only extended to global user-groups, Deluxe Administrators shouldn't use Powerdelete for simple disagreements between users that are acting in good faith. They should only use it to delete obvious spam and vandalism. Deluxe Administrators lost the ability in May 2018 after it was decided that Deluxe Administrators shouldn't have any abilities relating to features that no longer existed on the FANDOM network.

Groups that Deluxe Administrators are able to add and remove from their own account
Deluxe Administrators are able to add Administrator rights to their own account, should they have their Administrator rights revoked by an abusive Bureaucrat. Deluxe Administrators that abuse their rights cannot be demoted by Bureaucrats by default, though communities would be asked whether they wanted Bureaucrats to be able to demote Deluxe Administrators before granting the rights to the users that were trusted to have Deluxe Administrator rights.
 * Administrators

Deluxe Administrators were subsequently able to remove Administrator rights from their own account, though they could already do this using their Administrator rights. The reason why Deluxe Administrators were granted the ability to remove Administrator rights from their own account is because FANDOM Staff usually try not to have user-groups that can add specific rights to their own account without removing those specific rights from their own account as well. There have been issues in the past where users couldn't remove themselves from a specific user-group.

Groups that Deluxe Administrators are able to remove from their own account
Deluxe Administrators are able to remove their Deluxe Administrator rights from their own account, though they need to be careful when doing this, as there aren't any local user-groups that are able to reinstate their Deluxe Administrator rights.
 * Deluxe Administrators

Groups that Deluxe Administrators were previously able to add or remove from other accounts
Deluxe Administrators were previously able to promote other users to Deluxe Administrators. However because of the severe consequences of misusing the abilities extended to Deluxe Administrators, and because of security reasons, their abilities to promote other users to Deluxe Administrators were removed in November 2018.
 * Deluxe Administrators

What should Deluxe Administrators do?
As with regular Administrators, Deluxe Administrators are responsible for maintaining the wiki. In addition to the abilities that come with the Administrator rights that they already have, Deluxe Administrators are able to delete message wall messages posted by spammers and vandals in one click.

They are able to make minor tweaks to other user's JavaScript pages to fix any broken JavaScript that is causing errors such as unwanted pages on Special:Wantedpages. They are able to make minor fixes to other user's CSS pages where the CSS is obviously broken and how to fix it. Though they are normally expected to contact the owner of the pages before editing them.

They are able to delete any CSS or JavaScript pages created by spammers and vandals that contain harmful JavaScript code, or any pages containing only spam or hate messages. Deluxe Administrators are able to mass delete pages created by spammers and vandals, as well as quickly block users, and revert and delete spam and vandalism.

Deluxe Administrators are able to edit all MediaWiki pages including those that are not accessible to regular administrators, allowing them to customise changes to the wiki's appearance and interface for users. Due to the lack of restriction of MediaWiki editing, they need to be careful to avoid making any changes that could potentially create security issues or break the customisation policy.

Deluxe Administrators are also able to show and hide the contents of individual or multiple revisions, the edit summaries of the revisions, the names of the users/IP addresses that made the edits, or any combination of those three. They are also able to select individual or multiple bad faith revisions of pages to delete, rather than deleting the entire page history and restoring the good revisions.

Deluxe Administrators are able to suppress thread deletion events involving blatantly malicious and TOU breaking information so that other users cannot see them. They are able to rename categories, although they should be careful to make sure that the links pointing towards the old category title and any pages that are still categorised under the old category title are updated. On wikis that have the MergeHistory permission granted, Deluxe Administrators are also able to merge the page histories of two pages.

What should Deluxe Administrators not do?
Deluxe Administrators should not use their deluxe administrator powers to settle editing disputes; for example, hide the contents of specific revisions and keep the revisions that he or she prefers in an editing dispute that isn't vandalism. Deluxe Administrator powers should be used to help keep the wiki clear of TOU breaking information and potentially harmful code, but not for simple disagreements between users acting in good faith.

Deluxe Administrators shouldn't select individual or multiple revisions of pages made by other users that weren't made in bad faith, in order to keep his or her preferred revisions at the top of the page history. They shouldn't use their fast message wall deleting abilities to quickly delete message wall messages that weren't posted in bad faith.

Deluxe Administrators shouldn't make changes to non-white-listed MediaWiki messages without consent either from the other Administrators or from the general community. They also shouldn't restore non-white-listed messages that have been voted for deletion via community consensus. Deluxe Administrators shouldn't make questionable changes to the wiki's interface that may cause security issues or customisation policy violations, deliberate or otherwise.

Deluxe Administrators shouldn't delete the CSS or JavaScript pages of other users that don't contain any malicious code or ones that don't contain spam or hate messages. They also shouldn't make changes to other user's CSS or JavaScript pages if the changes aren't constructive and/or minor such as fixing a broken code.

Deluxe Administrators shouldn't mass delete pages that weren't made in bad faith. Nor should they quickly revert or delete anything that isn't spam or vandalism. While Deluxe Administrators are able to suppress thread deletion events, they shouldn't suppress thread deletion events that don't contain any malicious or TOU breaking information.

Deluxe Administrators shouldn't be careless and rename categories without checking to make sure that the links pointing towards the old category title and any pages that are still categorised under the old category title have been updated.

On wikis with the Abuse Filter extension enabled, Deluxe Administrators shouldn't use the advantage of being able to bypass abuse filters to deliberately perform actions that have been blocked by the abuse filter. On wikis with Achievements enabled, Deluxe Administrators shouldn't create and edit platinum badges that can only be earned by editing pages that only specific user-groups can edit.

On wikis with the Mergehistory permission granted, Deluxe Administrators shouldn't merge the histories of two obviously unrelated pages. Deluxe Administrators that abuse their powers by deliberately doing any of the things that they aren't supposed to do will have their deluxe administrator status revoked by Staff.

Ideally a deluxe administrator shouldn't be considered "in charge". Nor should they be thought of as outranking regular administrators. The ideal deluxe administrator is just someone who can be trusted to have additional abilities and to use them for the benefit of the wiki community in ways that can't be done without having deluxe administrator rights.