---
title: "Move an authenticator from one phone to your team"
description: "Move a shared account’s authenticator setup from one phone to your team. Check membership, preserve recovery access and test the new sign-in."
canonical: "https://sharedmfainbox.com/blog/move-authenticator-to-team"
author: "The Shared MFA Inbox team"
published: "2026-09-23"
updated: "2026-09-23"
---

# Move an authenticator from one phone to your team

> Move a shared account’s authenticator setup from one phone to your team. Check membership, preserve recovery access and test the new sign-in.

_By The Shared MFA Inbox team, Product. Published 2026-09-23, updated 2026-09-23. About 6 minutes to read._

To move a shared company account from one person’s authenticator to Shared MFA Inbox, an authorized person needs access to that service’s security settings. Add a supported setup to MFA Accounts, complete the service’s confirmation step and test a real sign-in. Keep a working recovery route until the move has been checked.

This is a change to how your team reaches another service. Importing a setup here does not reset that service, prove ownership of its account or remove the old setup from a phone. Work through one account at a time so that a mistake affects one tested change rather than the whole team’s access.

## Before you start, check whether the account should be shared

Look for the service’s own option to add people with separate logins. Use that where it meets the need. It gives the service a way to grant roles and record actions by person. A shared authenticator can help a permitted company login, but it cannot create individual roles inside that login.

Confirm that the account owner approves the move and that the service allows the arrangement. For a client account, agree who should have access and how control will return to the client. For a named signatory or personal account, do not assume a shared setup is appropriate just because its QR code can be scanned.

Choose a quiet time when the current owner is available. Avoid making the first change minutes before a payment deadline, live launch or shift handover. Leave enough time to find the service’s recovery instructions and stop safely if the new method does not work.

## Check the destination team before touching the key

Every member of the selected team can use every authenticator account saved in it. Read the full member list, including contractors and people who joined only to read SMS. There is no per-account grant that you can apply after import to narrow that audience.

A name such as “Finance only” is a label, not an access rule. If some team members should not generate codes for the account, choose a team with the right membership or use the outside service’s own controls. Do this before the setup is added. An access mistake is not fixed merely by renaming the entry.

Also choose who will own the change. That person should be able to reach the service’s security settings and finish its setup flow. They need a way to contact the account owner if an unexpected approval or recovery step appears. Do not make the move depend on someone who has already left.

## Save a recovery route that does not depend on this change

Find the service’s recovery codes, backup method or account-recovery instructions. Keep recovery codes in the secure location your company approves. Confirm who can reach that location when the normal account owner is away. Do not paste codes into the migration ticket, a chat message or a public document.

Read what the next setup action will do. Some services let you add another method before removing an old one. Others replace the old setup during the change. If replacement is required, confirm a separate recovery route first. Do not assume the phone will keep working just because it still displays a code.

An open browser session can help you finish setup, but it can expire and is not a substitute for recovery. If you have no working way into the source account, use that service’s recovery process. Shared MFA Inbox cannot recover the account or create a valid setup key for it.

## Get the setup from the service’s own security page

Use the service’s supported add or replace authenticator flow. It may show a QR code, a setup link or a manual key. That information is the setup credential used to make future codes. It is not the short code you see during an ordinary sign-in, and a screenshot of a login code cannot replace it.

Do not assume a transfer QR from a different authenticator app uses the same format. Follow a supported setup route and check the details before saving. Shared MFA Inbox accepts supported QR images, setup links and manual keys; it does not import push approvals, passkeys or physical security keys.

Handle a QR image or setup link with the same care as a password. Use it only in the approved setup flow. If you created a temporary file, review where it was saved and whether it entered chat, email or a shared folder. Clean up those temporary copies under your company’s credential-handling process.

## Find the account. Generate the code.

MFA Accounts preview with fictional company data and a sample authenticator code with its expiry countdown.

MFA Accounts — Add MFA account. Search by service or account.

Authenticator codes for the accounts you have access to.

Google Workspace (operations@example.com). Sample code 482910. Expires in 24s. Edit Google Workspace operations@example.com.

Slack (engineering@example.com). Edit Slack engineering@example.com.

Microsoft 365 (finance@example.com). Edit Microsoft 365 finance@example.com.

## Add the account and check its details

Open MFA Accounts in the intended team. Upload or paste the QR image, paste the setup link, or enter the manual key. Review the service and account names, then check the type and other setup details. Keep the values supplied by the service rather than changing them until a code seems to work.

Use a name the next teammate will understand. “Supplier portal — depot” is more useful than “New account.” If the same service is used for several companies or regions, include that distinction. Clear names reduce the chance that someone tries a valid code from the wrong account.

Saved setup keys are stored in encrypted form. The server uses them to generate codes and does not return the saved key to teammates. That is the product’s storage model, not a claim that the service cannot read the key. Read [security and access](https://sharedmfainbox.com/security) if this distinction affects your company’s choice.

## Finish the service’s confirmation step

Generate a code from the saved entry and enter it into the source service’s setup screen. The service may require that step before it treats the new method as active. Seeing digits here proves only that a code was generated; it does not prove that setup finished at the other end.

For a time-based setup, use the expiry shown in the app. If the code expires while you are switching tabs, request a current one. Requests made in the same time window can return the same code. There is no need to keep clicking until the digits change.

If the service refuses the code, check the selected account and setup details before trying again. Stop repeated attempts if you are unsure or the service warns of a lockout. Use the working recovery route or the service’s help process. Do not remove the old method merely because the import itself succeeded.

## Prove the handover from another person’s login

After setup is confirmed, open a separate browser session and test a real sign-in to the service. Keep the original setup session available until this test passes. Choose a harmless task, such as viewing a page you already have permission to read, rather than changing a live order or billing setting.

Next, ask another intended team member to sign in to Shared MFA Inbox as themselves. They should find the correct account, generate a code and complete their own sign-in at the service. Do not forward your code to them for this test. The point is to prove they can get a code without you.

Record the service, account owner, destination team, date and result. Leave the key, QR image and short code out of the record. If a shift or another time zone relies on this account, have someone from that group try too while help is still available.

## Decide what to do with the old setup

Copying the same setup key to a new place does not invalidate a copy on the old phone. If you need the old copy to stop working, use the source service’s supported process to replace or revoke that setup. Then update the team’s saved entry with the current setup and test again.

Likewise, deleting the entry from MFA Accounts does not change the source service’s security settings. That deletion removes the team’s entry here. Arrange another working sign-in method before doing it, especially if this was the team’s only usable authenticator setup.

Once the new route works, tell the team where to find the entry and who owns recovery. Review any saved recovery codes, old sessions and account passwords as part of the handover. The [offboarding checklist](https://sharedmfainbox.com/blog/shared-mfa-offboarding-checklist) is useful when the move is part of an employee or agency leaving.

## Move the next account only after this one is complete

A complete move has an agreed audience, a confirmed setup, a tested second person and a documented recovery owner. If one of those is missing, finish it before importing the next account. Bulk changes can hide a small mistake until the first urgent sign-in exposes it.

Some accounts will use different methods. Keep the [authenticator and SMS comparison](https://sharedmfainbox.com/blog/authenticator-app-vs-sms-for-teams) beside your account list so you do not buy a number for a service that needs none. Your first shared authenticator account is free; additional accounts are billed monthly or annually. See [pricing](https://sharedmfainbox.com/pricing). Add SMS only where the service requires texts and a test confirms the number works.

## Try shared authenticator codes with your team

Create a free team and test one account your team is allowed to share. No phone number is needed for authenticator codes.

- [Create free account](https://app.sharedmfainbox.com)

_No credit card required. Your first authenticator account is free._

---

Canonical: https://sharedmfainbox.com/blog/move-authenticator-to-team

Every page of this site is also available as Markdown. Site map: https://sharedmfainbox.com/llms.txt