That rule is enforced by the Permissions wizard, which gives any administrator the choice to demote or remove any administrator, from the Permissions list - but only when there is at least one other administrator in the list.
When the Permissions list is displayed, if there are at least two members with administrative authority, each administrator entry, in the list, has a link to demote or remove that member. If there is only one member with administrative authority, there is no such link - and that member can be neither demoted or removed from the list.
As long as only the Permissions wizard is used, to demote or remove administrators, this article would be meaningless (see the above link). But, there is another way for administrators to be removed - and this occasionally leaves blogs with no administrator.
If the only way to lose an administrator (or member) from a blog was by using the Permissions list to demote or remove, then the Permissions list setup, as described above, would be sufficient.
The account deletion process does not check team blog member status.
Unfortunately, the Google - and Blogger - account deletion processes don't consider the member lists for the blogs owned by the account. When a Blogger account is deleted, the fate of the blogs owned, by that account, has to be decided later.
Any blogs which have only one member (the owner) are either frozen or deleted - as with only one owner, there is no need to keep those blogs. Any blogs with more than one member simply lose that one member. But what if a blog has more than one member, but only one administrator - and that one administrator deletes his Google / Blogger account?
A team blog with one administrator - and that account deleted - is in trouble.
With a team blog with one administrator, and one or more authors, losing the one administrator would leave a blog that was being published (by the authors), but could not be managed (because there was no administrator). This would, in the past, lead to panic in the forum.
The administrator for my blog deleted his Blogger account - and now my blog has no administrator! What do we do now?
With no administrator existing, Blogger Support would be summoned, and would have to determine whether a blog:
- Had no administrators.
- Had at least one author.
- Was being requested by a person who had a legitimate need to request control (a former administrator, or a current author).
Blogger provides for team blogs with no administrator, using recovery.
To allow control recovery without needless delay, and avoid the need for endless detail in verifying any such panicky report, Blogger Engineering made a simple procedural change.
The "Forgot your username or password?" wizard, when control recovery is requested for a team blog with no administrator, simply sends the appropriate access tokens (aka "login instructions") to all blog authors - as long as the membership list is well maintained. Any blog authors, able to receive the login instructions, then become de facto administrators - and can jointly determine the fate of the blog.
This allows the control recovery process to be automated, with the risk of possible hijacking of actively owned (administered) blogs reduced. This simply requires that at least one blog author uses a Blogger account based on an active and genuine email address - and if necessary, can search persistently for the email sent.
In team recovery, each blog author must act honourably.
When this reset process is done, each blog author initially has the same power as each of the other authors. Blogger leaves it to all authors to act honourably - and to politely choose one or more authors to be administrators.
As long as the author submitting the reset process is able to locate the email message in his Inbox immediately, he can make himself the sole administrator - if he decides. If one of the authors has problem locating the email, it's possible that the other newly appointed administrators could unwisely hijack control of the blog.
If this happens, it will be up to the authors to jointly establish order. Blogger Support will not be involved in any conflict.
With larger blog teams, more chance that one member will act dishonourably.
The more authors a given blog may have, the greater the chance that one author, receiving the email message, may act dishonourably, and hijack the blog. In cases where there are a large number of authors (precise number not known, right now), Blogger will defer to the author requesting the reset.
With blogs owned by large teams, recovery is by individual authors.
In the latter case, the author requesting the account reset can enter his email address, that is used by his Blogger account, into "Forgot?" - and have the password reset email sent directly to him. If that author cannot locate the reset email, another author must try his luck.
Eventually, one author hopefully will be able to receive the email - and the blog, once again, will have an administrator.