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 in early March 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 two months after the permission was added to the Utility usergroup on all wikis, 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 appear on any wikis, aside from the Community Central Wiki.

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.

Fandom Helpers, Bots, Administrators, and Assistants have the ability to bypass CAPTCHAs. Content Moderators were subsequently granted the ability in October 2020. Wiki Representatives, Wiki Specialists, Spam Obliteration and Prevention members, and Emailconfirmed Users were also granted the ability, following their respective introductions in July 2021, July 2021, July 2020, and October 2020.
 * Skipcaptcha

Fandom Staff and Autoconfirmed Users previously had the ability to bypass CAPTCHAs, prior to this wiki's migration to Fandom 's Unified Community Platform in October 2020. Volunteer Spam Task Force members also previously had the ability, prior to the usergroup's retirement. Content Volunteers were also granted the ability, following their introduction in February 2018, until June 2021.

Wiki Managers and Content Team Members were subsequently granted the ability in December 2019, prior to the usergroups' respective retirements. User Rollbackers were subsequently granted the ability to bypass CAPTCHAs in March 2016, so they wouldn't have to go through the CAPTCHA when reverting vandalism on pages after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 are able to use it to revert vandalism across articles, regardless if they don't have the Skipcaptcha permission. User Rollbackers lost the ability to bypass CAPTCHAs in September 2017, after it was decided that being able to bypass CAPTCHAs was irrelevant to User Rollbackers. Since the odds of User Rollback rights being granted to an account that didn't have a verified email address were very small. And even if such odds did happen, User Rollbackers would still have been able to revert vandalism with the Userrollback extension.

User Rollbackers eventually regained the ability to bypass CAPTCHAs in May 2022, after it was decided that they would be granted all the currently existing abilities that replicated the best possible Userrollback experience, disregarding the fact that they still have the Userrollback permission. Since the Userrollback extension automatically bypasses CAPTCHAs and all other restrictions, it was decided that they should be able to bypass CAPTCHAs even if they didn't have a verified email address or they weren't using the Userrollback extension to revert vandalism.

Fandom Staff, Fandom Helpers, Spam Obliteration and Prevention members, Vanguards, Bots, Administrators, Content Moderators, and Autoconfirmed Users have the ability to edit semi-protected pages. Assistants were subsequently granted the ability to edit semi-protected pages in October 2020. Wiki Managers and Content Team Members also had the ability to edit semi-protected pages, prior to the usergroups' respective retirements. Wiki Representatives and Wiki Specialists were also granted the ability, following their introductions in July 2021.
 * Editsemiprotected

Content Volunteers previously had the ability to edit semi-protected pages via the Autoconfirmed permission, prior to this wiki's migration to Fandom 's Unified Community Platform in October 2020. User Rollbackers were subsequently granted the ability to edit semi-protected pages in May 2022, so they wouldn't be restricted from reverting vandalism on semi-protected pages after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 Editsemiprotected permission, in case they ever need it. However since most users already implicitly have the Editsemiprotected permission via the Autoconfirmed usergroup, the chances of User Rollbackers needing the Editsemiprotected permission as a standalone group are very small. Despite having the ability to edit semi-protected pages, User Rollbackers are not permitted to perform any actions other than rollback and delete on pages that are semi-protected, unless they have Administrator, Assistant, Content Moderator, or Autoconfirmed rights.

Global Bots, Fandom Staff, Fandom Helpers, Bots, Administrators, Assistants, and Content Moderators have the ability to have their edits automatically marked as patrolled. Discussion Moderators and Rollbackers were subsequently granted the ability in July 2019. Wiki Representatives, Wiki Specialists, Spam Obliteration and Prevention members, and Autopatrolled Users were also granted the ability, following their respective introductions in July 2021, July 2021, July 2020, and July 2019. Wiki Managers and Content Team Members were also granted the ability, following their respective introductions in May and July 2019, until their respective retirements.
 * Autopatrol

Volunteer Spam Task Force members also previously had the ability, prior to the usergroup's retirement. User Rollbackers were subsequently granted the ability to have their edits automatically marked as patrolled in May 2022, so that Administrators and Content Moderators wouldn't have to manually mark their edits as patrolled whenever they reverted vandalism on wikis with the recent changes patrol extension enabled. Although in practice, all edits made with the rollback button on wikis with the recent changes patrol extension enabled are automatically marked as patrolled anyway.

Fandom Staff, Wiki Representatives, Wiki Specialists, Fandom Helpers, Administrators, and Interactive Map Testers have the ability to create and edit interactive maps. User Rollbackers were subsequently granted the ability to create and edit interactive maps in May 2022, so they wouldn't be restricted from reverting vandalism on pages in the Map namespace after failing to successfully revert vandalism on the said pages with the Userrollback extension.
 * Editinteractivemap

Userrollback 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 Editinteractivemap permission, in case they ever need it. Despite having the ability to create and edit interactive maps, User Rollbackers are not permitted to perform any actions other than rollback and delete on pages in the Map namespace, unless they have Administrator or Interactive Map Tester rights.

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 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.

Fandom Staff, Fandom Helpers, Spam Obliteration and Prevention members, Global Discussion Moderators, Administrators, Content Moderators, and Discussion Moderators have the ability to delete and undelete article and blog comments. Wiki Representatives were also granted the ability to delete and undelete article and blog comments, following their introduction in July 2021. Wiki Managers also had the ability to delete and undelete article and blog comments, prior to the usergroup's retirement. Wiki Specialists were subsequently granted the ability in December 2021.
 * Articlecomments : delete

User Rollbackers were granted the ability in June 2021, so they would be able to continue being able to delete and undelete article and blog comments after they stopped being able to delete and undelete article and blog comments via the Posts:delete permission. However, unlike local Administrators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete and undelete article and blog comments since they wouldn't be able to delete article and blog comments with the Userrollback extension.

Fandom Staff, Fandom Helpers, Spam Obliteration and Prevention members, Global Discussion Moderators, Administrators, and Discussion Moderators have the ability to delete and undelete discussion posts. Wiki Representatives were also granted the ability to delete and undelete discussion posts, following their introduction in July 2021.
 * Posts : delete

Wiki Managers and Volunteer Spam Task Force members also had the ability to delete and undelete discussion posts, prior to the usergroups' respective retirements. Content Moderators were subsequently granted the ability to delete and undelete discussion posts in November 2020. Wiki Specialists were subsequently granted the ability to delete and undelete discussion posts in December 2021.

User Rollbackers were granted the ability in July 2020 so they would be able to delete discussion posts 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 and undelete discussion posts since they wouldn't be able to delete discussion posts with the Userrollback extension.

Fandom Staff, Fandom Helpers, Spam Obliteration and Prevention members, Global Discussion Moderators, Administrators, and Discussion Moderators have the ability to delete all comments, posts and threads by a specific user. Wiki Representatives were also granted the ability to delete all comments, posts and threads by a specific user, following their introduction in July 2021. Wiki Managers and Volunteer Spam Task Force members also had the ability to delete all comments, posts and threads by a specific user, prior to the usergroups' respective retirements. Content Moderators were subsequently granted the ability to delete all comments, posts and threads by a specific user in April 2021.
 * Posts : deleteall

Wiki Specialists were subsequently granted the ability to delete all comments, posts and threads by a specific user in December 2021. User Rollbackers were granted the ability in October 2020 so they would be able to delete all comments, posts and threads by a specific user, in addition to the ability to delete and undelete article and blog comments, message wall messages, and discussion posts. However, unlike local Administrators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete all comments, posts and threads by a specific user since they wouldn't be able to delete all comments, posts and threads by a specific user with the Userrollback extension.

Global Discussion Moderators, Administrators, and Discussion Moderators have the ability to delete and undelete message wall messages. Fandom Staff, Fandom Helpers, and Spam Obliteration and Prevention members were subsequently granted the ability in October 2020. Wiki Managers and Volunteer Spam Task Force members were also subsequently granted the ability in October 2020, prior to their respective retirements.
 * Threads : delete

Content Moderators were subsequently granted the ability in April 2021. Wiki Representatives were also granted the ability, following their introduction in July 2021. Wiki Specialists were subsequently granted the ability in December 2021. User Rollbackers were granted the ability in August 2020 so they would be able to delete message wall messages 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 and undelete message wall messages since they wouldn't be able to delete message wall messages with the Userrollback extension.

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 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.

Fandom Staff, Fandom Helpers, Spam Obliteration and Prevention members, Vanguards, Administrators, and Content Moderators were subsequently granted the ability to edit protected pages without cascading protection, following this wiki's migration to Fandom 's Unified Community Platform. Wiki Managers and Content Team Members were also subsequently granted the ability around this time, prior to their respective retirements. Assistants and Content Volunteers were subsequently granted the ability to edit protected pages without cascading protection in October 2020 and June 2021, respectively.
 * Editprotected

Wiki Representatives and Wiki Specialists were also granted the ability to edit protected pages, following their introductions in July 2021. User Rollbackers were subsequently granted the ability to edit protected pages without cascading protection in May 2022, so they wouldn't be restricted from reverting vandalism on protected pages after failing to successfully revert vandalism on the said pages with the Userrollback extension.

Userrollback 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 Editprotected permission, in case they ever need it. Despite having the ability to edit protected pages, User Rollbackers are not permitted to perform any actions other than rollback and delete on pages that are fully protected, unless they have Administrator, Assistant, or Content Moderator rights.

Fandom Staff, Fandom Helpers, Administrators, Assistants, and Content Moderators have the ability to change the protection settings of pages, and edit cascade-protected pages. Vanguards were subsequently granted the ability in April 2016. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021, July 2021, and July 2020. Wiki Managers and Content Team Members were also granted the ability, following their respective introductions in May and July 2019, until their respective retirements.
 * Protect

Volunteer Spam Task Force members also had the ability to change the protection settings of pages, and edit cascade-protected pages, prior to the usergroup's retirement. Content Volunteers were also granted the ability, following their introduction in February 2018, until June 2021. User Rollbackers were subsequently granted the ability to change the protection settings of pages, and edit cascade-protected pages in May 2022, so they wouldn't be restricted from reverting vandalism on cascade-protected pages after failing to successfully revert vandalism on the said pages with the Userrollback extension.

Userrollback 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 Protect permission, in case they ever need it. Despite having the ability to change the protection settings of pages, and edit cascade-protected pages, User Rollbackers are not permitted to perform any actions other than rollback and delete on pages that are cascade-protected, unless they have Administrator, Assistant, or Content Moderator rights.

Fandom Staff, Fandom Helpers, and Administrators have the ability to edit blog articles. Bots and Assistants were subsequently granted the ability in April 2021 and April 2016, respectively. Wiki Representatives and Wiki Specialists were also granted the ability, following their introductions in July 2021. Wiki Managers and Content Team Members were also granted the ability, following their respective introductions in May and July 2019, until their respective retirements.
 * Blog-articles-edit

Content Volunteers were also granted the ability, following their introduction in February 2018, until June 2021. User Rollbackers were subsequently granted the ability to edit blog articles in May 2022, so they wouldn't be restricted from reverting vandalism on blog articles after failing to successfully revert vandalism on the said articles with the Userrollback extension.

Userrollback 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 Blog-articles-edit permission, in case they ever need it. Despite having the ability to edit blog articles, User Rollbackers are not permitted to perform any actions other than rollback and delete on blog articles, unless they have Administrator or Assistant rights.

Fandom Staff, Fandom Helpers, and Administrators have the ability to mark reverted edits as bot edits. Assistants were subsequently granted the ability in October 2017. Wiki Managers were also subsequently granted the ability in December 2019, prior to the usergroup's retirement. Wiki Representatives and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021 and July 2020. Admin Mentors and Volunteer Spam Task Force members also had the ability to mark reverted edits as bot edits, prior to the usergroups' respective retirements.
 * Markbotedits

Wiki Specialists were subsequently granted the ability in December 2021. User Rollbackers were subsequently granted the ability to mark reverted edits as bot edits in November 2020. I was inspired to do this, since all the usergroups that currently have the Quicktools permission also have the Markbotedits permission. I was inspired to give User Rollbackers the ability to mark reverted edits as Bot edits because it is one of the optional abilities that can be accessed via the Quicktools permission which User Rollbackers were granted on the same day.

However, unlike local Administrators, User Rollbackers are actually almost never permitted to mark reverted edits as bot edits. They must only mark reverted edits as bot edits through the use of Quicktools, which in turn must only be used if they fail to quickly revert all edits made by specific users with the Userrollback extension, disregarding the fact that the Userrollback extension does not have an option to mark reverted edits as bot edits.

Fandom Staff, Wiki Representatives, Wiki Specialists, Fandom Helpers, Spam Obliteration and Prevention members, and Assistants have the ability to be exempted from rate limits. Content Volunteers, Bots, Administrators, and Content Moderators also had this ability until May 2018 when it was removed from all the default local usergroups and Content Volunteers, due to the ability becoming more conservative due to abuse.
 * Noratelimit

Content Volunteers subsequently regained the ability to be exempted from rate limits in June 2021. Wiki Managers, Content Team Members, and Volunteer Spam Task Force members also had the ability to be exempted from rate limits, prior to the usergroups' respective retirements. 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 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.

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 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.

Fandom Staff, Wiki Representatives, Wiki Specialists, Fandom Helpers, and Administrators have the ability to delete interactive maps. User Rollbackers were subsequently granted the ability to delete interactive maps in May 2022, so they wouldn't be restricted from deleting vandalism in the Map namespace after failing to successfully delete the said vandalism with the Userrollback extension, or with the Editinteractivemap and Delete permissions.
 * Deleteinteractivemap

Userrollback 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 Editinteractivemap and Deleteinteractivemap permissions, in case they ever need them. Despite having the ability to delete interactive maps, User Rollbackers are only permitted to delete interactive maps if for some reason they run into a page in the Map namespace that the Userrollback extension is unable to revert and delete, unless they have Administrator rights.

Fandom Staff, Fandom Helpers, and Administrators have the ability to edit whitelisted MediaWiki messages. Wiki Representatives, Wiki Specialists, Spam Obliteration and Prevention members, and Vanguards were also granted the ability to edit whitelisted MediaWiki messages, following their respective introductions in July 2021, July 2021, July 2020, and April 2016.
 * Editinterface

Wiki Managers, Content Team Members, and Interface Administrators were also granted the ability to edit whitelisted MediaWiki messages, following their respective introductions in May 2019, July 2019, and October 2020, until their respective retirements. Volunteer Spam Task Force members and Admin Mentors also had the ability to edit whitelisted MediaWiki messages, prior to the usergroups' respective retirements. Content Volunteers were also granted the ability to edit whitelisted MediaWiki messages, following their introduction in February 2018, until June 2021.

User Rollbackers were subsequently granted the ability to edit whitelisted MediaWiki messages in May 2022, so they wouldn't be restricted from reverting vandalism on pages in the MediaWiki namespace after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 Editinterface permission, in case they ever need it.

Despite having the ability to edit whitelisted MediaWiki messages, User Rollbackers are not permitted to perform any actions other than rollback and delete on whitelisted MediaWiki messages, unless they have Administrator rights. They also aren't permitted to undelete any system messages with the Custom-٭, Editnotice-٭, Gadget-٭, Gadgets-٭, and Tag-٭ prefixes, unless they have Fandom Staff, Wiki Representative, Wiki Specialist, or Fandom Helper rights.

Fandom Staff, Fandom Helpers, Spam Obliteration and Prevention members, Vanguards, and Administrators have the ability to edit CSS pages. Wiki Managers, Content Team Members, and Interface Administrators also had the ability to edit CSS pages, prior to the usergroups' respective retirements. Wiki Representatives and Wiki Specialists were also granted the ability to edit CSS pages, following their introductions in July 2021.
 * Editsitecss

Content Volunteers also had the ability to edit CSS pages, prior to June 2021. User Rollbackers were subsequently granted the ability to edit CSS pages in May 2022, so they wouldn't be restricted from reverting vandalism on CSS pages after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 Editinterface and Editsitecss permissions, in case they ever need them.

Despite having the ability to edit CSS pages, User Rollbackers are not permitted to perform any actions other than rollback and delete on CSS pages, unless they have Administrator rights. They also aren't permitted to move or undelete any CSS pages, unless they have Fandom Staff, Wiki Representative, Wiki Specialist, or Fandom Helper rights.

Fandom Staff, Fandom Helpers, Spam Obliteration and Prevention members, Vanguards, and Administrators have the ability to edit JavaScript pages. Wiki Managers, Content Team Members, and Interface Administrators also had the ability to edit JavaScript pages, prior to the usergroups' respective retirements. Wiki Representatives and Wiki Specialists were also granted the ability to edit JavaScript pages, following their introductions in July 2021.
 * Editsitejs

Content Volunteers also had the ability to edit JavaScript pages, prior to June 2021. User Rollbackers were subsequently granted the ability to edit JavaScript pages in May 2022, so they wouldn't be restricted from reverting vandalism on JavaScript pages after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 Editinterface and Editsitejs permissions, in case they ever need them.

Despite having the ability to edit JavaScript pages, User Rollbackers are not permitted to perform any actions other than rollback and delete on JavaScript pages, unless they have Administrator rights and the wiki has community JavaScript enabled. They also aren't permitted to move or undelete any JavaScript pages, unless they have Fandom Staff, Wiki Representative, Wiki Specialist, or Fandom Helper rights.

Fandom Staff, Fandom Helpers, and Administrators have the ability to edit JavaScript Object Notation pages. Interface Administrators also had the ability to edit JavaScript Object Notation pages, prior to the usergroup's retirement. User Rollbackers were subsequently granted the ability to edit JavaScript Object Notation pages in May 2022, so they wouldn't be restricted from reverting vandalism on JavaScript Object Notation pages after failing to successfully revert vandalism on the said pages with the Userrollback extension.
 * Editsitejson

Userrollback 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 Editinterface, Editsitejson, and Editinterfacetrusted permissions, in case they ever need them. However since only Fandom Staff and Fandom Helpers are currently able to edit JavaScript Object Notation pages, the chances of User Rollbackers needing to revert vandalism on those pages are very small.

Despite having the ability to edit JavaScript Object Notation pages, User Rollbackers are not permitted to perform any actions other than rollback and delete on JavaScript Object Notation pages, unless they have Administrator rights. They also aren't permitted to edit, move, or undelete any JavaScript Object Notation pages, unless they have Fandom Staff or Fandom Helper rights.

Fandom Staff, Fandom Helpers, Spam Obliteration and Prevention members, Global Discussion Moderators, and Administrators have the ability to delete boards. Wiki Managers also had the ability to delete forum boards, prior to their retirement. Wiki Representatives were also granted the ability to delete forum boards, following their introduction in July 2021. Volunteer Spam Task Force members were also granted the ability in October 2020, prior to their retirement.
 * Forums : delete

Wiki Specialists were subsequently granted the ability in December 2021. User Rollbackers were granted this ability in June 2021 so that they would be able to delete forum boards. However, unlike local Administrators, User Rollbackers are almost never permitted to use their forum board deletion tools. User Rollbackers were granted the ability to delete forum boards since they wouldn't be able to delete forum boards with the Userrollback extension.

User Rollbackers are generally advised not to delete forum boards in general, since the only local usergroup with the abilities to create and edit forum boards are local Administrators, and User Rollbackers generally aren't supposed to deal with vandalism made by Administrators, since they aren't equipped with the necessary tools to deal with them locally or globally.

Fandom Staff, Fandom Helpers, Bureaucrats, and Administrators have the ability to bypass IP-blocks, autoblocks, and range blocks. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021, July 2021, and July 2020. User Rollbackers were granted the ability to bypass IP-blocks, autoblocks, and range blocks, so they wouldn't fall victim to IP-blocks, autoblocks, and range blocks when reverting vandalism on pages after failing to successfully revert vandalism on the said pages with the Userrollback extension.
 * Ipblock-exempt

Userrollback 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 are able to use it to revert vandalism across articles, regardless if they don't have the Ipblock-exempt permission. User Rollbackers lost the ability to bypass IP-blocks, autoblocks, and range blocks in July 2018, after it was decided that they shouldn't be able to bypass IP-blocks, autoblocks, and range blocks. Being able to bypass IP-blocks, autoblocks, and range blocks was deemed highly irrelevant to User Rollbackers in any case, as they are still able to bypass IP-blocks, autoblocks, and range blocks when using the userrollback extension.

User Rollbackers eventually regained the ability to bypass IP-blocks, autoblocks, and range blocks in May 2022, after it was decided that they would be granted all the currently existing abilities that replicated the best possible Userrollback experience, disregarding the fact that they still have the Userrollback permission. Since the Userrollback extension automatically bypasses IP-blocks, autoblocks, range blocks and all other restrictions, it was decided that they should be able to bypass IP-blocks, autoblocks, and range blocks even if they weren't using the Userrollback extension to revert vandalism.

Fandom Utilities and Check Users have the ability to check users' IP addresses and other information. Fandom Helpers and Global Discussion Moderators were subsequently granted the ability to check users' IP addresses and other information in November 2016 and May 2021, respectively. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021, July 2021, and July 2020.
 * Checkuser

Wiki Managers and Content Team Members were also granted the ability, following their respective introductions in May and July 2019, until their respective retirements. Fandom Staff were also subsequently granted this ability, following this wiki's migration to Fandom 's Unified Community Platform in October 2020. Global Check Users and Volunteer Spam Task Force members also previously had the ability, prior to the usergroups' respective retirements.

User Rollbackers were subsequently granted the ability to check users' IP addresses and other information in June 2021, so they would be able to lessen the chances of reverting global vandalism made by users and IPs that were attached to those that were already reported on the SOAP Wiki. User Rollbackers are forbidden to use their check user rights for any other reason, including check user requests.

Fandom Utilities and Check Users have the ability to view the check user log. Fandom Helpers and Global Discussion Moderators were subsequently granted the ability to view then check user log in November 2016 and May 2021, respectively. Wiki Representatives and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021 and July 2020. Wiki Managers were also granted the ability, following their introduction in May 2019, until their retirement.
 * Checkuser-log

Fandom Staff were also subsequently granted this ability, following this wiki's migration to Fandom 's Unified Community Platform in October 2020. Wiki Specialists were subsequently granted the ability in December 2021. Global Check Users and Volunteer Spam Task Force members also previously had the ability, prior to the usergroups' respective retirements. User Rollbackers were subsequently granted the ability to view the check user log in June 2021, so they would be able to see when users' IP addresses and other information were checked, and why they were checked.

In addition to the ability to create and 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. Wiki Managers and Content Team Members were also granted the ability, following their respective introductions in May and July 2019, until their respective retirements. Fandom Helpers were subsequently granted the ability to bypass all abuse filters on all wikis in August 2020.
 * Abusefilter-bypass

Wiki Representatives and Wiki Specialists were also granted the ability, following their introductions in July 2021. Spam Obliteration and Prevention members were subsequently granted the ability in January 2022. User Rollbackers were subsequently granted the ability to bypass all abuse filters in January 2022, so they wouldn't be prevented from reverting vandalism on wikis that have abuse filters enabled.

User Rollbackers likely would have been granted the permission sooner, if Spam Obliteration and Prevention members had been granted it sooner. However User Rollbackers mostly revert vandalism using the Userrollback extension which works on the server side, so there's no notification of 'user permissions', as the extension has direct access to the database. So the chances of them triggering abuse filters would be very small anyway.

Fandom Utilities have the ability to edit, move, delete, and undelete all MediaWiki messages. Fandom Helpers were subsequently granted the ability to edit, move, delete, and undelete all MediaWiki messages in November 2016. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were also granted the ability to edit, move, delete, and undelete all MediaWiki messages, following their respective introductions in July 2021, July 2021, and July 2020. Fandom Staff were also subsequently granted the ability to edit, move, delete, and undelete all MediaWiki messages, following this wiki's migration to Fandom 's Unified Community Platform in October 2020.
 * Editinterfacetrusted

Wiki Managers and Content Team Members were also granted the ability to edit, move, delete, and undelete all MediaWiki messages, following their respective introductions in May and July 2019, until their respective retirements. Volunteer Spam Task Force members also previously had the ability to edit, move, delete, and undelete all MediaWiki messages, prior to the usergroup's retirement. Administrators and Admin Mentors previously had the ability to edit, move, delete, and undelete all MediaWiki messages via the Editinterface permission until August 2015. However most of the pages inside the MediaWiki namespace were locked, and only whitelisted messages could be edited, due to security reasons.

Editinterfacetrusted was added in August 2015 and functions the same way Editinterface did up until then, allowing users to edit, move, delete, and undelete any messages in the MediaWiki namespace. However only Fandom Utilities and Volunteer Spam Task Force members were immediately granted the ability to edit, move, delete, and undelete all MediaWiki messages, while Administrators regained the ability to delete all MediaWiki messages with the Deleteinterfacetrusted permission in November 2015. User Rollbackers were subsequently granted the ability to edit, move, and delete all MediaWiki messages in May 2022, so they wouldn't be restricted from reverting vandalism on all pages in the MediaWiki namespace after failing to successfully revert vandalism on the said pages with the Userrollback extension.

Userrollback 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 Editinterface and Editinterfacetrusted permissions, in case they ever need them. However since only Fandom Staff, Wiki Representatives, Wiki Specialists, Fandom Helpers, and Spam Obliteration and Prevention members are currently able to edit, move, and undelete all MediaWiki messages, the chances of User Rollbackers needing to revert vandalism on those pages are very small.

Despite having the ability to edit, move, and delete all MediaWiki messages, User Rollbackers are not permitted to perform any actions other than rollback and delete on non-whitelisted MediaWiki messages, unless they have Administrator rights. They also aren't permitted to undelete any system messages with the Custom-٭, Editnotice-٭, Gadget-٭, Gadgets-٭, and Tag-٭ prefixes, or edit, move, or undelete any non-whitelisted MediaWiki messages unless they have Fandom Staff, Wiki Representative, Wiki Specialist, or Fandom Helper rights.

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. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021, July 2021, and July 2020.
 * Lookupcontribs

Wiki Managers and Content Team Members were also granted the ability, following their respective introductions in May and July 2019, until their respective retirements. 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 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 also subsequently granted the ability in June 2019, until their retirement.
 * Multilookup

Wiki Representatives and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021 and July 2020.

Wiki Specialists were subsequently granted the ability in December 2021. 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.

In addition to the ability to delete pages, Fandom Staff and Fandom Helpers are able to mass delete pages and images created by a specific user. Volunteer Spam Task Force members also had the ability, prior to the usergroup's retirement. Wiki Managers and Content Team Members were subsequently granted the ability in December 2019, until their respective retirements. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were granted the ability, following their introductions in July 2021, July 2021, and July 2020.
 * Nuke

User Rollbackers were subsequently granted the ability to mass delete pages and images created by a specific user in July 2021. I was inspired to grant them the ability as an alternative in case they ever failed to quickly revert all edits made by specific users with the Userrollback extension. Both extensions are similar in some ways. Both allow users to mass delete pages and images created by a specific user.

Though the purpose of the Userrollback extension is to revert all edits by specified users on all the wikis they've targeted and delete all pages and images they've created, whereas Nuke can only be used to mass delete pages and images created by a specific user. It can only be used locally. Userrollback does not require any additional permissions to use, since it works on the server side, so there's no notification of 'user permissions', as the extension has direct access to the database. Nuke requires the Delete permission to delete pages. Userrollback didn't appear on any wikis, aside from the Community Central Wiki. Whereas Nuke appears on all wikis.

Before User Rollbackers were granted the ability to mass delete pages and images by default, they would have been able to mass delete pages and images by a specific user with a script at the Fandom Developers Wiki that allows Administrators and Content Moderators to use a reverse engineered version of the default extension of the same name.

Fandom Staff and Fandom Helpers have the ability to bypass phalanx rules. Volunteer Spam Task Force members also had the ability, prior to the usergroup's retirement. Wiki Managers and Content Team Members were also granted the ability, following their respective introductions in May and July 2019, until their respective retirements. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021, July 2021, and July 2020.
 * Phalanxexempt

User Rollbackers were subsequently granted the ability to bypass phalanx rules in November 2016, so they wouldn't be affected by the spam protection filter when reverting vandalism on pages after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 are able to use it to revert vandalism across articles, regardless if they don't have the Phalanxexempt permission.

User Rollbackers lost the ability to bypass phalanx rules in April 2017, after it was discovered that the permission made them immune to global blocks which wasn't what I had intended for them. Since User Rollbackers cannot manage local blocks or global blocks, I decided that they shouldn't be immune to them either. Being able to bypass phalanx rules was deemed highly irrelevant to User Rollbackers in any case, as they are still able to bypass phalanx rules when using the userrollback extension.

User Rollbackers eventually regained the ability to bypass phalanx rules in May 2022, after it was decided that they would be granted all the currently existing abilities that replicated the best possible Userrollback experience, disregarding the fact that they still have the Userrollback permission. Since the Userrollback extension automatically bypasses phalanx rules, it was decided that they should be able to bypass phalanx rules even if they weren't using the Userrollback extension to revert vandalism.

In addition to the ability to delete pages, Fandom Helpers were subsequently granted the ability to quickly block users, and revert and delete spam and vandalism with quick tools in July 2016. Wiki Managers and Content Team Members were also granted the ability, following their respective introductions in May and July 2019, until their respective retirements. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were also granted the ability, following their respective introductions in July 2021, July 2021, and July 2020.
 * Quicktools

Fandom Staff were also subsequently granted this ability, following this wiki's migration to Fandom 's Unified Community Platform in October 2020. Volunteer Spam Task Force members were also previously able to quickly block users, and revert and delete spam and vandalism with quick tools, prior to the usergroup's retirement. Fandom Utilities also previously had access to Quicktools, prior to this wiki's migration to UCP. However they weren't able to quickly block users, and revert and delete spam and vandalism as a standalone usergroup, as those actions required the Block, Rollback, and Delete permissions which Utilities didn't have.

User Rollbackers were subsequently granted the ability to quickly revert and delete spam and vandalism with quick tools in November 2020. I was inspired to grant them the ability as an alternative in case they ever failed to quickly revert all edits made by specific users with the Userrollback extension. Both extensions are similar in some ways. Both allow users to quickly revert and delete spam and vandalism. Though the Userrollback extension can be used to revert all edits by specified users on all the wikis they've targeted, whereas Quicktools can only be used locally.

Userrollback does not require any additional permissions to use, since it works on the server side, so there's no notification of 'user permissions', as the extension has direct access to the database. Quicktools requires the Rollback permission to revert edits, the Markbotedits permission to mark reverted edits as bot edits, the Delete permission to delete pages, the Block permission to block users, and the Blockemail permission to block the emails of users when blocking them. Userrollback couldn't be used to mark reverted edits as bot edits, delete pages, block users, or block emails. And it didn't appear on any wikis, aside from Fandom Community Central.

Fandom Staff and Fandom Helpers have the Unblockable permission which prevents them from getting blocked by Administrators and Bureaucrats on local communities. Volunteer Spam Task Force members also had the permission, prior to the usergroup's retirement. Wiki Managers and Content Team Members were also granted the permission, following their respective introductions in May and July 2019, until their respective retirements. Wiki Representatives, Wiki Specialists, and Spam Obliteration and Prevention members were also granted the permission, following their respective introductions in July 2021, July 2021, and July 2020. User Rollbackers were granted the Unblockable permission so they wouldn't be prevented from reverting cross-wiki vandalism after failing to successfully revert the vandalism with the Userrollback extension. Userrollback 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 are able to use it to revert cross-wiki vandalism, regardless if they are blocked on any of the wikis they are reverting vandalism on.
 * Unblockable

User Rollbackers lost the Unblockable permission in August 2017, after it was decided that they 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 vandalism there. However removing the Unblockable permission from User Rollbackers didn't serve as much purpose as it had been intended to, as they could still revert and delete vandalism with the userrollback extension. User Rollbackers eventually regained the Unblockable permission in May 2022, after it was decided that they would be granted all the currently existing abilities that replicated the best possible Userrollback experience, disregarding the fact that they still have the Userrollback permission. Since the Userrollback extension can be used to revert vandalism on wikis that the user has been blocked on, it was decided that they should be able to revert vandalism without the risk of getting blocked even when they aren't using the Userrollback extension to revert vandalism.

Even though User Rollbackers have the unblockable permission, if any users had already been locally blocked on a community, prior to receiving User Rollback rights, they wouldn't be able to unblock themselves, as they don't 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 Representatives, Wiki Specialists, and Fandom Helpers have the Unblockself permission, so if they were locally blocked on a wiki, prior to receiving Staff, Wiki Representative, Wiki Specialist, or Helper rights, they would be able to unblock themselves. This was also the case with Wiki Managers and Content Team Members, prior to their respective retirements.

Fandom Staff have the ability to edit and  pages. Wiki Managers also had the ability, prior to the usergroup's retirement. Fandom Helpers, Spam Obliteration and Prevention members, Vanguards, Content Volunteers, Interface Administrators, and Administrators were able to edit FandomMobile.css and FandomMobile.js pages via the Editinterface, Editsitecss, and Editsitejs permissions, prior to the introduction of the Edit-fandommobile-customizations permission. Fandom Helpers were subsequently granted the ability to edit FandomMobile.css and FandomMobile.js pages in May 2021.
 * Edit-fandommobile-customizations

Wiki Representatives were also granted the ability to edit FandomMobile.css and FandomMobile.js pages, following their introduction in July 2021. Wiki Specialists were subsequently granted the ability to edit FandomMobile.css and FandomMobile.js pages in December 2021. User Rollbackers were subsequently granted the ability to edit FandomMobile.css and FandomMobile.js pages in May 2022, so they wouldn't be restricted from reverting vandalism on FandomMobile.css and FandomMobile.js pages after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 Editinterface, Editsitecss, Editsitejs, and Edit-fandommobile-customizations permissions, in case they ever need them. However since only Fandom Staff, Wiki Representatives, Wiki Specialists, and Fandom Helpers are currently able to edit FandomMobile.css and FandomMobile.js pages, the chances of User Rollbackers needing to revert vandalism on those pages are very small. Despite having the ability to edit FandomMobile.css and FandomMobile.js pages, User Rollbackers are not permitted to perform any actions other than rollback and delete on FandomMobile.css and FandomMobile.js, unless they have Fandom Staff, Wiki Representative, Wiki Specialist, or Fandom Helper rights.

Fandom Staff have the ability to edit, move, delete, and undelete the personal CSS pages belonging to other users. Fandom Helpers and Administrators previously had the ability until August 2015 when it was removed from both usergroups due to security reasons. Interface Administrators also previously had the ability, following their introduction in October 2020, until October 2021 when it was also removed from Interface Administrators due to security reasons. Fandom Helpers subsequently regained the ability to edit, move, delete, and undelete the personal CSS pages belonging to other users in August 2020.
 * Editusercss

Administrators subsequently regained the ability to delete the personal CSS pages belonging to other users in October 2020. User Rollbackers were subsequently granted the ability to edit, move, and delete the personal CSS pages belonging to other users in May 2022, so they wouldn't be restricted from reverting vandalism on the personal CSS pages belonging to other users after failing to successfully revert vandalism on the said pages with the Userrollback extension.

Userrollback 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 Editusercss permission, in case they ever need it. However since only Fandom Staff and Fandom Helpers are currently able to edit, move, and undelete the personal CSS pages belonging to other users, the chances of User Rollbackers needing to revert vandalism on those pages are very small.

Despite having the ability to edit, move, and delete the personal CSS pages belonging to other users, User Rollbackers are not permitted to perform any actions other than rollback and delete on personal CSS pages belonging to other users, unless they have Administrator rights. They also aren't permitted to edit, move, or undelete any personal CSS pages belonging to other users, unless they have Fandom Staff or Fandom Helper rights.

Fandom Staff have the ability to edit, move, delete, and undelete the personal JavaScript pages belonging to other users. Fandom Helpers and Administrators previously had the ability until August 2015 when it was removed from both usergroups due to security reasons. Interface Administrators also previously had the ability, following their introduction in October 2020, until October 2021 when it was also removed from Interface Administrators due to security reasons. Fandom Helpers subsequently regained the ability to edit, move, delete, and undelete the personal JavaScript pages belonging to other users in August 2020.
 * Edituserjs

Administrators subsequently regained the ability to delete the personal JavaScript pages belonging to other users in October 2020. User Rollbackers were subsequently granted the ability to edit, move, and delete the personal JavaScript pages belonging to other users in May 2022, so they wouldn't be restricted from reverting vandalism on the personal JavaScript pages belonging to other users after failing to successfully revert vandalism on the said pages with the Userrollback extension.

Userrollback 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 Edituserjs permission, in case they ever need it. However since only Fandom Staff and Fandom Helpers are currently able to edit, move, and undelete the personal JavaScript pages belonging to other users, the chances of User Rollbackers needing to revert vandalism on those pages are very small.

Despite having the ability to edit, move, and delete the personal JavaScript pages belonging to other users, User Rollbackers are not permitted to perform any actions other than rollback and delete on personal JavaScript pages belonging to other users, unless they have Administrator rights. They also aren't permitted to edit, move, or undelete any personal JavaScript pages belonging to other users, unless they have Fandom Staff or Fandom Helper rights.

Fandom Staff and Fandom Helpers have the ability to edit, move, delete, and undelete the personal JavaScript Object Notation pages belonging to other users. Interface Administrators and Administrators previously had the ability until October 2021 when it was removed from both usergroups due to security reasons. User Rollbackers were subsequently granted the ability to edit, move, and delete the personal JavaScript Object Notation pages belonging to other users in May 2022, so they wouldn't be restricted from reverting vandalism on the personal JavaScript Object Notation pages belonging to other users after failing to successfully revert vandalism on the said pages with the Userrollback extension.
 * Edituserjson

Userrollback 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 Edituserjson permission, in case they ever need it. However since only Fandom Staff and Fandom Helpers are currently able to edit, move, and undelete the personal JavaScript Object Notation pages belonging to other users, the chances of User Rollbackers needing to revert vandalism on those pages are very small.

Despite having the ability to edit, move, and delete the personal JavaScript Object Notation pages belonging to other users, User Rollbackers are not permitted to perform any actions other than rollback and delete on personal JavaScript Object Notation pages belonging to other users, unless they have Administrator rights. They also aren't permitted to edit, move, or undelete any personal JavaScript Object Notation pages belonging to other users, unless they have Fandom Staff or Fandom Helper rights.

Fandom Staff, Wiki Representatives, Wiki Specialists, and Fandom Helpers have the ability to create and edit widgets in the Widget namespace. Administrators were previously able to create and edit widgets in the Widget namespace on wikis that have the Widgets extension enabled via the Editwidgets permission. However the ability to create and edit widgets in the Widget namespace has since been restricted to Fandom Staff, Wiki Representatives, Wiki Specialists, and Fandom Helpers. And in any case, the Widgets extension is currently in the process of being removed from the Fandom platform.
 * Editwidget

User Rollbackers were subsequently granted the ability to create and edit widgets in the Widget namespace in May 2022, so they wouldn't be restricted from reverting vandalism on pages in the Widget namespace after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 Editwidget permission, in case they ever need it.

However since the Widget namespace only exists on wikis that have the Widgets extension enabled, and since only Fandom Staff, Wiki Representatives, Wiki Specialists, and Fandom Helpers are able to edit that namespace on those wikis, the chances of User Rollbackers needing to revert vandalism on those pages are very small. Despite having the ability to create and edit widgets in the Widget namespace, User Rollbackers are not permitted to perform any actions other than rollback and delete on pages in the Widget namespace on wikis with the Widgets extension enabled, unless they have Fandom Staff, Wiki Representative, Wiki Specialist, or Fandom Helper rights.

Fandom Helpers have the ability to edit the system message to maintain allowed regular expressions and patterns on wikis with Semantic MediaWiki enabled. Wiki Managers were subsequently granted the ability to edit the Smw allows pattern system message in December 2019, prior to the usergroup's retirement. Wiki Representatives were also granted the ability to edit the Smw allows pattern system message, following their introduction in July 2021. Fandom Staff and Administrators also previously had the ability, prior to this wiki's migration to Fandom 's Unified Community Platform in October 2020.
 * Smw-patternedit

Wiki Specialists were subsequently granted the ability in December 2021. The reason Fandom Staff and Administrators no longer have this ability is because the Semantic MediaWiki extension has not been enabled on most wikis. Though that doesn't explain why they don't have the permission on wikis with Semantic MediaWiki enabled. User Rollbackers were subsequently granted the ability on wikis with Semantic MediaWiki enabled in May 2022, so they wouldn't be restricted from reverting vandalism on the Smw allows pattern system message after failing to successfully revert vandalism on the said page with the Userrollback extension.

Userrollback 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 Smw-patternedit permission, in case they ever need it. As it turns out, they are able to edit the Smw allows pattern system message on wikis that have Semantic MediaWiki added to them anyway, via the Editinterface permission.

Since only Wiki Representatives, Wiki Specialists, and Fandom Helpers currently have the ability to edit the Smw allows pattern system message on wikis that have Semantic MediaWiki added to them, the chances of User Rollbackers needing to revert vandalism on that page are very small. Despite having the ability to edit the Smw allows pattern system message on wikis that have Semantic MediaWiki enabled, User Rollbackers are not permitted to perform any actions other than rollback and delete on the Smw allows pattern system message on wikis that have Semantic MediaWiki enabled, unless they have Wiki Representative, Wiki Specialist, or Fandom Helper rights.

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 Specialist, Wiki Representative, or Staff member 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 vandalism. They do not use their Userrollback abilities against local vandalism. And they do not use their Userrollback abilities against any troublesome users or global vandals that have made any edits that aren't pure vandalism.

None of the usergroups on Fandom wikis have the ability to edit gadget definitions. However the permission does exist on Fandom's Unified Community Platform. The reason none of the usergroups on Fandom UCP wikis with the Gadgets extension enabled have the ability to edit gadget definitions is because the gadget definition namespace doesn't do anything. The gadget definition namespace was added by the gadgets extension for planned development that never happened to this day.
 * Gadgets-definition-edit

User Rollbackers were subsequently granted the ability to edit gadget definitions in May 2022, so they wouldn't be restricted from reverting vandalism on pages in the Gadget definition namespace after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 Gadgets-definition-edit permission, in case they ever need it.

However since the Gadget definition namespace only exists on wikis that have the Gadgets extension enabled, and since none of the usergroups are able to edit gadget definitions on those wikis, the chances of User Rollbackers needing to revert vandalism on gadget definitions are very small. Despite having the ability to edit gadget definitions, User Rollbackers are not permitted to perform any actions other than rollback and delete on pages in the Gadget definition namespace on wikis with the Gadgets extension enabled, unless they have Fandom Staff rights.

None of the usergroups on Fandom wikis have the ability to edit gadget CSS and JavaScript pages. However the permission does exist on Fandom's Unified Community Platform. The reason none of the usergroups on Fandom UCP wikis with the Gadgets extension enabled have the ability to edit gadget CSS and JavaScript pages is because the gadget namespace doesn't do anything. The gadget namespace was added by the gadgets extension for planned development that never happened to this day.
 * Gadgets-edit

User Rollbackers were subsequently granted the ability to edit gadget CSS and JavaScript pages in May 2022, so they wouldn't be restricted from reverting vandalism on pages in the Gadget namespace after failing to successfully revert vandalism on the said pages with the Userrollback extension. Userrollback 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 Gadgets-edit permission, in case they ever need it.

However since the Gadget namespace only exists on wikis that have the Gadgets extension enabled, and since none of the usergroups are able to edit gadget CSS and JavaScript pages on those wikis, the chances of User Rollbackers needing to revert vandalism on gadget CSS and JavaScript pages are very small. Despite having the ability to edit gadget CSS and JavaScript pages, User Rollbackers are not permitted to perform any actions other than rollback and delete on pages in the Gadget namespace on wikis with the Gadgets extension enabled, unless they have Fandom Staff rights.

User Rollbackers were subsequently granted an ability to edit pages in restricted namespaces, without needing any of the permissions listed under the namespace restrictions section of the ListGroupRights special page. They are supposed to be able to revert vandalism in all namespaces on all wikis with few exceptions, usually hidden wikis like the Community Council Wiki. Therefore, I wanted to ensure that User Rollbackers would be able to revert vandalism in all namespaces on wikis with custom namespace restrictions added, if they fail to successfully revert vandalism in the said namespaces with the Userrollback extension. Userrollback works on the server side, so there's no notification of 'user permissions', as the extension has direct access to the database.
 * Namespaceprotection-bypass

But User Rollbackers still have the ability to edit pages in restricted namespaces, in case they ever need to revert vandalism in those namespaces without the Userrollback extension, and are missing the required permissions to edit in those namespaces. The ability to edit pages in restricted namespaces ensures that even without the Editinterface, Editwidget, Gadgets-edit, Gadgets-definition-edit, and Editinteractivemap permissions, User Rollbackers are still able to revert vandalism in the MediaWiki, Widget, Gadget, Gadget definition, and Map namespaces. Even though they are able to edit pages in restricted namespaces, they still require additional permissions to edit certain pages in certain namespaces, if those said permissions don't appear under the namespace restriction section of the ListGroupRights special page.

For example, the Editinterfacetrusted permission is still required to edit unwhitelisted system messages. The Editsitecss permission is still required to edit sitewide CSS pages. The Editsitejs permission is still required to edit sitewide JavaScript pages. The Editinterfacetrusted and Editsitejson permissions are still required to edit sitewide JavaScript Object Notation pages. The Editsitecss and Edit-fandommobile-customizations permissions are still required to edit pages. And the Editsitejs and Edit-fandommobile-customizations permissions are still required to edit pages.

None of the usergroups on Fandom wikis that use MediaWiki 1.33.3 have the ability to view social logs, as the permission has never existed on that version of MediaWiki. However the permission's purpose is covered by the Discussionslog:view permission on wikis that use MediaWiki 1.33.3, which is extended to Fandom Staff, Fandom Helpers, and Spam Obliteration and Prevention members. Global Discussion Moderators were subsequently granted the Discussionslog:view permission in June 2021. Wiki Representatives were also granted the Discussionslog:view permission, following their introduction in July 2021.
 * Sociallogs

Wiki Managers and Volunteer Spam Task Force members also had the Discussionslog:view permission, prior to their respective retirements. Wiki Specialists were subsequently granted the Discussionslog:view permission in December 2021. Though the Discussionslog:view permission functions the same way on wikis that use MediaWiki 1.37.2 as it does on wikis that use MediaWiki 1.33.3, the system messages associated with the Discussionslog:view permission on wikis that use MediaWiki 1.33.3 are associated with the Sociallogs permission on wikis that use MediaWiki 1.37.2 instead.

This implies that the Discussionslog:view permission will be removed and its abilities will be transferred to the Sociallogs permission in the near future. User Rollbackers were granted the ability to view social logs in April 2022, so they would continue being able to view the Special:SocialLogs page after the Discussionslog:view permission is removed and replaced with the Sociallogs permission. They were granted the ability to view social logs, so they would be able to lessen the chances of reverting global vandalism made by users whose IP addresses had already been reported on the SOAP Wiki. User Rollbackers are forbidden to use their social log access rights for any other reason, including check user requests.

Fandom Staff and Fandom Helpers have the ability to view blacklisted spam filter entries via the Phalanx permission. Volunteer Spam Task Force members also had the ability, prior to the usergroup's retirement. Wiki Managers were subsequently granted the ability in December 2019, prior to the usergroup's retirement. Wiki Representatives and Spam Obliteration and Prevention members were also granted the ability, following their introductions in July 2021 and July 2020. Wiki Specialists were subsequently granted the ability in December 2021.
 * Spamfilter-view

User Rollbackers were subsequently granted an ability to view spam protection filters. However unlike the Phalanx permission, the Spamfilter-view ability would not allow users to manage global blocks or spam filters. The reason I subsequently decided that User Rollbackers should have an ability to view the entries of spam protection filters was so they would hopefully keep instances of performing actions that would otherwise trigger the spam protection filter to a minimum.

However since User Rollbackers are there to revert vandalism made by global vandals, the chances of them needing to bypass spam protection filters or view them are very small. And in any case, User Rollbackers mostly revert vandalism using the Userrollback extension which works on the server side, so there's no notification of 'user permissions', as the extension has direct access to the database. Which further decreases the chances of them doing things that would otherwise trigger the spam protection filter.

User Rollbackers can have their rights revoked by Staff if they are found to have abused the privilege of viewing spam protection filters in order to deliberately do things that would not only have triggered the spam protection filter but are in violation of Fandom's terms of use. Although in practice many users that would be part of the User Rollback group would probably also be Staff anyway.

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 vandalised on multiple wikis, as long as the said users haven't made any edits on any wikis that aren't pure vandalism. In cases where their userrollbacks fail, they are able to revert edits or delete pages that they failed to revert or delete with the Userrollback permission.

They are able to revert the edits to or delete pages including interactive maps, sitewide CSS, JavaScript pages, and JavaScript Object Notation pages, MediaWiki pages, widgets, gadget definitions, gadget JavaScript and CSS pages, semi-protected, fully protected, and cascade-protected pages, and other users' blog articles, CSS pages, JavaScript pages, and JavaScript Object Notation pages. But these occasions are rare and kept to a minimum. User Rollbackers may revert and delete vandalism made by a user on a quiet or inactive wiki.

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

User Rollbackers are able 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. They are able to lookup the contributions made by a specific account, in order to pin down all the wikis they've hit, so they can revert all the edits that they've made.

User Rollbackers are able to check whether a user or IP address whose global vandalism they are about to revert is attached to an account or IP address that has already been reported on the SOAP wiki, to avoid dealing with global vandalism made by users and IP addresses that have already been reported. They are able to view the checkuser log to see when users' IP addresses and other information were checked, and why they were checked.

Since User Rollbackers cannot use their userrollback rights to delete article and blog comments, message wall messages, and discussion posts, they are able to delete all the article and blog comments, message wall messages, and discussion posts of a specific user by going onto their contributions page. They are able to view blacklisted entries on the Special:Phalanx page to lessen the chances of them accidentally adding anything that might match a blacklisted entry when reverting vandalism.

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 vandalism. They do not use their userrollback rights to revert 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 revert and delete vandalism on very large or very active wikis. They do not use their tools to revert and delete vandalism on wikis, unless the wikis are quiet or inactive. Or if they have previously failed to revert the vandalism with the userrollback extension. They do not use their tools for any other purpose. When undoing edits in most situations, they must use the undo button, as would any regular user.

User Rollbackers do not revert global 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 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 vandals to 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 lookup the global contributions of users or IP addresses if they need to quickly locate all the wikis where certain users or IP addresses have edited. User Rollbackers do not do checkuser requests. They only check users' IP addresses and other information if they need to check whether a user or IP address whose global vandalism they are about to revert is attached to an already reported account or IP address.

User Rollbackers do not delete article and blog comments, message wall messages, or discussion posts unless they are dealing with a global vandal whose edits they have reverted with the userrollback extension, since the Userrollback permission cannot be used to delete article and blog comments, message wall messages, or discussion posts. User Rollbackers do not check the Special:Phalanx page unless they need to view blacklisted entries to lessen the chances of them accidentally adding anything that might match a blacklisted entry when reverting vandalism. They also must not deliberately do anything that would otherwise match a blacklisted entry.

User Rollbackers do not change the protection settings of other users' blog articles, create blog articles for other users, or edit, move, or undo edits to other users' blog articles unless they have Administrator or Assistant rights. They also do not change the protection settings of interactive maps, or create or undo edits to whitelisted MediaWiki pages or sitewide CSS pages unless they have Administrator rights. User Rollbackers also do not create or undo edits to sitewide JavaScript pages unless they have Administrator rights and the wiki has sitewide JavaScript enabled.

User Rollbackers do not change the protection settings of semi-protected pages, or create, edit, move, or undo edits to semi-protected pages unless they have Administrator, Assistant, Content Moderator, or Autoconfirmed rights. They also do not change the protection settings of fully protected or cascade-protected pages, or create, edit, move, or undo edits to fully protected or cascade-protected pages unless they have Administrator, Assistant, or Content Moderator rights. They do not change the protection settings of pages in general unless they have Administrator, Assistant, or Content Moderator rights.

User Rollbackers do not create, edit, move, or undo edits to interactive maps unless they have Administrator or Interactive Map Tester rights. They also do not change the protection settings of widgets, or create, edit, move, or undo edits to MediaWiki pages, pages,  pages, or widgets, or move sitewide CSS or sitwide JavaScript pages unless they have Fandom Staff, Wiki Representative, Wiki Specialist, or Fandom Helper rights. User Rollbackers also do not change the protection settings of gadget definitions or gadget CSS and JavaScript pages, or create, edit, move, or undo edits to gadget definitions or gadget CSS and JavaScript pages unless they have Fandom Staff rights.

User Rollbackers do not change the protection settings of other users' CSS, JavaScript, or JavaScript Object Notation pages, or create, edit, move, or undo edits to sitewide JavaScript Object Notation pages, or other users' CSS, JavaScript, or JavaScript Object Notation pages unless they have Fandom Staff or Fandom Helper rights. If a User Rollback is part of another usergroup that grants them the ability to undelete pages, they must not undelete semi-protected pages, fully protected pages, cascade-protected pages, or pages in general unless they have Administrator or Content Moderator rights.

User Rollbackers may not undelete other users' blog articles, interactive maps, or whitelisted MediaWiki pages unless they have Administrator rights. They also may not undelete sitwide CSS pages, sitewide JavaScript pages, MediaWiki pages with or without a whitelisted prefix, FandomMobile.css pages, FandomMobile.js pages, or widgets unless they have Fandom Staff, Wiki Representative, Wiki Specialist, or Fandom Helper rights. They also may not undelete gadget definitions or gadget CSS and JavaScript pages unless they have Fandom Staff rights.

User Rollbackers may not undelete sitewide JavaScript Object Notation pages, or other users' CSS, JavaScript, or JavaScript Object Notation pages unless they have Fandom Staff or Fandom Helper rights. User Rollbackers that abuse their powers by doing any of the things that they aren't supposed to do will have their userrollback status revoked by Staff. Although in practice most User Rollbackers would probably also be Staff anyway.

System Messages associated with the usergroup
Listed below are the system messages associated with the User Rollback usergroup.

System Messages associated with the ability
Listed below are the system messages associated with the Userrollback right. While these are related to the permission that inspired this fictional usergroup and not related to the fictional usergroup itself, I decided to include them on this page for interest.