Username Alias

I strongly support this feature request. In corporate environments, it's common to encounter scenarios where multiple internal systems share a single underlying account and password but require different username formats as outlined in this post.

Currently, users have to manage this situation by maintaining separate 1Password entries for each username variation. Although workable, this method is inefficient, creates redundancy, complicates password updates, and generates unnecessary alerts in Watchtower about apparent password reuse.

The proposed solution—allowing username aliases to be linked specifically to individual websites within a single entry—addresses this problem effectively. Although it introduces additional complexity in terms of UI and underlying data management, this complexity is worthwhile because it directly aligns with authentic and widespread enterprise use cases.

My own positive professional experience with 1Password, even though it is not the officially mandated password manager at our organization, led me to adopt it personally. Implementing username aliases would significantly improve usability, streamline credential management, and reinforce 1Password’s value in professional settings.

Thank you for considering this essential feature enhancement!