Set up an authenticator and manage your sessions

Complete authenticator enrollment and use the separate session controls.

Open Personal Account → Security in Spaces, or Profile → Security, to manage your account’s authentication settings.

Enroll an authenticator

  1. Find Multi-factor authentication (TOTP) and use the enable action.
  2. Open your authenticator app and scan the QR code. If scanning is unavailable, enter the displayed setup code manually in the authenticator.
  3. Enter the six-digit code generated by the authenticator into Node Cluster.
  4. Choose Verify & enable.
  5. Wait for the successful verification and the enabled state. Seeing the QR code alone does not mean enrollment is complete.

Keep the authenticator available for future verification prompts. The setup code and QR code are account secrets; do not put them in project files or a support screenshot.

Use Cancel if you decide not to complete the setup. If a verification fails, check that you used the current code for this account and follow the error shown.

Use the authenticator at sign-in

When the app requests verification, enter the code from the enrolled authenticator. Password recovery can also ask for this code. An organization invitation does not remove the account’s verification requirements.

This is an individual-account setup guide. It does not establish that your organization has an enforced MFA policy for every sign-in method or every member.

Sign out other sessions

In Current session, choose Sign out other sessions and check the result. The action requests revocation of other sessions while keeping the current session. The page is not a complete device inventory, and the confirmation should not be read as a guarantee of instantaneous loss of every already-issued token.

Use the normal sign-out control if you also want to leave the current session.

Disable or recover MFA

If you intentionally want to remove the enrolled factor, choose Disable MFA, read the confirmation, and confirm only when that is the intended change. Check the result before assuming the factor was removed.

If you cannot sign in or no longer have your authenticator, use the established support channel for recovery. No self-service recovery-code or administrator-reset procedure is documented here because those flows were not established in the reviewed interface.