Skip to main content

Accepting Membership In Somebody's Blog

When somebody invites you to be a member of a blog
  • To read a private blog.
  • To become an author.
  • To become an administrator, or maybe the new owner of the blog.
You get a token in your email, attached to a membership invitation. When you exercise the token, by clicking on the link in the email, you connect the blog with your Blogger account. What you do, when you exercise the token, affects both your immediate and future access to the blog in question - and you need to understand the details.

To accept membership in someone's blog, you are required to provide a Blogger account, or to setup a new Blogger account.

When you accept membership, you see a modified Google login display.

You should see a version of the standard Blogger / Google login display. There are several possibilities, when you use the Blogger / Google login wizard.

Note that the invitation - to a private blog or a team blog - has an expiration date.

If you intend to accept the invitation, you should consider it seriously, and act promptly. If the invitation includes a "Preview" option, use the option only to view the blog once - then accept membership, promptly.

Remember the account name / email address, and the password.

The login process will not verify for you, that you are using the correct Blogger account - that is your responsibility.

Always use the correct account, when accepting membership. Make a note of - or memorise - the account name / email address, and the password. Do not depend upon account / blog recovery, for routine blog access.

Verification of details varies, by GMail or non GMail email address.

When you wish to accept blog membership using a Google email address, you provide the password for that account, and the password is verified against the account. This verifies that you own the account in question. Blogger / Google accounts based upon GMail accounts are authenticated, and account ownership is verified.

When you wish to accept membership in a blog using a Blogger account based upon a non Google email address, you provide the password for the Blogger account, and the password is verified against the Blogger account (for an existing Blogger account), or a new Blogger account is setup. In neither case is ownership of the non Google email address verified, nor is the password checked against the non Google email account.

You are allowed to accept membership using any Blogger account that you may have, or may create - regardless of the email address used in sending the invitation, by the blog owner.

If you accept membership using an email address / Blogger account that does not appear in the original Permissions based invitation, your membership acceptance should, even so, be accepted - provided the mysterious "100 members, total" limit is not exceeded.

Possibilities for more problems come later.

Changing the password varies, similarly.

When you change the password for your Google / GMail account, the password for the Blogger account changes too - since it's really one account. When you wish to change the name of the GMail / Google account, you have to setup a new account, and transfer all assets to the new account.

The latter process is clumsy, and complex - but whether you change the account name, or the password, you know what you have done. And the account name, and password, is always synchronised.

When you change the password for a non Google account, that's all that changes. If you have a Blogger account that's based upon a non Google email address, that password does not change - unless you change it intentionally, and separately.

When you rename a non Google email account, or setup a new non Google email account to replace an existing account, again, your Blogger account does not change.

Access recovery of a non GMail Blogger account requires account access.

If you later become confused about a Blogger account name or password, and the Blogger account was based upon a non Google email address, you will need access to the non Google email account to recover the Blogger account or reset the Blogger password. Lack of access to the non Google account, whether it was originally yours - or whether it never existed in the first place, will leave you unable to manage your blog.

As always, you are responsible for using the right Blogger account when accepting membership - just as you are responsible for proving your identity or membership, in general.


Ashwin Acharya said…
Hi there. For a while I was stuck (being the noob I am), but this article was fantastic, very easy to follow and very informative. Thank you very much! :)

~ A.A.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: