Skip to content

Try to explain how to deal with secure 2fa requirements #40665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Try to explain how to deal with secure 2fa requirements #40665

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
123e1b2
Try to explain how to deal with secure 2fa requirements
jsoref Oct 3, 2025
c546b88
Add another instance of `exclusively`
jsoref Oct 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...r-your-organization/requiring-two-factor-authentication-in-your-organization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,9 +71,9 @@ Before you require use of two-factor authentication, we recommend notifying {% i

### Requiring secure methods of two-factor authentication in your organization

Alongside requiring two-factor authentication, you can require that organization members, billing managers, and outside collaborators use secure methods of 2FA. Secure two-factor methods are passkeys, security keys, authenticator apps, and the GitHub mobile app. Users who do not have a secure method of 2FA configured, or who have any insecure method (such as SMS) configured, will be prevented from accessing organization resources.
Alongside requiring two-factor authentication, you can require that organization members, billing managers, and outside collaborators exclusively use secure methods of 2FA. Secure two-factor methods are passkeys, security keys, authenticator apps, and the GitHub mobile app. Users who do not have a secure method of 2FA configured, or who have any insecure method (such as SMS) configured, will be prevented from accessing organization resources.

Before you require secure methods of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers and asking them to set up secure 2FA for their accounts. You can see if members and outside collaborators already use secure methods of 2FA on each organization's People page. For more information, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled).
Before you require secure methods of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers: instructing them to set up secure 2FA for their accounts and then remove insecure methods of 2FA (including SMS). You can see if members and outside collaborators already exclusively use secure methods of 2FA on each organization's People page. For more information, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled).

{% data reusables.organizations.secure_two_factor_authentication %}
{% data reusables.organizations.secure_two_factor_authentication_confirm %}
Expand Down
Loading