User Rollbackers

User Rollbackers are a fictional global usergroup. The intention was to come up with a fictional global usergroup that was based around the extension of the same name. So therefore the idea was a fictional volunteer usergroup whose primary task was to quickly revert all edits made by specific users across all wikis when Fandom Staff, Fandom Helpers, and Volunteer Spam Task Force members aren't around to take bigger action against global vandals.

Inspiration
The inspiration for the fictional usergroup started sometime in February 2016 when I was researching all the usergroup rights that all the usergroups had on Fandom. I was checking the Special:ListGroupRights page in order to update my own article page that listed all the permissions that each usergroup has or had since September 2014. Then I noticed the Userrollback permission that had been added on the list of permissions that Fandom Utilities had.

There was no description on the special page as to what the permission did, and because the permission had "rollback" in its name, I became curious as to what the permission did. I knew that it must have been a permission that only Utilities should have, but that was literally it. It wasn't too long though before I was told what the permission did. To quickly revert all edits made by specific users across all wikis.

Less than five months after the permission was added to the Utility usergroup, and less than a month after I got the idea for the fictional User Rollback usergroup, the permission was removed from the Utility usergroup in April 2016. In fact the extension was removed altogether. While it was around, the extension didn't seem to be added anywhere outside Fandom Community Central.

Despite this all being in November 2015 - April 2016, past MediaWiki messages indicate that the extension dated back from June 2015 at the latest. While various archives on GitHub confirm that the extension dated back from December 2011 at the latest. Even though the idea was that the fictional volunteer usergroup would be for non-Staff, it is highly unlikely that anyone without Staff or Utility rights would be given access to the usergroup, if the usergroup existed.

Abilities that the User Rollback usergroup has
Since the User Rollback usergroup is based around the userrollback extension, it does not have many other abilities. In fact most of the abilities currently extended to User Rollbackers aren't permissions that they had at the time of the usergroup's creation.

As the User Rollback usergroup has "rollback" in its name, and since the usergroup is intended to deal with global vandalism against specific global vandals from all affected wikis, I felt that User Rollbackers should have global access to the Rollback permission. However, unlike local Administrators, Assistants, Content Moderators, and Rollbackers, User Rollbackers are only permitted to use their rollback rights on quiet or inactive wikis, and only against obvious spam and vandalism.
 * Rollback

User Rollbackers do not replace or outrank local users with rollback rights. Any users that are part of the User Rollback usergroup must have Administrator, Assistant, Content Moderator, and/or Rollback rights on a wiki in order for them to be able to use rollback for the same reasons that a local user with rollback rights would on the said wiki.

User Rollbackers were subsequently granted the ability to delete pages. However, unlike local Administrators and Content Moderators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete pages in case they ever fail to successfully delete the target pages with the Userrollback extension.
 * Delete

The code for the Userrollback extension allows access to a special page titled "Special:UserRollback" that lets a user enter a username and revert and delete their edits from all wikis. Of course, the user in question would need to have the Userrollback permission.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. But User Rollbackers still have the Delete permission, in case they ever need it. Despite having the ability to delete pages, User Rollbackers are only permitted to delete pages if for some reason they run into a page that the Userrollback extension is unable to revert and delete.

User Rollbackers were subsequently granted the ability to delete pages with large histories. However, unlike local Administrators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete pages with large histories in case they ever fail to successfully delete the target pages with the Userrollback extension, or with the Delete permission.
 * Bigdelete

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. But User Rollbackers still have the Delete and Bigdelete permissions, in case they ever need them. Despite having the ability to delete pages with large histories, User Rollbackers are only permitted to delete pages if for some reason they run into a page that the Userrollback extension is unable to revert and delete.

Administrators, Content Moderators, Bots, and Content Volunteers previously had the ability to bypass rate limits until May 2018. However it was removed from all local usergroups and Content Volunteers, due to the ability becoming more conservative due to abuse.
 * Noratelimit

Fandom Staff, Wiki Managers, Content Team Members, Fandom Helpers, and Spam Obliteration and Prevention members are the only remaining usergroups with the ability to be exempted from rate limits. Volunteer Spam Task Force members also had the ability to be exempted from rate limits, prior to the usergroup's retirement.

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 usergroups with the ability, excluding a few custom usergroups on certain wikis.

User Rollbackers were subsequently granted the ability to bypass rate limits, in case they ever ran into a situation where being unable to bypass rate limits complicates their performance with quickly reverting global vandalism. Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. But User Rollbackers still have the Noratelimit permission, in case they ever need it.

User Rollbackers lost the ability to bypass rate limits in May 2017, after it was decided that being able to bypass rate limits was irrelevant to User Rollbackers. And even if it was relevant, User Rollbackers would still have been able to bypass rate limits when using the userrollback extension. Otherwise they would still have been able to temporarily flag themselves as a Content Moderator or Assistant during that time, should they have ever needed to bypass rate limits.

If User Rollbackers still had the ability to bypass rate limits by May 2018, it is possible that they would have lost the ability, after the ability had become more conservative due to abuse. Though it is possible that since they are a volunteer group that is involved in counter vandalism globally, they may have been one of the few usergroups to have retained the ability.

Since Content Moderators no longer have the ability to bypass rate limits, and since Assistants are a custom usergroup that only exists on a couple of wikis, not to mention User Rollbackers are no longer able to flag themselves as a Content Moderator or Assistant, User Rollbackers eventually regained the ability to bypass rate limits in December 2018, to ensure that not having it didn't complicate their performance with quickly reverting global vandalism.

Fandom Staff, Wiki Managers, Fandom Helpers, Spam Obliteration and Prevention members, Global Discussion Moderators, Administrators, and Discussion Moderators have the ability to delete article and blog comments. Volunteer Spam Task Force members also previously had the ability until the usergroup's retirement in August 2020.
 * Posts : delete

User Rollbackers were granted this ability in July 2020 so that they would be able to delete article and blog comments on UCP wikis, since the ability wasn't introduced on legacy wikis until August 2020. However, unlike local Administrators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete article and blog comments since they wouldn't be able to delete article and blog comments with the Userrollback extension.

Global Discussion Moderators, Administrators, and Discussion Moderators have the ability to delete message wall messages and discussion posts.
 * Threads : delete

User Rollbackers were granted this ability in August 2020 so that they would be able to delete message wall messages and discussion posts on legacy wikis, since the ability wasn't introduced on UCP wikis until a few days after it was introduced on legacy wikis. However, unlike local Administrators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete message wall messages and discussion posts since they wouldn't be able to delete message wall messages and discussion posts with the Userrollback extension.

Fandom Staff and Fandom Helpers have the ability to view IP actions across all wikis. Volunteer Spam Task Force members also had the ability, prior to the usergroup's retirement. Wiki Managers were subsequently granted the ability in June 2019.
 * Multilookup

Spam Obliteration and Prevention members were also granted the ability, following their introduction in July 2020. User Rollbackers were subsequently granted the ability to view IP actions across all wikis, so that they would have an easier time finding and reverting edits made by a specific IP address across all wikis.

Fandom Helpers have the ability to view a user's contributions across all wikis. Fandom Staff were subsequently granted the ability sometime between December 2014 and 2015. Volunteer Spam Task Force members also had the ability, prior to the usergroup's retirement.
 * Lookupcontribs

Wiki Managers and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in May 2019 and July 2020. User Rollbackers were subsequently granted the ability to view a user's contributions across all wikis, so that they would have an easier time finding and reverting edits made by specific users across all wikis.

Fandom Utilities previously had the ability to quickly revert all edits made by specific users across all wikis. However the ability was removed from the Utility usergroup in April 2016, and the extension was removed from the Fandom network. Despite this, User Rollbackers still have access to the ability to this day, because if they didn't still have the ability, they would no longer serve their central purpose.
 * Userrollback

User Rollbackers are able to quickly revert all edits made by specific users across all wikis whenever they find a user that has engaged in cross-wiki vandalism, and there isn't a SOAP, Helper, Wiki Manager, or Staff around to take bigger action against the global vandal.

User Rollbackers don't use their Userrollback abilities for any other reason than dealing with global spam and vandalism. They do not use their Userrollback abilities against local spam or vandalism. And they do not use their Userrollback abilities against any troublesome users, global spammers, or vandals that have made any edits that aren't pure spam or vandalism.

Abilities that User Rollbackers previously had
Since the User Rollback usergroup is based around the userrollback extension, it isn't supposed to have many abilities as a standalone group. Most of the abilities that were previously included in the User Rollback usergroup were removed after it was decided that they weren't relevant to the User Rollback usergroup, they allowed them to do things or bypass restrictions that they weren't intended to be able to do or be able to bypass, or they allowed User Rollbackers to do things or bypass restrictions on local wikis that went against the best wishes of their communities.

User Rollbackers were subsequently given the ability to edit semi-protected pages, in case their account was less than 4 days old. However they lost the ability in September 2017, after it was decided that being able to edit semi-protected pages was irrelevant to User Rollbackers.
 * Autoconfirmed

Since the odds of User Rollback rights being granted to an account that was less than 4 days old were very small. And even if such odds did happen, User Rollbackers would still have been able to revert the vandalism with the userrollback extension. Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database.

Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to revert vandalism across semi-protected pages, regardless if they didn't have the Autoconfirmed permission. Otherwise they would still have been able to temporarily flag themselves as a Content Moderator or Assistant during that time, should they have been unable to revert vandalism on a semi-protected page.

User Rollbackers were subsequently given the ability to bypass CAPTCHAs, in case their account was less than 4 days old. However they lost the ability in September 2017, after it was decided that being able to bypass CAPTCHAs was irrelevant to User Rollbackers.
 * Skipcaptcha

Since the odds of User Rollback rights being granted to an account that was less than 4 days old were very small. And even if such odds did happen, User Rollbackers would still have been able to revert the vandalism with the userrollback extension. Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database.

Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to revert vandalism across articles, regardless if they didn't have the Skipcaptcha permission. Otherwise they would still have been able to temporarily flag themselves as an Assistant during that time, should they have ever needed to bypass a CAPTCHA. Otherwise they could simply check the confirmation box.

User Rollbackers were subsequently granted the ability to delete article comments. However they lost the ability in March 2020, in preparation for what would become the retirement of the article comments feature, once all wikis got migrated over to Fandom's new Unified Community Platform.
 * Commentdelete

Unlike local Administrators, Content Moderators, and Discussion Moderators, User Rollbackers were almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete article comments in case they ever failed to successfully delete article comments with the Userrollback extension.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. But User Rollbackers still had the Commentdelete permission, in case they ever needed it. Despite previously having the ability to delete article comments, User Rollbackers were only permitted to delete article comments if for some reason they ran into anything that the Userrollback extension was unable to revert and delete.

User Rollbackers were subsequently granted the ability to delete comments from blog articles. However they lost the ability in September 2020, in preparation for what would become the retirement of the article comments feature, once all wikis got migrated over to Fandom's new Unified Community Platform.
 * Blog-comments-delete

Unlike local Administrators and Discussion Moderators, User Rollbackers were almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete blog comments in case they ever failed to successfully delete the blog comments with the Userrollback extension.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. But User Rollbackers still had the Blog-comments-delete permission, in case they ever needed it. Despite previously having the ability to delete blog comments, User Rollbackers were only permitted to delete blog comments if for some reason they ran into anything that the Userrollback extension was unable to revert and delete.

User Rollbackers were subsequently granted the ability to delete message wall messages. However they lost the ability in March 2020, in preparation for what would become the retirement of the message wall feature, once all wikis got migrated over to Fandom's new Unified Community Platform.
 * Walladmindelete

Unlike local Administrators, User Rollbackers were almost never permitted to use their message wall delete tools. User Rollbackers were granted the ability to delete message wall messages in case they ever failed to successfully delete the message wall messages with the Userrollback extension.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. But User Rollbackers still had the Walladmindelete permission, in case they ever needed it. Despite previously having the ability to delete message wall messages, User Rollbackers were only permitted to delete message wall messages if for some reason they ran into anything that the Userrollback extension was unable to revert and delete.

User Rollbackers were subsequently granted the ability to remove message wall messages. However they lost the ability in March 2020, in preparation for what would become the retirement of the message wall feature, once all wikis got migrated over to Fandom's new Unified Community Platform.
 * Wallremove

Unlike local Administrators and Discussion Moderators, User Rollbackers were almost never permitted to use their message wall remove tools. User Rollbackers were granted the ability to remove message wall messages in case they ever failed to successfully delete the message wall messages with the Userrollback extension.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. But User Rollbackers still had the Wallremove permission, in case they ever needed it.

Despite previously having the ability to remove message wall messages, User Rollbackers were only permitted to remove message wall messages if for some reason they ran into anything that the Userrollback extension was unable to revert and delete, and they found themselves unable to delete a message wall message without removing it first.

User Rollbackers were subsequently given the ability to use higher limits in API queries. However they lost the ability in May 2017, after it was decided that being able to use higher limits in API queries was irrelevant to User Rollbackers. And even if it were relevant, User Rollbackers would still have been able to temporarily flag themselves as an Assistant during that time, should they have ever needed to use higher limits in API queries.
 * Apihighlimits

User Rollbackers were subsequently given the ability to override the title or username blacklist. However they lost the ability in May 2017, after it was decided that being able to override the title or username blacklist was irrelevant to User Rollbackers. And even if it were relevant, User Rollbackers would still have been able to override the title or username blacklist when using the userrollback extension.
 * Tboverride

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to revert vandalism across articles, regardless if they didn't have the Tboverride permission. Otherwise they would still have been able to temporarily flag themselves as an Assistant during that time, should they have ever needed to override the title or username blacklist.

User Rollbackers previously had the ability to bypass auto-blocks, IP-blocks, and range blocks. However they lost the ability in July 2018, after it was decided that User Rollbackers shouldn't be able to bypass auto-blocks, IP-blocks, and range blocks.
 * Ipblock-exempt

Seeing as User Rollbackers didn't have the ability to block users from editing, or the ability to manage global blocks and spam filters. Being able to bypass auto-blocks, IP-blocks, and range blocks was highly irrelevant to User Rollbackers in any case, as they would still have been able to bypass auto-blocks, IP-blocks, and range blocks when using the userrollback extension.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to bypass auto-blocks, IP-blocks, and range blocks, regardless of what permissions they had.

User Rollbackers previously had the ability to bypass automatic blocks of proxies. However they lost the ability in December 2016, after it was decided that User Rollbackers shouldn't be able to bypass automatic blocks of proxies. Seeing as User Rollbackers didn't have the ability to block users from editing, or the ability to manage global blocks and spam filters.
 * Proxyunbannable

On top of that, at the time of the fictional usergroup's creation, I imagined User Rollbackers as being like Global Rollbackers, but in Volunteer Spam Task Force form. Since VSTF didn't have the ability to bypass automatic blocks of proxies, prior to the usergroup's retirement, I felt that it was unnecessary for User Rollbackers to have it. Being able to bypass automatic blocks of proxies was highly irrelevant to User Rollbackers in any case, as they would still have been able to bypass automatic blocks of proxies when using the userrollback extension.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to bypass automatic blocks of proxies, regardless of what permissions they had.

User Rollbackers were subsequently given the ability to delete all MediaWiki messages. However, unlike local Administrators, User Rollbackers were actually almost never permitted to delete MediaWiki messages. User Rollbackers were granted the ability to delete all MediaWiki messages in case they were unable to delete MediaWiki messages that had been created by a cross-wiki spammer or vandal on a wiki where they had Administrator rights, and none of their global contributions consisted of anything other than spam and vandalism. They were also granted the ability to delete MediaWiki messages in case they ever failed to successfully delete MediaWiki messages with the Userrollback extension.
 * Deleteinterfacetrusted

Despite having the ability to delete all MediaWiki messages at one point, User Rollbackers were only permitted to delete MediaWiki messages if for some reason they ran into any messages that the Userrollback extension was unable to revert and delete. User Rollbackers lost the ability to delete MediaWiki messages in July 2018, shortly after they were granted the ability, after it was decided that User Rollbackers shouldn't have the ability to delete all MediaWiki messages if they didn't have the ability to edit MediaWiki messages.

This was also done to counter the possibility of User Rollbackers deleting MediaWiki messages with the delete button on wikis where they had Content Moderator, but not Administrator rights. However removing the Deleteinterfacetrusted permission from User Rollbackers didn't serve as much purpose as it had been intended to, as User Rollbackers can still revert and delete spam and vandalism with the userrollback extension, even if it involves reverting edits across MediaWiki pages or deleting them.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to revert and delete spam and vandalism from specific users across all wikis, regardless if they didn't have the Deleteinterfacetrusted permission.

User Rollbackers were subsequently given the ability to bypass phalanx rules, so that they would be unaffected by the spam protection filter. However they lost the ability to bypass phalanx rules in April 2017, because it was decided that User Rollbackers shouldn't be immune to global blocks.
 * Phalanxexempt

When I decided that User Rollbackers should be exempt from phalanx rules, I was unaware that they would be immune to global blocks as well. And since User Rollbackers cannot manage local blocks or global blocks, I decided that they shouldn't be immune to either of them.

Currently the only usergroups that are exempt from phalanx rules are Fandom Staff, Wiki Managers, Content Team Members, Fandom Helpers, and Spam Obliteration and Prevention members. Volunteer Spam Task Force members were also exempt from phalanx rules, prior to the usergroup's retirement.

With the exception of Content Team Members, all of these usergroups have the ability to block users locally, as well as Fandom Staff, Wiki Managers, Fandom Helpers, and Spam Obliteration and Prevention members having the ability to manage global blocks and spam filters.

Being able to bypass phalanx rules was highly irrelevant to User Rollbackers in any case, as they would still have been able to bypass phalanx rules when using the userrollback extension. Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database.

Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to bypass phalanx rules, regardless of what permissions they had.

User Rollbackers previously had the Unblockable permission which prevented them from getting blocked by Administrators and Bureaucrats on local communities. The reason User Rollbackers had this permission was so that they could revert global spam and vandalism without getting blocked on any wikis they were trying to revert global spam and vandalism on.
 * Unblockable

Even though they previously had the Unblockable permission, if any users had already been locally blocked on a community, prior to receiving User Rollback rights, they wouldn't have been able to unblock themselves, as they do not have the permission to remove any blocks placed upon their account. This is also the case with members of the Spam Obliteration and Prevention.

It was also the case with members of the Volunteer Spam Task Force, prior to the usergroup's retirement. Fandom Staff, Wiki Managers, Content Team Members, and Fandom Helpers have the Unblockself permission, so if they had been locally blocked on a wiki, prior to receiving Staff, Wiki Manager, Content Team Member, or Helper rights, they would be able to unblock themselves.

User Rollbackers lost the Unblockable permission in August 2017, after it was decided that User Rollbackers shouldn't have the Unblockable permission if they couldn't block users locally or globally. This was also done out of respect for local communities in case they didn't want certain User Rollbackers to revert any spam or vandalism there. However removing the Unblockable permission from User Rollbackers didn't serve as much purpose as it had been intended to, as User Rollbackers can still revert and delete spam and vandalism with the userrollback extension.

Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database. Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to revert and delete spam and vandalism from specific users across all wikis, regardless if they were blocked on any of them.

Groups that User Rollbackers were previously able to add or remove from other accounts
User Rollbackers were previously able to grant and revoke Rollback rights from other users on local communities. However, unlike local Bureaucrats, User Rollbackers were actually almost never permitted to add or remove Rollback rights from other users.
 * Rollbackers

User Rollbackers lost the ability to add and remove Rollback rights from other accounts on local communities in July 2017, after it was decided that User Rollbackers shouldn't be able to modify the user rights of other users on local communities.

This was also because Volunteer Spam Task Force members had recently lost the ability to add and remove Rollback and Bot rights from other accounts on local communities, and because the time of the fictional usergroup's creation, I imagined User Rollbackers as being like Global Rollbackers, but in VSTF form.

Groups that User Rollbackers were previously able to add or remove from their own account
User Rollbackers were previously able to add and remove Assistant rights to and from their own account on C.Syde's Wiki and the Encyclopedia SpongeBobia. However, unlike local Bureaucrats, User Rollbackers were actually almost never permitted to add Assistant rights to their own account. User Rollbackers had the ability to add Assistant rights to their own account, in case they ever ran into a situation where they were unable to fully revert global spam or vandalism by specific users using their User Rollback rights.
 * Assistants

User Rollbackers lost the ability to add and remove Assistant rights to and from their own account on C.Syde's Wiki and the Encyclopedia SpongeBobia in December 2018, after it was discovered that User Rollbackers didn't need to belong to any other usergroups or have any extra permissions in order to use the Userrollback extension effectively. Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database.

Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to quickly revert cross-wiki spam and vandalism from specific users across all wikis, regardless if they didn't have the Editsemiprotected permission in order to revert edits made on semi-protected pages. And regardless if they didn't have the Editprotected permission in order to revert edits made on fully protected pages.

User Rollbackers were previously able to add and remove Content Moderator rights to and from their own account on local communities. However, unlike local Bureaucrats, User Rollbackers were actually almost never permitted to add Content Moderator rights to their own account. User Rollbackers had the ability to add Content Moderator rights to their own account, in case they ever ran into a situation where they were unable to fully revert global spam or vandalism by specific users using their User Rollback rights.
 * Content Moderators

User Rollbackers lost the ability to add and remove Content Moderator rights to and from their own account on local communities in December 2018, after it was discovered that User Rollbackers didn't need to belong to any other usergroups or have any extra permissions in order to use the Userrollback extension effectively. Userrollback apparently works on the server side, so there's no notification of "user permissions", as the extension has direct access to the database.

Because the extension has direct access to the database, users with the Userrollback permission would have been able to use it to quickly revert and delete cross-wiki spam and vandalism from specific users across all wikis, regardless if they didn't have the Editprotected permission in order to revert edits made on fully protected pages. And regardless if they didn't have the Delete permission in order to delete pages created by cross-wiki spammers and vandals.

User Rollbackers were previously able to add and remove Rollback rights to and from their own account on local communities. However, unlike local Bureaucrats, User Rollbackers were actually almost never permitted to add Rollback rights to their own account.
 * Rollbackers

User Rollbackers lost the ability to add and remove Rollback rights to and from their own account on local communities in January 2018, after it was decided that it was pointless for User Rollbackers to have the ability to add Rollback rights to their own account, as they already had all the permissions extended to Rollbackers on all wikis.

Groups that User Rollbackers were previously able to remove from their own account
User Rollbackers were subsequently able to remove User Rollback rights from their own account. However, they lost the ability to remove User Rollback rights from their own account in April 2016, shortly after they were granted it.
 * User Rollbackers

User Rollbackers lost the ability to self-revoke their User Rollback rights after it was decided that fictional global usergroups shouldn't be able to remove global usergroups from their own account, seeing as most of the real global usergroups weren't self-revocable.

What do User Rollbackers do?
User Rollbackers are volunteers that are entrusted with the Userrollback permission, which allows them to quickly revert all edits made by specific users across all wikis. They use their userrollback rights to revert all contributions made by users that have spammed and vandalised on multiple wikis, as long as the said users haven't made any edits on any wikis that aren't pure spam or vandalism.

In cases where their userrollbacks fail, they may occasionally be found reverting the edits or deleting the pages that they failed to revert or delete with the Userrollback permission. But these occasions are rare and kept to a minimum. User Rollbackers may occasionally be found using their Rollback permission to revert spam and vandalism made by a user on a quiet or an inactive wiki.

In situations where the user that they have previously reverted all the edits of continues to make more spam or vandal edits, User Rollbackers will also be found on the SOAP Wiki where they report the users that are doing the cross-wiki spam or vandalism. User Rollbackers are advised to report the said users to SOAP anyway, so that the SOAP can take bigger action against the global spammers or vandals.

Sometimes User Rollbackers need to use their Multilookup permission to lookup the contributions made by a specific IP address, in order to pin down all the wikis they've hit, so they can revert all the edits that they've made. To lookup the contributions made by a specific account, User Rollbackers need to use their Lookupcontribs permission, in order to pin down all the wikis they've hit, so they can revert all the edits that they've made.

What do User Rollbackers not do?
User Rollbackers do not use their userrollback rights to revert all contributions made by users that have made any edits that aren't pure spam or vandalism. They do not use their userrollback rights to revert spam or vandalism made by a user that has only edited on one wiki. User Rollbackers do not use their deletion tools to manually delete pages unless they somehow fail to do so using the Userrollback permission.

User Rollbackers do not use the Rollback permission to revert spam or vandalism on very large or very active wikis. They do not use their rollback tool to revert spam or vandalism on wikis, unless the wikis are quiet or inactive. Or if they have previously failed to revert the spam or vandalism with the userrollback extension. They do not use the rollback tool for any other purpose. Instead they must use the undo button to undo edits, as would a regular user.

User Rollbackers generally do not revert global spam or vandalism made by users that have been reported on the SOAP Wiki. They also do not remove reports on the SOAP Wiki, since they can't block or globally block users. If a User Rollback has reverted all the edits made by specific users across all wikis, and they continue to spam or vandalise, User Rollbackers are advised not to use their Userrollback rights to revert edits made by the same users twice. Instead, they must report the spammers or vandals to the SOAP or Staff.

User Rollbackers also do not lookup the global contributions of users or IP addresses if another user asks them to. They only use their Multilookup and Lookupcontribs permissions if they need to quickly locate all the wikis where certain users or IP addresses have edited.