Google allows Gmail username changes without losing data, prompts developers to update authentication systems
Google has introduced a feature allowing Gmail users in the US to change their username without losing data. The update requires developers using Google Sign-In to review authentication systems to prevent account duplication and ensure seamless user access.
Hyderabad: Google has rolled out a new feature allowing users in the United States to update their Google Account username without losing access to their existing account, emails, or stored data.
The move addresses a long-standing user concern, as many individuals wish to change outdated email addresses that no longer reflect their identity due to personal or professional changes.
Under the update, users can modify their username while retaining their original email address as an alternative linked to the same account. Both email addresses will function simultaneously, directing messages to a single inbox. Users will also be able to send and receive emails using either address.
Previously available only to business users on Google Workspace, the feature is now being extended to consumer Gmail accounts.
Impact on platforms and developers
The update has important implications for platforms that rely on “Sign in with Google” or use email addresses as user identifiers.
For platforms that already use a unique subject ID to identify users, no changes are required. The subject ID remains constant regardless of any changes to a user’s email address.
However, platforms that rely on email addresses as identifiers may face challenges. If users change their username, systems that depend on email-based identification could fail to recognise existing accounts, potentially resulting in duplicate accounts or loss of access.
Google noted that if an existing OAuth authorisation remains active, the old email address will continue to be shared to maintain continuity. However, if access is revoked and restored, the updated email address will be provided, which could disrupt user recognition.
For users who sign in using email and password, the experience will remain unchanged, as their original email address will continue to function. However, issues may arise if such users later attempt to log in via Google Sign-In using a new email address, potentially creating duplicate accounts.
Passkey-based authentication systems will not be affected by the update.
Recommendations for developers
Google has advised developers to adopt subject ID as the primary user identifier to ensure consistency. It also recommends enabling email-based account recovery and allowing users to update their email addresses within platform settings.
These steps, the company said, will help maintain seamless user experiences and prevent authentication-related issues.
The company has encouraged developers to review their authentication systems and implement necessary changes as the feature rolls out.
