It’s back now...must have been a “bug” ;) 

​@ElvaMiro 

Thank you for your reply. However, I need to respectfully push back on the suggestion to gather more votes and use cases for 2FA implementation:

1. We already have concrete evidence of security breaches affecting non-enterprise customers (as demonstrated by the recent 150+ unauthorized members incident).
2. The technical implementation is largely complete - 2FA is already working for enterprise customers, the infrastructure exists, and the documentation is written.
3. The use case for 2FA is universal and well-established: protecting user accounts from unauthorized access. This is security fundamentals, not a feature request.
4. Multiple paying customers have been requesting this for years, providing feedback and use cases throughout that time.

This isn't a matter of gathering more feedback or proving demand - it's about providing a basic security feature that's industry standard. Every day without universal 2FA puts more customer workspaces at risk of compromise.

As someone who has worked in digital product development, I can confidently say that extending existing 2FA infrastructure to all paying customers requires minimal technical effort compared to the initial implementation. The barrier here isn't technical or about understanding use cases - it appears to be purely a business decision to keep it as a premium feature.

I genuinely appreciate you engaging with the community on this, but we need action on this security issue, not more voting and use cases. Meanwhile, real security breaches continue to occur, putting customer data and intellectual property at risk. How many more workspaces need to be compromised before this basic security feature is made accessible to all paying customers?