Fictional User Group Rights/Removed

The following is an archive of past fictional usergroups and access rights that were previously associated with fictional usergroups conceived or adopted by C.Syde. For information about the current fictional usergroups conceived or adopted by C.Syde, and their present associated access rights, see this page.

User Group A
User Group A was a fictional usergroup that was between rollbackers and sysops. They had access to many of the sysop tools, apart from the ones that were introduced in 2015 onward. They had all the tools that User Group C had, and most of the tools that User Group B had.

User Group A had the ability to edit protected pages without cascading protection, unlike the default usergroups on legacy wikis. The reason for this was because at the time of this page's creation, I was unaware that none of the usergroups on Fandom had the ability to edit protected pages but not the ability to change protection settings. However there were some usergroups on certain legacy wikis that have ability to edit protected pages without cascading protection.

User Group B
User Group B was a fictional usergroup that was between rollbackers and sysops. They had access to many of the sysop tools, apart from the ones that were introduced in 2015 onward. They also didn't have the abilities to delete pages, or to block and unblock users. They had all the tools that User Group C had, and most of the tools that User Group A had. They had slightly fewer tools than User Group A, but they had access to a few tools that User Group A did not.

User Group C
User Group C was a fictional usergroup that was between rollbackers and sysops. They had access to many of the sysop tools, apart from the ones that were introduced in 2015 onward. They also didn't have the abilities to delete pages, or to block and unblock users. They had access to many tools, though they had fewer tools than User Group A and User Group B.

User Group C had the ability to edit protected pages without cascading protection, unlike the default usergroups on legacy wikis. The reason for this was because at the time of this page's creation, I was unaware that none of the usergroups on Fandom had the ability to edit protected pages but not the ability to change protection settings. However there were some usergroups on certain legacy wikis that have ability to edit protected pages without cascading protection.

Assistants
Assistants were a fictional usergroup that was based on the existing custom usergroup of the same name on the Encyclopedia SpongeBobia. It served as a position between Rollbackers and Administrators. It was sort of similar to the Content Moderator usergroup which was introduced in January 2016. An extended version of the Assistant usergroup exists on this wiki.

Assistants could only have their rights revoked by themselves, Bureaucrats, Deluxe Administrators, or Fandom Utilities, and they could only be promoted by Bureaucrats, Deluxe Administrators, and Fandom Utilities. Having this status caused 'ASSISTANT' to appear next to the username on the user's userpage.

Autopatrolled Users
Autopatrolled Users were a fictional usergroup that was based on existing custom usergroups on other wikis, of the same name. As the name of the usergroup implies, users belonging to that group had the ability to have their own edits automatically marked as patrolled.

There are several versions of this custom usergroup, including on external sites outside Fandom. A version of the Autopatrolled usergroup exists on The Sims Wiki, and another on this wiki.

Autopatrolled Users could only have their rights revoked by Administrators, Bureaucrats, Junior Admins, Deluxe Administrators, or Fandom Utilities, and they could only be promoted by Administrators, Bureaucrats, Junior Admins, Deluxe Administrators, and Fandom Utilities.

Emailconfirmed Users
Emailconfirmed Users were a fictional global usergroup that was based on the now existing global usergroup of the same name. As the name of the usergroup implies, users belonging to that group had confirmed their email in their preferences. They were also able to perform CAPTCHA-triggering actions without having to go through the CAPTCHA.