Humble Bundle Redesign Removes Two-Factor Verification From Settings

What happened

Humble Bundle, the storefront for games and other software, has launched a redesigned site, and its settings page no longer offers a way to add or update two-factor verification methods. Kotaku first reported the change, and The Verge has since covered it.

PC Gamer pointed to a mismatch: Humble Bundle's support pages still discuss two-factor verification, so help content describes a capability the settings page no longer appears to provide. The reporting available here does not include a published explanation from the company or a timeline for restoring the option.

Why it matters

Account settings are where customers manage trust. Two-factor verification is one of the few controls a user can add to protect a purchase history and a library of digital content, so its removal during a visual refresh is more than a cosmetic change. It is a functional regression that users are unlikely to notice until they need the protection.

The case also shows how redesigns can drift away from the documentation that surrounds them. When help articles describe features that the interface no longer shows, customers lose the ability to self-serve and are more likely to contact support. For operators, the gap between product and documentation is a service-design issue as much as a security one.

The Renascence take

Most coverage of a redesign focuses on how the new interface looks. The more useful question is what the old interface was doing for users that the new one has quietly stopped doing. Teams should audit every function of a legacy screen against the new one before launch, and treat security controls as core journeys rather than settings buried in a menu.

A redesign that looks cleaner but removes a protection has not improved the experience; it has moved the risk onto the customer. Users judge a service by what it lets them do when something goes wrong, and account security is exactly that moment. Customer-obsessed operators should map every feature in a redesign against a documented inventory of user jobs, and keep help content in sync with the live product as part of the same release. If the documentation still promises a feature, the product team owes customers either the feature or an honest notice that it has gone.