# New admins can't enroll 2FA when enforce second factor is set to Staff

**URL:** <https://meta.discourse.org/t/new-admins-cant-enroll-2fa-when-enforce-second-factor-is-set-to-staff/286042>\
**Category:** Bug\
**Created:** [November 20, 2023, 7:22am UTC](https://meta.discourse.org/t/new-admins-cant-enroll-2fa-when-enforce-second-factor-is-set-to-staff/286042 "2023-11-20T07:22:03Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)\
**Post date:** [November 20, 2023, 7:22am UTC](https://meta.discourse.org/t/new-admins-cant-enroll-2fa-when-enforce-second-factor-is-set-to-staff/286042/3 "2023-11-20T07:22:04Z")

</div>

The page just randomly reloads with the following errors in browser console:

> Uncaught TypeError: t is undefined  
> hasSecondFactors second-factor.js:47  
> u handle-descriptor.js:55  
> get Ember  
> untrack validator.js:670  
> Ember 3  
> second-factor.js:47:11

Some errors might have lost because the page immediately reloads when I click the Add Authenticator button.

---

_[View the full topic](https://meta.discourse.org/t/new-admins-cant-enroll-2fa-when-enforce-second-factor-is-set-to-staff/286042)._
