diff options
| author | Evan Read <eread@gitlab.com> | 2018-11-13 10:39:21 +1000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2018-11-13 10:53:38 +1000 |
| commit | 20146580a0618e7c9a726c6d53e51d3ca60b63e8 (patch) | |
| tree | 5d70d8989f3897f84468dde83ca9521d759fc12c /doc/security/two_factor_authentication.md | |
| parent | dbb342d4d95d24a1313c64be4a923ea5f759d3fa (diff) | |
| download | gitlab-ce-20146580a0618e7c9a726c6d53e51d3ca60b63e8.tar.gz | |
Resolve Markdown ordered lists not conforming to styleguidedocs/fix-ordered-list-item-prefix
Diffstat (limited to 'doc/security/two_factor_authentication.md')
| -rw-r--r-- | doc/security/two_factor_authentication.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/security/two_factor_authentication.md b/doc/security/two_factor_authentication.md index cd290a80314..b770f2544d2 100644 --- a/doc/security/two_factor_authentication.md +++ b/doc/security/two_factor_authentication.md @@ -13,8 +13,8 @@ You can read more about it here: Users on GitLab, can enable it without any admin's intervention. If you want to enforce everyone to set up 2FA, you can choose from two different ways: - 1. Enforce on next login - 2. Suggest on next login, but allow a grace period before enforcing. +- Enforce on next login. +- Suggest on next login, but allow a grace period before enforcing. In the Admin area under **Settings** (`/admin/application_settings`), look for the "Sign-in Restrictions" area, where you can configure both. |