Merge pull request #385 from rubygems/ui-only-removed

Remove ui only documentation
rubygems · Dec 30, 2024 · 648d58c · 648d58c
2 parents 85834db + ec59237
commit 648d58c
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 4 deletions.
diff --git a/api-key-scopes.md b/api-key-scopes.md
@@ -103,7 +103,7 @@ If you are using a key to modify only one of your gems, please consider gem scop
 Enable MFA on specific API keys
 -----------------------------
 
-If your account has MFA enabled on the **UI only** or **UI and gem signin** [authentication level](https://guides.rubygems.org/setting-up-multifactor-authentication/#authentication-levels), you have the option to enable MFA on a specific API key. This will require an OTP code for `gem push`, `yank`, `owner --add/--remove` commands.
+If your account has MFA enabled on the **UI and gem signin** [authentication level](https://guides.rubygems.org/setting-up-multifactor-authentication/#authentication-levels), you have the option to enable MFA on a specific API key. This will require an OTP code for `gem push`, `yank`, `owner --add/--remove` commands.
 
 You can toggle this option when creating or editing an API key on the UI.
 ![New API key with MFA enabled](/images/new-mfa-api-key.png){:class="t-img"}

diff --git a/setting-up-multifactor-authentication.md b/setting-up-multifactor-authentication.md
@@ -23,13 +23,14 @@ When you register a new device or enable MFA for the first time, we will enable
 MFA for both the UI and the API. If you go to the "Edit Settings" page again, in the "Multi-factor Authentication" section, you
 will see a dropdown menu with these options:
 
-- **UI only (Deprecated)**: sign in from browser, updating MFA levels and resetting password will require OTP code. These are referred to as UI operations.
 - **UI and gem signin**: UI operations and `gem signin` will require OTP code.
 - **UI and API**: UI operations, `gem signin`, `push`, `owner --add` and `owner --remove` will require OTP code.
 
-Note: If you are on the "UI only" or "UI and gem signin" authentication level,
+**UI only** was previously a valid MFA level. However, it has been removed, and only accounts that are currently at that level will still see it in the dropdown.
+
+Note: If you are on the **UI and gem signin** authentication level,
 you can selectively enable MFA on specific API keys (see [API key scopes](https://guides.rubygems.org/api-key-scopes/#enable-mfa-on-specific-api-keys)).
-This is different from the "UI and API" level as MFA is enabled on all API keys by default and cannot be selectively enabled.
+This is different from the **UI and API** level as MFA is enabled on all API keys by default and cannot be selectively enabled.
 
 Steps to change your MFA level: