28:
277:. On the other hand, if a page is speedily deleted, it may be appropriate for an admin to speedily undelete it as well, especially if the admin improves or expands the article. It would be polite to notify the admin who deleted it, and if the two parties cannot reach agreement, the matter should be taken to deletion review.
196:
on articles is unacceptable behavior, wheel warring is never appropriate, regardless of an admin's goals or motivations. It is counterproductive and needlessly divisive. An admin should never repeatedly perform the same admin action within a short time frame when the action has been undone by another
213:
Admins should never use their admin abilities to intimidate others. For instance, threatening a user with an inappropriate block is just as bad behavior as actually making that block. Of course, warning a user in advance of blocks that are appropriate is good practice - it is only common courtesy to
141:
Knowledge works by consensus, and admins are expected to implement consensus (though an admin who holds a minority view is free to make their case as an editor and let another admin close the discussion). Admins who have taken sides in a discussion should not rule as to what the consensus was unless
99:
Admins, having more power, can do more harm than an average user, and thus are subject to higher standards of behavior. It is the responsibility of the admin to know the additional policies which apply to them as admins, and to take care to faithfully operate within them, so as to foster a just
294:
An admin should not block a user if they are not neutral with respect to that user, or have a conflict of interest. For instance, an admin blocking a user for an edit war involving that same admin is abusing their power. That said, being accused or attacked by a user does not necessarily mean a
222:
Admins are expected to use their tools in accordance with current policy, and therefore are expected to keep abreast of policy in the areas where they use the tools. Admins using a new or unfamiliar part of the admin toolset are advised to refresh their understanding of relevant policies.
302:
Admins should also be aware that warning a user of a block, especially when the user has no prior history of problems, can be perceived as a threat. When dealing with otherwise good contributors, it may be advisable to make suggestions as to their behavior without mentioning a block.
153:
mean that discussion is needed before any action can be taken. An admin who thinks that e.g. deleting a disruptive page is a good idea can do so. However, should this action turn out to be disputed by another good-faith user, it is preferable to discuss it or get a third opinion.
107:
That said, nobody's perfect. While admins are held to high standards, it is inevitable that they make the occasional mistake, or perform an action that isn't particularly wise. Admins are expected to listen to reasonable criticism, and to learn from their mistakes.
145:
Similarly, if discussion is ongoing regarding a certain issue, it is bad form to bypass the discussion and "force" the issue. Instead, one should help out by joining the discussion, or requesting outside opinion if necessary. This, too, applies to any editor.
395:
Admins and
Rollbackers can use the rollback button to quickly undo the last edit(s) by a single person on a single page. It is the equivalent of picking the last version by another editor from the history and restoring that, without leaving an
214:
inform a revert warrior or vandal that a block can be imposed for that behavior. When dealing with established editors that don't generally make problems, it may be preferable to suggest different behavior, rather than mentioning blocks.
317:
Admins blocked for any reason cannot perform any admin actions until and unless another admin unblocks them. Blocked admins may only edit their own talkpages. Similarly, admins should not unblock their own alternate accounts, other than
84:, and (with the exceptions of image deletion and page history merges/splits) can be undone by other admins. An admin who regularly misuses admin tools may be temporarily blocked by other admins, just as users can be blocked for
407:
The rollback tool is mainly intended to be used against vandalism, but can also be used to undo ones own mistakes. It should never be used in content disputes, edit wars or to revert another users' good faith edits.
189:" is the repeated performing of an admin action that is then undone by another admin. It can occur between two admins who disagree, or between one admin and a larger group of like-minded individuals.
231:
Admins are privy to information that other users are entitled to expect will be kept securely. Therefore admins are expected to operate on an appropriate level of security, including using a
133:
of articles. With regard to simple misbehavior, admins are treated identically to regular users; for instance, a three-revert violation can be sanctioned with a 24-hour block.
121:
Admins are entrusted with additional abilities, but do not have special rights beyond those of regular editors. Like everybody else, admins are expected to behave in a
314:
violation of policy. Assume good faith should extend to admin actions and they should not be undone without a better reason than "I wouldn't have done it".
358:
Admins can edit protected pages, but should in general refrain from doing so (with obvious exceptions such as acting on talk page consensus or adding a
417:
46:
347:
Admins should not protect pages in edit wars that they are involved in. However, protection of a page does not imply endorsement for the
306:
When undoing a block placed by another admin, it is good form to make a note of it either on the blocking admin's talk page, or on
368:
message). If a page is protected to stop an edit war, it is bad form to edit the page unless you are neutral in that edit war.
437:
177:
are abused to make an opinion seem more prevalent than it actually is. Such sockpuppetry does not constitute true consensus.
45:
for its implementation was not established within a reasonable period of time. If you want to revive discussion, please use
35:
432:
63:
50:
17:
273:
If a page is deleted per one of the deletion process pages, it should only be undeleted after being discussed on
101:
375:
which define the
Knowledge interface. Since any change in there affects the entire community, these pages are
379:
for experimenting with and should never be modified without prior discussion in a central place, such as the
89:
447:
197:
admin. If admins are in disagreement over what should be done, the issue should be discussed (generally at
342:
442:
280:
A page should never be speedily deleted if it has been restored as a result of a deletion review vote.
289:
253:
267:
104:, which has the authority to impose probation or sanctions, including removal of admin status.
193:
85:
142:
either it was very clear, or they are ruling that the consensus was against their position.
348:
208:
8:
372:
319:
42:
362:
235:
and not using their admin account on insecure machines such as in
Internet cafes. See
236:
173:
cannot be overridden by apparent consensus to the contrary. Additionally, sometimes
295:
conflict of interest. When in doubt, the admin should place a notification on the
330:
232:
186:
157:
That said, a few core principles of
Knowledge are non-negotiable. In particular,
355:
involved admin reverts once to the other version and then immediately protects.
205:, or on the talk pages of the admins involved) so that consensus can be formed.
174:
170:
426:
401:
384:
326:
307:
296:
274:
259:
202:
198:
180:
130:
126:
122:
93:
81:
76:
Admins are primarily held accountable by other admins. All admin actions are
397:
380:
351:
the page is protected in. For that reason, it shouldn't be a problem if an
263:
158:
336:
77:
325:
The appropriateness of a block on another admin should be discussed on
390:
283:
247:
71:
136:
162:
62:
This was a proposed policy based on the many opinions given at the
266:, or if a consensus was reached to delete the page on one of the
116:
310:. Better yet would be to discuss it first unless the block is a
242:
217:
166:
411:
258:
Pages should only be deleted if they meet a criterion for
226:
111:
16:For the established policy for administrators, see
100:environment. Admins are held accountable to the
424:
333:over whether another admin should be blocked.
418:Knowledge:Administrative Standards Commission
322:for sharing IP addresses with blocked users.
161:(which includes applications of doctrine of
18:Knowledge:Administrators § Accountability
425:
92:; such blocks should be noted on the
22:
64:Knowledge:Admin accountability poll
13:
14:
459:
80:, are subject to discussion and
26:
102:Knowledge Arbitration Committee
400:. Non-admins have access to a
329:. It is extremely bad form to
1:
438:Knowledge dispute resolution
404:that has the same function.
7:
343:Knowledge:Protection policy
10:
464:
433:Knowledge failed proposals
340:
287:
251:
15:
371:Admins can also edit the
290:Knowledge:Blocking policy
254:Knowledge:Deletion policy
125:manner, to not engage in
49:or initiate a thread at
199:the admin noticeboard
171:Neutral Point of View
209:Bullying and threats
448:Knowledge adminship
264:copyright violation
443:Knowledge culture
381:admin noticeboard
297:admin noticeboard
129:and to not claim
94:admin noticeboard
58:
57:
455:
367:
361:
268:deletion process
169:license, or the
90:personal attacks
51:the village pump
30:
29:
23:
463:
462:
458:
457:
456:
454:
453:
452:
423:
422:
414:
402:javascript tool
393:
373:MediaWiki pages
365:
359:
345:
339:
327:the noticeboard
292:
286:
275:deletion review
260:speedy deletion
256:
250:
245:
233:strong password
229:
220:
211:
203:deletion review
183:
139:
119:
114:
74:
54:
27:
21:
12:
11:
5:
461:
451:
450:
445:
440:
435:
421:
420:
413:
410:
392:
389:
338:
335:
285:
282:
249:
246:
244:
241:
228:
225:
219:
216:
210:
207:
182:
179:
138:
135:
118:
115:
113:
110:
73:
72:Accountability
70:
69:
68:
56:
55:
41:
40:
31:
9:
6:
4:
3:
2:
460:
449:
446:
444:
441:
439:
436:
434:
431:
430:
428:
419:
416:
415:
409:
405:
403:
399:
388:
386:
382:
378:
374:
369:
364:
356:
354:
350:
344:
334:
332:
328:
323:
321:
315:
313:
309:
304:
300:
298:
291:
281:
278:
276:
271:
269:
265:
261:
255:
240:
238:
237:WP:SOCK#LEGIT
234:
224:
215:
206:
204:
200:
195:
190:
188:
187:Wheel warring
181:Wheel warring
178:
176:
172:
168:
164:
160:
159:copyright law
155:
152:
147:
143:
134:
132:
128:
124:
109:
105:
103:
97:
95:
91:
87:
83:
79:
67:
65:
60:
59:
52:
48:
47:the talk page
44:
39:
37:
32:
25:
24:
19:
406:
398:edit summary
394:
385:village pump
376:
370:
357:
352:
346:
324:
316:
311:
305:
301:
293:
279:
272:
257:
230:
221:
212:
194:edit warring
191:
184:
156:
150:
148:
144:
140:
120:
106:
98:
75:
61:
33:
341:Main page:
320:auto-blocks
288:Main page:
252:Main page:
243:Admin tools
175:sockpuppets
127:revert wars
427:Categories
337:Protection
149:This does
34:This is a
363:protected
331:wheel war
137:Consensus
131:ownership
86:edit wars
43:Consensus
38:proposal.
412:See also
391:Rollback
383:and the
284:Blocking
248:Deletion
227:Security
192:Just as
163:Fair Use
112:Behavior
349:version
270:pages.
262:, or a
165:), the
117:General
308:WP:ANI
218:Policy
82:review
78:logged
36:failed
312:clear
201:, or
123:civil
167:GFDL
377:not
299:.
151:not
96:.
88:or
429::
387:.
366:}}
360:{{
353:un
239:.
185:"
66:.
53:.
20:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.