Meta tags:

Headings (most frequently used words):

restrict, editing, pages, of, all, certain, access, viewing, by, to, uploaded, files, removing, the, specific, for, creating, in, manual, preventing, contents, simple, private, wiki, account, creation, restricting, exporting, login, link, from, accounts, other, restrictions, see, also, an, entire, namespace, but, few, ip, address, ranges, particular, user, namespaces, example, restriction, server, configuration, anonymous, non, sysop, users, absolutely, everyone,

Text of the page (most frequently used words):
the (96), you (56), pages (48), restrict (48), and (47), mediawiki (38), user (34), page (32), #editing (32), for (32), can (29), manual (26), all (26), #access (25), this (25), not (25), edit (24), use (23), may (22), users (22), wggrouppermissions (21), with (20), account (20), from (19), wiki (18), that (18), extension (17), see (17), false (17), view (16), will (16), want (15), have (15), other (15), are (15), read (13), special (13), namespace (12), php (12), private (12), files (12), extensions (11), viewing (11), any (11), your (11), certain (11), anonymous (10), but (10), also (10), only (10), create (10), sysop (10), specific (9), allow (9), rights (9), links (9), login (9), uploaded (9), creating (9), using (8), possible (8), they (8), one (8), new (8), main (8), sysops (8), protect (8), code (7), help (7), more (7), still (7), them (7), prevent (7), address (7), contents (6), control (6), restrictions (6), software (6), these (6), version (6), support (6), than (6), localsettings (6), there (6), need (6), name (6), password (6), menu (6), createaccount (6), security (6), authorization (6), above (6), such (6), warning (6), creation (6), add (5), toggle (5), search (5), text (5), available (5), under (5), hacks (5), their (5), designed (5), set (5), originalusername (5), even (5), accounts (5), link (5), few (5), information (5), content (5), sidebar (5), createpage (5), namespaces (5), move (5), org (4), configuration (4), third (4), party (4), wgnamespaceprotection (4), some (4), editable (4), history (4), permissions (4), into (4), work (4), merge (4), then (4), non (4), able (4), block (4), removing (4), unset (4), export (4), every (4), when (4), file (4), wgwhitelistread (4), everyone (4), could (4), disable (4), source (4), images (4), image (4), example (4), talk (4), default (4), requires (4), true (4), autoconfirmed (4), particular (4), ranges (4), email (4), get (4), english (4), hide (4), preventing (3), developers (3), policy (3), terms (3), site (3), most (3), number (3), completely (3), delete (3), edits (3), username (3), simple (3), right (3), log (3), userlogin (3), cannot (3), restricting (3), issues (3), separate (3), wikis (3), data (3), basic (3), which (3), exists (3), used (3), anyone (3), case (3), per (3), give (3), common (3), older (3), higher (3), reading (3), img_auth (3), method (3), restriction (3), server (3), core (3), except (3), entire (3), examples (3), registrations (3), click (3), tools (3), subsection (3), table (2), statistics (2), about (2), privacy (2), creative (2), commons (2), license (2), was (2), last (2), edited (2), permission (2), configure (2), restricts (2), editsubpages (2), lockdown (2), approved (2), better (2), list (2), check (2), don (2), ask (2), official (2), channels (2), something (2), hack (2), has (2), features (2), fine (2), grained (2), groups (2), wgnonincludablenamespaces (2), wgrestrictionlevels (2), wgrestrictiontypes (2), related (2), section (2), remove (2), simply (2), unless (2), former (2), anotherusername (2), manner (2), been (2), exporting (2), upgrade (2), problems (2), those (2), viewable (2), between (2), make (2), database (2), whitelist (2), public (2), leaks (2), must (2), different (2), technical (2), mode (2), various (2), wikimedia (2), its (2), projects (2), others (2), removed (2), manually (2), require (2), level (2), neither (2), result (2), message (2), versions (2), recentchanges (2), setting (2), allows (2), like (2), functionality (2), css (2), instructions (2), wguploadpath (2), wish (2), location (2), order (2), deny (2), accessible (2), local (2), url (2), always (2), upload (2), directly (2), does (2), instead (2), given (2), way (2), change (2), usergroup (2), without (2), actions (2), feature (2), note (2), custom (2), ns_policy (2), editpolicy (2), array (2), absolutely (2), how (2), form (2), modify (2), created (2), random (2), button (2), send (2), confirmaccount (2), what (2), might (2), languages (2), translate (2), appearance (2), changes (2), donate (2), portal (2), topic, mobile, cookie, statement, conduct, disclaimers, additional, apply, agree, cc0, attribution, sharealike, february, 2026, categories, retrieved, https, www, index, title, preventing_access, oldid, 8198752, nsfilerepo, authorprotect, revs, moderation, flagged, revisions, proper, out, date, please, goes, wrong, fully, configuable, levels, tikiwiki, twiki, moinmoin, wgemailconfirmtoedit, interest, creator, ban, things, none, unhacked, packages, well, attempt, contort, anyway, however, another, original, disappear, preserve, readability, shown, deactivated, rename, usurped, null, wgblockdisableslogin, made, anoncontribs, skintemplate, function, skintemplatenavigation, universal, wghooks, tested, lts, upper, corner, specialpages, since, r19935, parameters, install, reapply, time, updated, immediately, fixes, upgrades, released, course, supported, having, shouldn, listed, plan, category, unviewable, interwiki, shared, localsetting, necessarily, clearly, delineated, criteria, lot, plug, sample, suitable, purpose, warned, three, possibilities, declined, t3924, intend, usage, basically, same, implementation, just, extra, why, operation, committees, single, exception, wikipedia, sister, act, normally, invisible, instance, forum, very, matter, two, modes, permanently, destroy, while, state, purposes, longer, revisiondelete, deleted, strongly, advised, supports, natively, patches, claiming, provide, cases, potentially, exposing, confidential, own, risk, nor, foundation, responsible, added, nature, reflect, actual, status, management, system, partial, although, won, determined, correct, errors, nosuchusershort, wrongpassword, listusers, running, later, vulnerability, affects, allowing, workaround, cve, 2025, 6590, required, screen, reason, recommended, authentication, htpasswd, equivalent, addition, think, isn, feed, readers, adding, names, word, space, underscore, line, engines, indexed, google, part, resourceloader, module, thus, exposed, through, turn, off, wgusesitecss, wgusesitejs, load, gadget, foo, who, knows, directory, either, point, script, follow, external, htaccess, visitor, after, combine, unable, markup, should, avoid, template, inclusion, sensitive, internet, where, accessed, apache, network, were, serving, addresses, articles, refer, including, docs, subdirectories, remain, publicly, via, direct, enabled, ability, served, underlying, web, based, unrestricted, further, createtalk, finer, four, days, old, revoking, already, prevents, affected, deprive, include, possibility, group, changing, blocking, schools, institutions, specified, present, modifying, systematically, future, basis, rangeblock, blockip, unblock, impose, blanket, sandboxes, join, request, etc, generously, fit, too, often, mentioned, spaces, protected, configured, period, assumed, defined, constant, equal, constants, ns_project, project, starting, variable, member, administrators, registered, before, classes, admin, put, place, abusefilter, modifications, methods, fixed, bug, 1859, article, top, loginprompt, sent, emailed, forgot, requested, first, marked, confirmed, enter, else, pick, wgenableemail, logged, following, confirmation, queue, proceed, follows, root, path, installation, depending, installed, probably, whitelisted, language, translated, question, requestaccount, thorough, testing, customization, provided, incomplete, real, world, ways, cause, accidentally, show, oneself, customizing, contains, useful, 日本語, አማርኛ, বাংলা, українська, русский, čeština, svenska, português, polski, italiano, français, español, dansk, català, kadazandusun, deutsch, bahasa, indonesia, printable, download, pdf, book, print, shortened, cite, permanent, here, general, discussion, beginning, personal, sandbox, village, pump, recent, community, developer, development, communication, desk, faq, contribute, tech, blog, navigation, jump,

Text of the page (random words):
create account link to get to the account creation form enter a username and an email address and click the by email button note you need wgenableemail true or else the sysop must pick a password and send it to the user the account will be created with a random password which is then emailed to the given address as with the forgot password feature the user will be requested to change password at first login when they do this the email address will also be marked as confirmed if you click the create account button instead you have to manually send the user their password you may also modify the contents of the email sent to new users by editing the page mediawiki createaccount text to prevent even sysops from creating accounts prevent new user registrations by anyone wggrouppermissions createaccount false wggrouppermissions sysop createaccount false to add a message on top of the login form modify mediawiki loginprompt restrict editing restrict editing of all pages users will still be able to read pages with these modifications and they can view the source by using special export article name or other methods see also bug 1859 fixed see help user rights and wggrouppermissions if you use extension abusefilter any wiki admin can also put various restrictions in place some examples of how to protect all pages from editing not reading by certain classes of users restrict anonymous editing requires that a user be registered before they can edit wggrouppermissions edit false restrict editing by all non sysop users requires that a user be a member of the administrators sysop usergroup wggrouppermissions edit false wggrouppermissions user edit false wggrouppermissions sysop edit true restrict editing by absolutely everyone wggrouppermissions edit false wggrouppermissions user edit false wggrouppermissions sysop edit false restrict editing of an entire namespace mediawiki version 1 10 starting from mediawiki version 1 10 it is possible to protect entire namespaces using the wgnamespaceprotection variable examples only allow autoconfirmed users to edit project namespace wgnamespaceprotection ns_project array autoconfirmed only allow sysops to edit policy namespace wggrouppermissions sysop editpolicy true wgnamespaceprotection ns_policy array editpolicy note that in the last case it s assumed that a custom namespace exists and that ns_policy is a defined constant equal to the namespace number see manual using custom namespaces and manual namespace constants for a list of mediawiki s core namespaces restrict editing of certain specific pages use the protect feature by default any sysop can protect pages so only other sysops can edit them in 1 9 and higher by default they can also protect pages so only autoconfirmed users with accounts older than a configured period can edit them this does not require editing configuration files if you want to restrict editing to groups with specific permissions edit wgrestrictionlevels to prevent actions other than edit and move use wgrestrictiontypes restrict editing of all but a few pages to impose a blanket restriction on editing for all pages but allow a few such as sandboxes join request pages etc to be more generously editable you can use the editsubpages extension this may not fit too often but you could also use the restrict editing of certain specific pages method mentioned above with all name spaces protected and only a special one editable by everyone which has all the pages you want editable restrict editing for certain ip address ranges schools and other institutions may want to block all edits not from a few specified ip address ranges to do so see manual block and unblock the only way to do this at present without modifying the code is to go to special blockip and systematically rangeblock every one of the address ranges that you don t want to be able to edit this will work for all future versions of mediawiki it will not work on a per namespace basis restrict editing by a particular user use the user blocking functionality to deprive a user of all edit access mediawiki does not include a possibility to give rights to separate users directly instead rights are always given to a user group there is no way in the core software to change permissions of particular users in order to restrict or allow editing particular pages except by changing their usergroup restrict creating of all pages revoking the edit right already prevents affected users from creating new pages and talk pages anonymous users can t create pages wggrouppermissions createpage false only users with accounts four days old or older can create pages requires mw 1 6 or higher wggrouppermissions createpage false wggrouppermissions user createpage false wggrouppermissions autoconfirmed createpage true restrict creating pages in certain namespaces there are separate rights for creating talk pages createtalk and creating non talk pages createpage if you need per namespace control finer than that it is not possible in core mediawiki and requires an extension such as extension lockdown restrict access to uploaded files further information manual image authorization img_auth php and manual user rights read if you have enabled the ability to upload files these will be served directly by the underlying web server as a result account based access to the file is unrestricted by default setting the user right read to false only restricts access to wiki pages such as articles and talk pages uploaded files including images files docs under the wguploadpath subdirectories will always remain publicly accessible via direct url access by default to restrict access to uploaded files refer to the instructions in manual image authorization and img_auth php example for access restriction to uploaded files in the server configuration if sensitive files are uploaded to an internet accessible wiki you may wish to add restrictions on where these can be accessed from on apache if your local network were 10 1 2 you could restrict serving files to local addresses with location mediawiki images order deny allow allow from 10 1 2 3 deny from all location restrict viewing restrict viewing of all pages warning if you want anonymous users to be unable to view the wiki markup code you should not allow them to edit any page see restrict editing of all pages above if they can edit any page they can use template inclusion to view even pages they can t edit this may be possible to avoid by using wgnonincludablenamespaces warning this method allows any visitor to view the wiki after creating an account you may wish to combine it with restrict account creation above warning uploaded images will still be viewable to anyone who knows the image directory s name either point wguploadpath to the img_auth php script and follow the instructions in manual image authorization or use some external method to protect images like htaccess warning wiki pages like mediawiki common css and mediawiki gadget foo css may be part of a public resourceloader module and thus can have their source code exposed through load php turn off wgusesitejs and wgusesitecss to disable this functionality if anonymous users can t view your page neither can search engines your site will not be indexed on google add this line to your localsettings php file disable reading by anonymous users wggrouppermissions read false but allow them to read e g these pages wgwhitelistread main page help contents the wgwhitelistread setting allows users to view the main page if page names have more than one word use a space between them not an underscore _ in addition to the main page of such a private site you could give access to the recentchanges page if you think that its content isn t private for feed readers by adding special recentchanges to wgwhitelistread if you need to protect even the sidebar main page or login screen for any reason it s recommended that you use higher level authentication such as htpasswd or equivalent warning if you are running a private wiki it is required that you upgrade to mediawiki version 1 39 13 1 43 2 1 44 0 or a later to protect your wiki a security vulnerability cve 2025 6590 affects older versions allowing any user to view all pages on private wikis there is no workaround available 1 although special listusers won t be available it can be determined if a username is correct from userlogin errors you may want to give a common text for mediawiki wrongpassword and mediawiki nosuchusershort restrict viewing of certain specific pages mediawiki was not designed to support per page or partial page access restrictions if you require this level of control you are strongly advised to use a content management system that supports it natively patches or third party extensions claiming to provide access control when in use with mediawiki may not work in all cases potentially exposing confidential data use them at your own risk neither the mediawiki developers nor the wikimedia foundation are responsible for any data leaks that may result this message is added to all extensions of this nature and may not reflect the actual security status of this extension for more information see security issues with authorization extensions to prevent anyone but sysops from viewing a page it can simply be deleted to prevent even sysops from viewing it it can be removed more permanently using manual revisiondelete to completely destroy the text of the page it can be manually removed from the database in any case the page cannot be edited while in this state and for most purposes no longer exists to have a page act normally for some users but be invisible to others as is possible for instance in most forum software is a very different matter mediawiki is designed for two basic access modes everyone can view every single page on the wiki with the possible exception of a few special pages this is the mode used by wikipedia and its sister projects anonymous users can only view the main page and login page and cannot edit any page this is basically the same as the above in terms of technical implementation just an extra check for every page view which is why it exists this is the mode of operation used by certain private wikis such as those used by various wikimedia committees if you intend to have different view permissions than that mediawiki is not designed for your usage see t3924 n declined data is not necessarily clearly delineated by namespace page name or other criteria and there are a lot of leaks you ll have to plug if you want to make it so see security issues with authorization extensions for a sample other wiki software may be more suitable for your purpose you have been warned if you must use mediawiki there are three basic possibilities set your wiki up private and whitelist specific pages that will be public with wgwhitelistread in the localsetting php file see the section above set up separate wikis with a shared user database configure one as viewable and one as unviewable see above and make interwiki links between them install a third party hack or extension you will have to reapply it every time you upgrade the software and it may not be updated immediately when new security fixes or upgrades of mediawiki are released third party hacks are of course not supported by mediawiki developers and if you re having problems you shouldn t ask on mediawiki l mediawiki or other official support channels a number of hacks are listed in category page specific read access extensions read about security issues with authorization extensions if you plan to use one of those restricting exporting see also manual parameters to special export it is not possible to export the contents of a page that cannot be read since r19935 removing the login link from all pages one can remove the login create account link from the upper right corner of all pages as users can still go to special specialpages special userlogin to log in in localsettings php use tested with mediawiki 1 43 0 lts wghooks skintemplatenavigation universal function skintemplate links unset links user menu createaccount unset links user menu login unset links user menu login private unset links user menu anoncontribs removing accounts if you want to completely remove access to a user e g on a simple private wiki it s not possible to simply delete the account unless no edits have been made you can block it but the user will still be able to read pages unless wgblockdisableslogin is set however using user merge and delete extension you can merge the account in another one and delete the former the original account will then disappear if you want to preserve history readability i e to have edits from the user to be still shown under their name you can create a new account e g with username originalusername deactivated and then merge originalusername into the former or even rename originalusername into anotherusername then create an account under originalusername and merge anotherusername into it in this manner originalusername will be completely usurped if you ve set a non null password other restrictions you may want to have pages editable only by their creator or ban viewing of history or any of a number of other things none of these features are available in an unhacked version of mediawiki if you need more fine grained permissions see the see also section for links to other wiki packages that are designed for this as well as hacks that attempt to contort mediawiki into something it s not designed to be but may work anyway see also there are some related manual help pages that may be of interest manual localsettings php manual wggrouppermissions manual wgrestrictiontypes manual wgrestrictionlevels manual wgnamespaceprotection manual wgemailconfirmtoedit manual wgnonincludablenamespaces manual user rights help user rights and groups other wiki software may have better support for fine grained access control than mediawiki moinmoin twiki tikiwiki has fully configuable access control to features and permission levels if you want better access control but want to use mediawiki this is a list of extensions and hacks to allow restrictions not possible in the software proper these hacks may be out of date check the version they re for please don t ask in official mediawiki support channels if something goes wrong with a third party hack extension flagged revisions extension moderation extension approved revs extension lockdown extension authorprotect extension editsubpages restricts anonymous users from editing most pages extension nsfilerepo retrieved from https www mediawiki org w index php title manual preventing_access oldid 8198752 categories page specific read access extensions mediawiki configuration configure permission namespace this page was last edited on 8 february 2026 at 03 02 text is available under the creative commons attribution sharealike license additional terms may apply text in the help namespace is available under the creativ...