Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Meta:Administrators: Difference between revisions

From WikiOasis Meta
Zippybonzo (alt) (talk | contribs)
create a draft
Tags: Potentially disruptive edit Visual edit
 
No edit summary
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Header
| title = Administrators
| notes = This page describes the role and responsibilities of WikiOasis administrators (<code>sysop</code>), and outlines the procedures for gaining or losing the rights.
| color = blue
}}
{{Meta policy}}
[[File:Meta administrator.png|{{dir|{{PAGELANGUAGE}}|left|right}}|150px]]
'''Administrator''' is a default group enabled on all wikis by default. It can be granted and removed by [[Meta:Bureaucrat|Bureaucrats]] by default.
== On Meta ==
'''Administrators''' are users with additional technical capabilities on Meta. They use these technical capabilities to perform routine maintenance, such as deleting old pages and blocking vandal accounts. They have the technical ability to do the following (not an exhaustive list):
'''Administrators''' are users with additional technical capabilities on Meta. They use these technical capabilities to perform routine maintenance, such as deleting old pages and blocking vandal accounts. They have the technical ability to do the following (not an exhaustive list):


Line 9: Line 19:
* Edit the [[Global title blacklist]]
* Edit the [[Global title blacklist]]


== Becoming an administrator ==
=== Becoming an administrator ===
Administrator is a highly trusted role, giving users the ability to manage certain global functionality, such as central notices and the global title blacklist. In order for a user to become an administrator, they must request it on the [[Meta:Requests for permissions|requests for permissions]] page. For the request to be deemed successful, there needs to be the following:
Administrator is a highly trusted role, giving users the ability to manage certain global functionality, such as central notices and the global title blacklist. In order for a user to become an administrator, they must request it on the [[Meta:Requests for permissions|requests for permissions]] page. For the request to be deemed successful, there needs to be the following:


Line 16: Line 26:
* The request must have been open for at least 7 days
* The request must have been open for at least 7 days


== Revocation ==
=== Revocation ===
In the event that a request for the removal of administrator for a user is opened on the [[Community portal]], for the request to be deemed successful, there needs to be the following:
In the event that a request for the removal of administrator for a user is opened on the [[Community portal]], for the request to be deemed successful, there needs to be the following:


Line 22: Line 32:
* The request has been open for at least 3 days
* The request has been open for at least 3 days
* At least 3 users vote in the discussion
* At least 3 users vote in the discussion
== On other wikis locally ==
By default, administrators have access to:
* Protect pages
* Delete and undelete pages, revisions and logged actions
* Block and unblock users
* Edit fully protected pages, and those in the MediaWiki namespace
=== Appointment/Revocation ===
If a wiki has a local procedure for appointment/revocation of administrator access, that should be followed. If a wiki does not have any local bureaucrats, please post a request at [[Steward requests]] for a user to be granted administrator. If a wiki does not have any local administrators or bureaucrats, a discussion should take place as per local procedure, and upon closure, the closing user should request for the right to be given (if successful) at [[Steward requests]]. If a wiki has no local administrators or bureaucrats, and no local procedure, stewards follow these guidelines:
* A discussion should take place for 5 days on the community portal
* A 70% support ratio should be reached.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.