Manual:User rights/sr

This page is a translated version of the page Manual:User rights and the translation is 7% complete.

User rights are permissions (like the ability to edit pages or to block users) that can be assigned to different user groups. MediaWiki ships with a default set of user rights and user groups, but these can be customized. This page explains the default rights and groups and how to customize them.

For information about how to add and remove individual wiki users from groups, see Help:User rights and groups and Manual:Setting user groups in MediaWiki .

A default MediaWiki installation assigns certain rights to default groups (see below). You can change the default rights by editing the $wgGroupPermissions array in LocalSettings.php with the syntax.

$wgGroupPermissions['group']['right'] = true /* or false */;
In a default installation $wgGroupPermissions will be set in includes/DefaultSettings.php, but it is not present in LocalSettings.php. You will then need to add it in that file.

If a member has multiple groups, they get all the permissions from each of the groups they are in. All users, including anonymous users, are in the '*' group; all registered users are in the 'user' group. In addition to the default groups, you can arbitrarily create new groups using the same array.


This example will disable viewing of all pages not listed in $wgWhitelistRead , then re-enable for registered users only:

$wgGroupPermissions['*']['read'] = false;
# The following line is not actually necessary, since it's in the defaults. Setting '*' to false doesn't disable rights for groups that have the right separately set to true!
$wgGroupPermissions['user']['read'] = true;

This example will disable editing of all pages, then re-enable for users with confirmed email addresses only:

# Disable for everyone.
$wgGroupPermissions['*']['edit'] = false;
# Disable for users, too: by default 'user' is allowed to edit, even if '*' is not.
$wgGroupPermissions['user']['edit'] = false;
# Make it so users with confirmed email addresses are in the group.
$wgAutopromote['emailconfirmed'] = APCOND_EMAILCONFIRMED;
# Hide group from user list.
$wgImplicitGroups[] = 'emailconfirmed';
# Finally, set it to true for the desired group.
$wgGroupPermissions['emailconfirmed']['edit'] = true;

Creating a new group and assigning permissions to it

You can create new user groups by defining permissions for the according group name in $wgGroupPermissions['<group-name>'] where <group-name> is the actual name of the group.

Additionally to assigning permissions, you should create these three wiki pages with fitting content:

  • MediaWiki:Group-<group-name> (content: Name of the group)
  • MediaWiki:Group-<group-name>-member (content: Name of a member of the group)
  • MediaWiki:Grouppage-<group-name> (content: Name of the group page)

By default, bureaucrats can add users to, or remove them from, any group. However, if you are using Manual:$wgAddGroups and Manual:$wgRemoveGroups , you may need to customize those instead.


This example will create an arbitrary "projectmember" group that can block users and delete pages, and whose edits are hidden by default in the recent changes log:

$wgGroupPermissions['projectmember']['bot'] = true;
$wgGroupPermissions['projectmember']['block'] = true;
$wgGroupPermissions['projectmember']['delete'] = true;
The group name cannot contain spaces, so use 'random-group' or 'random_group' instead of 'random group'. Moreover it is recommended to only use lowercase letters to create a group.

In this example, you would probably also want to create these pages:

  • MediaWiki:Group-projectmember (content: Project members)
  • MediaWiki:Group-projectmember-member (content: Project member)
  • MediaWiki:Grouppage-projectmember (content: Project:Project Members)

This will ensure that the group will be referred to as "Project members" throughout the interface, and a member will be referred to as a "Project member", and overviews will link the group name to Project:Project members.

This example disables write access (page editing and creation) by default, creates a group named "writer", and grants it write access. Users can be manually added to this group via Special:UserRights:

$wgGroupPermissions['*']['edit'] = false;
$wgGroupPermissions['*']['createpage'] = false;
$wgGroupPermissions['user']['edit'] = false;
$wgGroupPermissions['user']['createpage'] = false;
$wgGroupPermissions['writer']['edit'] = true;
$wgGroupPermissions['writer']['createpage'] = true;

In this example, you would probably also want to create these pages:

  • MediaWiki:Group-writer (content: Writers)
  • MediaWiki:Group-writer-member (content: Writer)
  • MediaWiki:Grouppage-writer (content: Project:Write)

Removing predefined groups

MediaWiki out of the box comes with a number of predefined groups. Most of these groups can be removed by unsetting the according array keys, among them $wgGroupPermissions['<group-name>']. For details, see below.


This example will eliminate the bureaucrat group entirely. It is necessary to ensure that all six of these variables are unset for any group that one wishes to remove from being listed at Special:ListGroupRights; however, merely unsetting $wgGroupPermissions will suffice to remove it from Special:UserRights. This code should be placed after any require_once lines that add extensions, such as Extension:Renameuser containing code that gives bureaucrats group permissions by default.

unset( $wgGroupPermissions['bureaucrat'] );
unset( $wgRevokePermissions['bureaucrat'] );
unset( $wgAddGroups['bureaucrat'] );
unset( $wgRemoveGroups['bureaucrat'] );
unset( $wgGroupsAddToSelf['bureaucrat'] );
unset( $wgGroupsRemoveFromSelf['bureaucrat'] );

In some extensions (Flow, Semantic MediaWiki, etc.), rights are added during extension registration or in a registration function. In this case, it could be necessary to use a registration function in LocalSettings.php to remove some predefined user groups:

$wgExtensionFunctions[] = function() use ( &$wgGroupPermissions ) {
    unset( $wgGroupPermissions['oversight'] );
    unset( $wgGroupPermissions['flow-bot'] );

Note on the group called "user"

With the above mechanism, you can remove the groups sysop, bureaucrat and bot, which - if used - can be assigned through the usual user permission system. However, it is currently impossible to remove the user group. This group is not assigned through the usual permission system. Instead, every logged-in user automatically is a member of that group. This is hardcoded in MediaWiki and currently cannot be changed easily.

List of permissions

The following user rights are available in the latest version of MediaWiki. If you are using an older version, look at "Special:Version" on your wiki and see if your version is covered in the "Versions" column.

Right Description User groups that have this right by default Versions
read читање страница - when set to false, override for specific pages with $wgWhitelistRead
Warning Warning: Setting the user right "read" (allow viewing pages) to false will only protect wiki (article, talk, ...) pages, but uploaded files (images, files, docs... in the $wgUploadPath subdirectories) will always remain readable via direct access by default.
Use the information from Manual:Image authorization and img_auth.php pages when you have the need to restrict image views and file download access to only logged-in users.
*, user 1.5+
applychangetags примењивање ознака на нечије измене user 1.25+
autocreateaccount аутоматска пријава спољашњим корисничким налогом - a more limited version of createaccount 1.27+
createaccount отварање нових корисничких налога - register / registration *, sysop 1.5+
createpage прављење страница (изузев страница за разговор) - захтева право edit *, user 1.6+
createtalk прављење страница за разговор - захтева право edit *, user 1.6+
delete-redirect преснимавање преко постојећих преусмерења која садрже само једну измену (note that this is not needed if the group already has the delete right) 1.36+
edit уређивање страница *, user 1.5+
editsemiprotected уређивање страница под заштитом „Allow only autoconfirmed users“ - without cascading protection autoconfirmed, bot, sysop 1.22+
editprotected уређивање страница под заштитом „Allow only administrators“ - without cascading protection sysop 1.13+
minoredit означавање измена мањим user 1.6+
move премештање страница - захтева право edit user, sysop 1.5+
move-categorypages премештање категорија - захтева право move user, sysop 1.25+
move-rootuserpages премештање основних корисничких страница - захтева право move user, sysop 1.14+
move-subpages премештање страница с њиховим подстраницама - захтева право move user, sysop 1.13+
movefile премештање датотека - захтева право move и $wgAllowImageMoving да буде подешено на true user, sysop 1.14+
reupload замењивање постојећих датотека - захтева право upload user, sysop 1.6+
reupload-own замењивање сопствених датотека - requires the upload right (note that this is not needed if the group already has the reupload right) 1.11+
reupload-shared локално замењивање датотека на дељеном спремишту медија - (if one is set up) with local files (захтева право upload) user, sysop 1.6+
sendemail слање имејлова другим корисницима user 1.16+
upload отпремање датотека - захтева право edit и $wgEnableUploads да буде подешено на true user, sysop 1.5+
upload_by_url отпремање датотека с URL адресе - захтева право upload (До 1.20 отдавалось системным администраторам) 1.8+
bigdelete брисање страница с великом историјом измена (as determined by $wgDeleteRevisionsLimit ) - requires the delete right sysop 1.12+
block блокирање даљих измена других корисника - Block options include preventing editing and registering new accounts, and autoblocking other users on the same IP address sysop 1.5+
blockemail блокирање функције слања имејлова кориснику - allows preventing use of the Special:Emailuser interface when blocking - requires the block right sysop 1.11+
browsearchive претрага избрисаних страница - through Special:Undelete - requires the deletedhistory right sysop 1.13+
changetags додавање и уклањање разних ознака на појединачним изменама и уносима у дневницима - currently unused by extensions user 1.25+
delete брисање страница 1.5–1.11: allows the deletion or undeletion of pages.
1.12+: allows the deletion of pages. For undeletions, there is now the 'undelete' right, see below
sysop 1.5+
deletedhistory прегледање избрисаних ставки историје без повезаног текста sysop 1.6+
deletedtext прегледање избрисаног текста и промена између избрисаних измена sysop
deletelogentry брисање и враћање одређених уноса у дневнику - allows deleting/undeleting information (action text, summary, user who made the action) of specific log entries - requires the deleterevision right suppress 1.20+
deleterevision брисање и враћање одређених измена страница - allows deleting/undeleting information (revision text, edit summary, user who made the edit) of specific revisions Split into deleterevision and deletelogentry in 1.20 suppress 1.6+
editcontentmodel мењање садржинског модела странице - requires the edit right user 1.23.7+
editinterface уређивање корисничког окружења - contains interface messages. For editing sitewide CSS/JSON/JS, there are now segregate rights, see below. - requires the edit right sysop, interface-admin 1.5+
editmyoptions уређивање сопствених подешавања * 1.22+
editmyprivateinfo уређивање сопствених приватних података (нпр. имејл-адресе, правог имена) - also hides the "Change Password", but not other ways to change the password * 1.22+
editmyusercss уређивање сопствених датотека на CSS-у - prior to 1.31 it was assigned to everyone (i.e. "*") (note that this is not needed if the group already has the editusercss right) - requires the edit right user 1.22+
editmyuserjs уређивање сопствених датотека на JavaScript-у - prior to 1.31 it was assigned to everyone (i.e. "*") (note that this is not needed if the group already has the edituserjs right) - requires the edit right user 1.22+
editmyuserjsredirect уређивање сопствених датотека на JavaScript-у које су преусмерења (note that this is not needed if the group already has the edituserjs right) - requires the edit right 1.34+
editmyuserjson уређивање сопствених датотека на JSON-у (note that this is not needed if the group already has the edituserjson right) - requires the edit right user 1.31+
editmywatchlist уређивање сопственог списка надгледања (знајте да неке предузете радње ће свеједно додати странице на списак и без овог права) * 1.22+
editsitecss уређивање CSS-а за цео пројекат - requires the editinterface right interface-admin 1.32+
editsitejs Уређивање JavaScript-а за цео пројекат - requires the editinterface right interface-admin 1.32+
editsitejson уређивање JSON-а за цео пројекат - requires the editinterface right sysop, interface-admin 1.32+
editusercss уређивање CSS датотека других корисника - requires the edit right interface-admin 1.16+
edituserjs уређивање туђих датотека на JavaScript-у - requires the edit right interface-admin 1.16+
edituserjson уређивање туђих ЈСОН датотека - requires the edit right sysop, interface-admin 1.31+
hideuser блокирање корисничког имена и његово сакривање од јавности - Only users with 1000 edits or less can be suppressed by default - requires the block right

Use $wgHideUserContribLimit to disable.

suppress 1.10+
markbotedits означавање враћених измена као измене бота - see Manual:Administrators#Rollback - requires the rollback right sysop 1.12+
mergehistory обједињавање историја страница - requires the edit right sysop 1.12+
pagelang мењање језика странице - $wgPageLanguageUseDB must be true 1.24+
patrol означавање измена других корисника патролираним - $wgUseRCPatrol must be true sysop 1.5+
patrolmarks преглед ознака за патролирање у скорашњим изменама 1.16+
protect мењање подешавања заштите и уређивање страница под ланчаном заштитом - requires the edit right sysop 1.5+
rollback брзо враћање измена последњег корисника који је мењао одређену страницу - requires the edit right sysop 1.5+
suppressionlog прегледање приватних дневника suppress 1.6+
suppressrevision прегледање, скривање и враћање одређених измена страница од свих корисника - Prior to 1.13 this right was named hiderevision - requires the deleterevision right suppress 1.6+
unblockself деблокирање самог себе - Without it, an administrator that has the capability to block cannot unblock themselves if blocked by another administrator sysop 1.17+
undelete враћање избрисаних страница - requires the deletedhistory right sysop 1.12+
userrights уређивање свих корисничких права - allows the assignment or removal of all(*) groups to any user.

(*)With $wgAddGroups and $wgRemoveGroups you can set the possibility to add/remove certain groups instead of all

bureaucrat 1.5+
userrights-interwiki уређивање корисничких права на другим пројектима 1.12+
viewmyprivateinfo преглед сопствених приватних података (нпр. имејл-адресе, правог имена) * 1.22+
viewmywatchlist преглед сопственог списка надгледања * 1.22+
viewsuppressed прегледање измена скривених од свих корисника - i.e. a more narrow alternative to "suppressrevision" (note that this is not needed if the group already has the suppressrevision right) suppress 1.24+
autopatrol аутоматско означавање сопствених измена патролираним - $wgUseRCPatrol must be true bot, sysop 1.9+
deletechangetags брисање ознака из базе података - currently unused by extensions sysop 1.28+
import увожење страница из других пројеката - "transwiki" - requires the edit right sysop 1.5+
importupload увожење страница из отпремљене датотеке - This right was called 'importraw' in and before version 1.5 - requires the edit right sysop 1.5+
managechangetags прављење и (де)активирање ознака - currently unused by extensions sysop 1.25+
siteadmin закључавање и откључавање базе података - which blocks all interactions with the web site except viewing. (није доступно по подразумеваном) 1.5+
unwatchedpages прегледање списка ненадгледаних страница - lists pages that no user has watchlisted sysop 1.6+
apihighlimits употреба виших граница за упите API-ја bot, sysop 1.12+
autoconfirmed без ограничавања ставки за IP адресе - used for the 'autoconfirmed' group, see the other table below for more information autoconfirmed, bot, sysop 1.6+
bot сматрање измена као аутоматски процес - can optionally be viewed bot 1.5+
ipblock-exempt заобилажење IP блокада, аутоблокада и блокада опсега sysop 1.9+
nominornewtalk непоседовање мањих измена на страницама за разговор отвара прозор за нове поруке - requires the minoredit right bot 1.9+
noratelimit отпорност на ограничења - not affected by rate limits (prior to the introduction of this right, the configuration variable $wgRateLimitsExcludedGroups was used for this purpose) sysop, bureaucrat 1.13+
override-export-depth извоз страница укључујући и повазене странице до дубине од пет веза
With this right, you can define the depth of linked pages at Special:Export. Otherwise, the value of $wgExportMaxLinkDepth , which is 0 by default, will be used.
purge чишћење кеш меморије странице - URL parameter "&action=purge" user 1.10+
suppressredirect премештање страница без остављања преусмерења - requires the move right bot, sysop 1.12+
writeapi употреба API-ја за писање - requires the edit right *, user, bot 1.13+
Although these permissions all control separate things, sometimes to perform certain actions you need multiple permissions. For example allowing people to edit but not read pages doesn't make sense, since in order to edit a page you must first be able to read it (Assuming no pages are allowlisted). Allowing uploads but not editing does not make sense, since in order to upload an image you must implicitly create an image description page, etc.

List of groups

The following groups are available in the latest version of MediaWiki. If you are using an older version then some of these may not be implemented.

Group Description Default rights Versions
* all users (including anonymous). createaccount, createpage, createtalk, edit, editmyoptions, editmyprivateinfo, editmywatchlist, read, viewmyprivateinfo, viewmywatchlist, writeapi 1.5+
user registered accounts. applychangetags, changetags, createpage, createtalk, edit, editcontentmodel, editmyusercss, editmyuserjs, editmyuserjson, minoredit, move, move-categorypages, move-rootuserpages, move-subpages, movefile, purge, read, reupload, reupload-shared, sendemail, upload, writeapi
autoconfirmed registered accounts at least as old as $wgAutoConfirmAge and having at least as many edits as $wgAutoConfirmCount . autoconfirmed, editsemiprotected 1.6+
bot accounts with the bot right (intended for automated scripts). autoconfirmed, autopatrol, apihighlimits, bot, editsemiprotected, nominornewtalk, suppressredirect, writeapi 1.5+
sysop users who by default can delete and restore pages, block and unblock users, et cetera. apihighlimits, autoconfirmed, autopatrol, bigdelete, block, blockemail, browsearchive, createaccount, delete, deletedhistory, deletedtext, editinterface, editprotected, editsemiprotected, editsitejson, edituserjson, import, importupload, ipblock-exempt, managechangetags, markbotedits, mergehistory, move, move-categorypages, move-rootuserpages, move-subpages, movefile, noratelimit, patrol, protect, reupload, reupload-shared, rollback, suppressredirect, unblockself, undelete, unwatchedpages, upload 1.5+
interface-admin users who can edit sitewide CSS/JS. editinterface, editsitecss, editsitejs, editsitejson, editusercss, edituserjs, edituserjson 1.32+
bureaucrat users who by default can change other users' rights. noratelimit, userrights 1.5+
suppress deletelogentry, deleterevision, hideuser, suppressionlog, suppressrevision, viewsuppressed

From MW 1.12, you can create your own groups into which users are automatically promoted (as with autoconfirmed and emailconfirmed) using $wgAutopromote . You can even create any custom group by just assigning rights to them.

Default rights

The default rights are defined in DefaultSettings.php .

  • Default values in HEAD version:

  • The default values in the latest stable MediaWiki release, version 1.37, are available here:

  • Additional rights: you should be able to list all the permissions available on your wiki by running User::getAllRights().

Adding new rights

Information for coders only follows.

If you're adding a new right in core, for instance to control a new special page, you are required to add it to the list of available rights in PermissionManager.php , $coreRights (example). If you're doing so in an extension , you instead need to use $wgAvailableRights .

You probably also want to assign it to some user group by editing $wgGroupPermissions described above.

If you want this right to be accessible to external applications by OAuth or by bot passwords, then you will need to add it to a grant by editing $wgGrantPermissions .

// create projectmember-powers right
$wgAvailableRights[] = 'projectmember-powers';

// add projectmember-powers to the projectmember-group
$wgGroupPermissions['projectmember']['projectmember-powers'] = true;

// add projectmember-powers to the 'basic' grant so we can use our projectmember powers over an API request
$wgGrantPermissions['basic']['projectmember-powers'] = true;

You also need to add right-[name] and action-[name] interface messages to /languages/i18n/en.json (with documentation in qqq.json). The right-* messages can be seen on Special:ListGroupRights and the action-* messages are used in a sentence like "You do not have permission to ...".

See also