Thanks for bringing this up--the concept of salt makes a lot more sense to me now.
So one-salt-per-user is clearly better, but one-salt-for-all is still better than no-salt-at-all.
A common and simple password setup is hash(username+password) or hash(private_account_attribute+password).
Also, use bcrypt/scrypt/similar.
Not exactly. Having a salt at all mitigates rainbow table attacks, having a unique salt per password also limits brute-force attacks (you can't brute-force the whole table trying out cleartexts with a given salt, you have to brute-force each password individually).
Having a global unique salt is already better than no salt at all.
Usually we fetch user/email, hash password, compare to hash in database - authenticate if match or deny if not.
You might feel like adding a hidden component but it won't noticeably help security and it's not a salt.