Notification of imminent suspension of administrative permissions due to inactivity
Following a community discussion in June 2011, consensus was reached to provisionally suspend the administrative permissions of users who have been inactive for one year (i.e. administrators who have not made any edits or logged actions in more than one year). As a result of this discussion, your administrative permissions will be removed if you do not return to activity within the next several days. If you wish to have these permissions reinstated should this occur, please post to the Wikipedia:Bureaucrats' noticeboard and the userright will be restored per the re-sysopping process (i.e. as long as the attending bureaucrats are reasonably satisfied that your account has not been compromised, that your inactivity did not have the effect of evading scrutiny of any actions which might have led to sanctions, that you have not been inactive for a three-year period of time, and that you have not been inactive from administrative tasks for a five year period of time). If you remain inactive for a three-year period of time, including the present year you have been inactive, you will need to request reinstatement at WP:RFA. Further, following a community discussion in March of 2018, Administrators suspended for inactivity who have not had any logged administrative activity for five years will need to request reinstatement at WP:RFA. This removal of access is procedural only, and not intended to reflect negatively upon you in any way. We wish you the best in future endeavors, and thank you for your past administrative efforts. — JJMC89 bot 00:01, 25 March 2018 (UTC)
ArbCom 2018 election voter message
ArbCom 2019 special circular
Administrator account security (Correction to Arbcom 2019 special circular)
ArbCom would like to apologise and correct our previous mass message in light of the response from the community.
Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.
We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.
For the Arbitration Committee, -Cameron11598 21:03, 4 May 2019 (UTC)