Shared Two-Factor Verification

For shared and standing development orgs, the verification text number is tied to a Google Voice number that posts to a chat room (such as HipChat or Slack), for shared access. 

Protecting an account with only a username and password can be insecure.

To provide more security, some systems, like Salesforce orgs, use two factor authentication. If a login comes from a different computer, or a password reset is requested, the system sends out a one-time code you can use for authentication. Most systems can send the code by email or SMS text message.

Of course, everyone already receives too much email, and many of us prefer to communicate by chat or text message. 

Since you can post a email message to a chat room via most chat platforms, including HipChat, Slack, and Ryver, it's easy to setup a Gmail account with Google voice, attach it to your chat room. (See Resource Checklist.)

Voila! Any email authentication messages for the shared resource are now surfaced in the chat room. (As well as the Gmail account, if you want to login there.)

No more cluttering up your own email client with a zillion filters to keep shared messages out of your face!

Resource Checklist

  • Create a chat room for shared authentication messages.
  • Enable the room for email. 
  • Create a Gmail account for the chat room, and setup Google Voice
  • Store the credentials for the account in your Password Manager. (Important!)
  • Forward emails from the gmail account to the chat room.
  • Use the gmail account as the email address for the shared resource.
  • For systems that support SMS verification, use the Google Voice number as the mobile phone number. 

Please submit feedback to the DreamOps Success Group