New sign-in page for Google Apps services

All Google Apps services are getting a new sign-in page that’s consistent regardless of the URL from where you sign in. For example, users will sign in to the same way they sign in to The new sign-in page began rolling out to select Google services in 2013, and will start rolling out to Google Apps for Business, EDU, and GOV domains in January 2014. The rollout will complete on March 1, 2014. Users may continue to see the deprecated sign-in page until that time.

The new sign-in page provides a streamlined and cohesive sign-in experience for all users, an account chooser that makes it easy to switch between Google accounts, and security enhancements, including advanced bot detection and improved account hijacking protection.

  • The new sign-in page requires users to sign in with their full email address (example: (The old sign-in pages only required users to enter their username, but that convenience was offset by the complex URLs users needed to access those sign-in pages.)
  • The Stay signed in checkbox is selected by default. Users who want to sign out of Google Apps automatically when they close their browser should deselect this checkbox. Users who leave this checkbox selected when they sign in will remain signed in for two weeks or until they click the Sign out button that appears when they click their photo in the upper right corner.

Note the following:

  • All links to your custom URL will still work. They'll simply redirect to the new page.
  • The Google Apps sign-in page can no longer be personalized with colors and custom logos.
  • In SSO-enabled domains with a network mask, users will see the new Google sign-in page when they log in from outside of the SSO network mask.
  • For SSO-enabled domains without a network mask, accessing the service specific sign-in URLs will continue to redirect the user to the configured SSO login page.
  • When you sign in to a Google Apps Sites page, a slightly different version of the new sign-in page appears if:
    • Your domain uses SSO without a network mask
    • OR
    • You’re signing in within your SSO network mask