Gratisdata:User access levels/en-gb

A user's ability to use certain interface features are determined by the user rights that user has. Despite the term user right, extra permissions are privileges that require the trust of the community. This page summarizes them.

Overview
All users are part of the  group in Gratisdata (denoted as "Unregistered users" in the table), and all user accounts are part of the   group (denoted as "Registered accounts" in the table). Except for the  pseudo-group, which all users who have passed the age and activity requirements are in, only those groups are automatically granted. Autoconfirmed status for an account requires at least 4 days of age and at least 50 edits (90 days and 100 edits if editing through a Tor node; the abuse filter can revoke and/or delay automatic granting of this right, but no filters are currently configured to do so). The  user right can be manually assigned by administrators to accounts which don't meet this requirement, which provides equivalent permissions. Extra permissions like administrator access can only be assigned to registered user accounts.

Unregistered users
Denoted by  in the software configuration settings, this includes any user on Gratisdata. They may create and edit most pages (if not protected or in the MediaWiki: (interface) namespace). Unregistered users are identified by their IP addresses when making edits. Any unregistered user, if not blocked from doing so, may create an account for themselves at Special:CreateAccount. They are limited to 8 edits per minute and must answer a CAPTCHA prompt when adding new external links.

New users
Any logged-in user may maintain a watchlist at Special:Watchlist, and may email any other user (unless blocked from doing so) by using Special:EmailUser. While they no longer have the editing rate limit, they must still answer a CAPTCHA prompt when adding new external links until they become autoconfirmed or confirmed.

Autoconfirmed users
An account with at least 4 days of age and at least 50 edits (90 days and 100 edits for editors from Tor nodes; abuse filter can potentially delay or revert automatic promotion) is said to be. Any user account which does not meet these requirements can be granted the permission and receive the same permissions. Autoconfirmed users no longer need to respond to CAPTCHAs for most actions, can edit semi- pages, and can move most pages (except items and properties, which are simply renamed by changing the appropriate labels instead).

Administrators

 * Main page: 

Administrators, also known as sysops, are trusted with tasks such as blocking users, pages (and editing fully-protected pages), and deleting pages. Administrator access is assigned to users who pass a successful, by bureaucrats. They can assign rollback, confirmed user, IP block exempt, autopatrolled, and property creator status to other users, and can assign translation administrator and flooder status to themselves (but not other users). They automatically have access to all permissions they can assign (except translation administrator and flooder) - for example, administrators can create properties without assigning themselves the right.

Bureaucrats

 * Main page: 

Bureaucrats can add administrator, bureaucrat, bot, flooder and translation administrator status to any user, and remove bot, flooder and translation administrator status (removal of either administrator or bureaucrat status must be done by stewards). They also can rename users. The process for gaining bureaucrat status is similar to administrator status, but the requirements are higher, and generally only existing administrators are successful.

Translation administrators

 * Main page: 

Because Gratisdata is a multilingual wiki, it uses the translate extension, and translation administrators are users with access to administrative functions of the extension. Normal administrators may assign the right to themselves without filing a request, but all other users must make a request at Gratisdata:Requests for permissions/Translation administrator, and a local bureaucrat will assign the right to those who provide a good reason.

Bots

 * Main page: 

Bots are automated and/or semi-automated accounts that perform repetitive, generally-simple, tasks that humans would find tedious to perform. Such accounts are given the bot flag by a bureaucrat, after a successful request at Gratisdata:Requests for permissions/Bot. They may make edits at very fast rates, and are hidden from recent changes and watchlists.

Flooders

 * Main page: 

The flood flag is intended for repetitive actions performed by human users. Like the bot flag, the flood flag hides edits and log actions from Special:RecentChanges and watchlists. Administrators can add the flag to their own account if necessary; other users can be granted the flag by a bureaucrat per request at Gratisdata:Bureaucrats' noticeboard. The flood flag is not a permanent user right, so every flooder can remove the flag themselves when the respective actions are done.

Subsets of administrator access
The following groups give rights to users that administrators already have. All can be assigned or removed by administrators and requested at. They do not require election, but administrators are expected to use their judgement when assigning them.

Autopatroller

 * Main page: 

An autopatrolled user's edits are automatically marked as "patrolled", and autopatrolled users can patrol edits of users who are not autopatrolled by marking them as "patrolled". The right was generally granted to users whose edits are clearly not problematic. After the removal of this group, all autoconfirmed and manually confirmed users have their edits automatically marked as "patrolled".

Rollback

 * Main page: 

Rollback is a simple tool that can allow fast reverting of vandalism or other obvious abuse. When the "rollback" link is clicked, the latest edit to the page is reverted with an automatic edit summary, currently "Reverted edits by to last version by ". In addition, if the second-latest edit was also made by the same user as the latest, that edit is also reverted. All edits are reverted to the latest version by a user other than the user who was reverted. Rollback is generally assigned to those who demonstrate active vandalism and spam combating on Gratisdata.

Confirmed user

 * Main page: 

This group gives the same rights as autoconfirmed users to trusted users who don't meet the requirement for automatic promotion.

IP block exempt

 * Main page: 

If an IP address is blocked with the option to not allow logged-in users to edit, this permission allows editing from such IP addresses. It is granted only to those who need it and can be trusted not to abuse it, and CheckUser may be used to verify that need.

Property creators

 * Main page: 

New properties can only be created by users in this group or administrators, as properties should be discussed before being used.

Functionary permissions
These permissions, due to their potential privacy implications, require all members of their respective groups to be at least 16 years of age, of age of majority in their resident country, and identified to Miraheze Limited. Functionary permissions (including access for new stewards) can only be assigned by existing stewards.

Stewards

 * Main page: meta:Stewards

Stewards have access to MediaWiki interface on all Miraheze-hosted wikis, and unlike administrator and bureaucrat status, is a global permission that is elected annually. They can change any and all user rights, and serve as members of groups a particular wiki does not have. They will also act as CheckUsers until Gratisdata elects local CheckUsers, and when Gratisdata does select such users, stewards will be tasked with assigning them.

CheckUsers

 * Main page: meta:CheckUsers

The term CheckUser refers both to a member of this group of users and the tool they have access to. CheckUser allows members of this group to examine the IP address data of logged-in users, which is otherwise private information. Its primary purpose is to investigate sock puppetry. CheckUser access, like Oversight access, is granted after at least 20 support votes and at least 80% support after at least 7 days of discussion.

Oversighters

 * Main page: meta:Oversight

The term oversight refers to the name of the extension that was originally used for this purpose until it was replaced by RevisionDelete. Administrators can also apply RevisionDelete to particular edits or log actions, but oversighters can also hide the information from even administrators. It is done to hide either otherwise-private information or libellous information that even administrators should not have access to.