Manual:User rights/sr

Jump to navigation Jump to search
This page is a translated version of the page Manual:User rights and the translation is 8% complete.

Outdated translations are marked like this.
Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎Tagalog • ‎dansk • ‎español • ‎français • ‎italiano • ‎polski • ‎português do Brasil • ‎русский • ‎српски / srpski • ‎українська • ‎हिन्दी • ‎মেইতেই লোন্ • ‎中文 • ‎日本語 • ‎한국어

User rights are specific access and ability permissions that can be assigned to customizable user groups. Groups can then be assigned to (or removed from) users through the Special:UserRights special page. See Help:User rights and groups .

Access to this interface is itself governed by the userrights right, so only users in the Бирократе group can do it (in a default set-up). See Manual:Setting user groups in MediaWiki for information about managing and the assignment of user groups.

Changing group permissions

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 of 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 “ninja” group that can block users and delete pages, and whose edits are hidden by default in the recent changes log:

$wgGroupPermissions['ninja']['bot']    = true;
$wgGroupPermissions['ninja']['block']  = true;
$wgGroupPermissions['ninja']['delete'] = true;
Note: the group name cannot contain spaces, so use 'random-group' or 'random_group' instead of 'random group'

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

  • MediaWiki:Group-ninja (content: Ninjas)
  • MediaWiki:Group-ninja-member (content: ninja)
  • MediaWiki:Grouppage-ninja (content: Project:Ninjas)

This will ensure that the group will be referred to as “Ninjas” throughout the interface, and a member will be referred to as a “ninja”, and overviews will link the group name to Project:Ninjas.

This example disables write access (page editing and creation) by default, creates a group named “Write”, 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['Write']['edit'] = true;
$wgGroupPermissions['Write']['createpage'] = true;

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

  • MediaWiki:Group-Write (content: Writers)
  • MediaWiki:Group-Write-member (content: Writer)
  • MediaWiki:Grouppage-Write (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 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 Authorisation 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+
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.8+
bigdelete брисање страница са великом историјом 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 sysop 1.11+
browsearchive претрага избрисаних страница - through Special:Undelete 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 (not available by default) 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 (not available by default) 1.6+
editcontentmodel мењање модела садржаја странице user 1.23.7+
editinterface уређивање корисничког окружења - contains interface messages. For editing sitewide CSS/JSON/JS, there are now segregate rights, see below. sysop, interface-admin 1.5+
editmyoptions уређивање сопствених подешавања * 1.22+
editmyprivateinfo уређивање сопствених приватних података (нпр. адресе е-поште, правог имена) * 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) 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) user 1.22+
editmyuserjson уређивање сопствених JSON датотека (note that this is not needed if the group already has the edituserjson right) user 1.31+
editmywatchlist уређивање сопственог списка надгледања; неке предузете радње ће свеједно додати странице на списак и без овог права * 1.22+
editsitecss Edit sitewide CSS interface-admin 1.32+
editsitejs Edit sitewide JavaScript interface-admin 1.32+
editsitejson Edit sitewide JSON interface-admin 1.32+
editusercss уређивање туђих CSS датотека interface-admin 1.16+
edituserjs уређивање туђих JavaScript датотека interface-admin 1.16+
edituserjson уређивање туђих JSON датотека interface-admin 1.31+
hideuser блокирање корисничког имена и његово сакривање од јавности - (није доступно по подразумеваном)

Only users with 1000 edits or less can be suppressed by default. Use $wgHideUserContribLimit to disable.

markbotedits означавање враћених измена као измене бота - see Manual:Administrators#Rollback sysop 1.12+
mergehistory обједињавање историја страница sysop 1.12+
pagelang мењање језика странице - $wgPageLanguageUseDB must be true 1.24+
patrol означавање туђих измена патролираним - $wgUseRCPatrol must be true sysop 1.5+
patrolmarks прегледање ознака за патролирање унутар скорашњих измена 1.16+
protect мењање нивоа заштите и уређивање страница под преносивом заштитом sysop 1.5+
rollback брзо враћање измена последњег корисника који је мењао одређену страницу sysop 1.5+
suppressionlog прегледање приватних дневника 1.6+
suppressrevision прегледање, скривање и враћање одређених измена страница од свих корисника - Prior to 1.13 this right was named hiderevision (not available by default) 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 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) 1.24+
autopatrol аутоматско означавање измена патролираним - $wgUseRCPatrol must be true bot, sysop 1.9+
deletechangetags брисање ознака из базе података - currently unused by extensions sysop 1.28+
import увожење страница из других викија - “transwiki” sysop 1.5+
importupload увожење страница из отпремљене датотеке - This right was called 'importraw' in and before version 1.5 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 minor edit 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+
purge чишћење кеш меморије странице без потврде - URL parameter "&action=purge" user 1.10+
suppressredirect премештање страница без остављања преусмерења bot, sysop 1.12+
writeapi коришћење API-ја за писање *, 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 whitelisted). 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, proxyunbannable, 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+

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 .

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 User.php , $mCoreRights (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 ninja-powers right
$wgAvailableRights[] = 'ninja-powers';

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

//add ninja-powers to the 'basic' grant so we can use our ninja powers over an API request
$wgGrantPermissions['basic']['ninja-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