> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/security/mfa-devices/managing-mfa-devices.md).
# Managing MFA Devices
{% hint style="success" %}
#### Required User Credentials
\[**Flosum User**] - Any Role
{% endhint %}
## Overview
Enabling Multi-Factor Authentication (MFA) provides an additional security layer for your Flosum Cloud Apps login. After adding an MFA device to your account, you can manage it through the following actions:
* [#edit-name](#edit-name "mention")
* [#disable](#disable "mention")
* [#enable](#enable "mention")
* [#delete](#delete "mention")
{% hint style="info" %}
For instructions on how to add an MFA device, refer to the following article.
* [Adding an MFA Device](/global-settings/security/mfa-devices/adding-an-mfa-device.md)
{% endhint %}
## Managing an MFA Device
{% stepper %}
{% step %}
### Access Global Settings
1. From any **Flosum Cloud App**, click the **App Switcher** icon at the top of the left sidebar menu.
2. Click **Global Settings**.
3. The **Global Settings** app will open in a new tab.
{% hint style="info" %}
Global Settings can also be accessed by logging in directly via the Flosum Cloud Apps Login URL. See the following article for login instructions.
* [Log In To Global Settings](/global-settings/getting-started/log-in-to-global-settings.md)
{% endhint %}
{% endstep %}
{% step %}
### Select an MFA Device
1. Click **MFA Devices** from the sidebar menu.
2. Click the **Device Name** of the MFA device to manage.
{% endstep %}
{% step %}
### Edit Name
You can modify the MFA device name, but the change will only appear in Global Settings, not in your authenticator app.
1. Click **Edit**.
2. Edit the **Name** textbox to change the name of the MFA device.
3. Click **Save**.
4. The MFA device will be updated with the new name.
{% endstep %}
{% step %}
### Disable
Disabling the MFA device means MFA will no longer protect your account’s login.
1. Click the **Actions** dropdown menu.
2. Click **Disable**.
3. Click **Confirm** in the Disable MFA Device dialog box.
4. The MFA device **Status** is updated to **Disable**.
{% endstep %}
{% step %}
### Enable
If an MFA device is disabled, you can re-enable it to add MFA protection to your account. Once enabled, you must use the same authenticator app that was used to set up this MFA device.
1. Click the **Actions** dropdown menu.
2. Click **Enable**.
3. Click **Confirm** in the Enable MFA Device dialog box.
4. The MFA device **Status** is updated to **Enable**.
{% endstep %}
{% step %}
### Delete
You can delete an MFA device, but after deletion, you'll need to add a new one to re-enable MFA protection for your login.
1. Click the **Actions** dropdown menu.
2. Click **Delete**.
3. Click **Confirm** in the Delete MFA Device dialog box.
4. The MFA device will be removed from the list.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flosum.com/global-settings/security/mfa-devices/managing-mfa-devices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
