Adding an Admin to Meta Business Manager When the Existing Admin's Personal Account Is Disabled

Why a disabled personal profile can strand a Business Manager

A business portfolio (Meta's current name for Business Manager) is not something you log into directly. People sign in with their own Facebook identity, and the portfolio grants each person a permission level. Meta documents two levels for portfolios and the assets inside them: full control and partial access. Only people with full control of the portfolio can add people, assign assets such as ad accounts and Pages, or edit and remove other people's permissions. Full control of a single asset, like one ad account, is not enough to edit permissions at the portfolio level.

That creates a single point of failure. If the only person with full control loses their personal Facebook account, nobody left inside the portfolio has the permission needed to add a replacement admin. In a Meta for Developers community thread, a user whose personal account was disabled reported losing access to a verified Business Manager, a Developer App and a linked Page in one event.

Search Engine Land reports that personal profiles, Pages, ad accounts and Business Manager run as separate systems with their own rules and support paths, so one action against a person can strand business assets that were never accused of anything.

First, diagnose your access state

Work through these checks before filing anything:

1. Can the original person still sign in, or complete a recovery prompt Meta shows at login? Only that person can use a personal-account appeal.
2. Does anyone else still hold full control of the portfolio? A second employee, finance user or agency contact with full control can add people from inside the portfolio. Audit everyone who can still sign in and what each can do.
3. Which layer is affected? The portfolio, a Facebook Page and an ad account are separate. A person may still have access to a Page or ad account when nobody can administer the portfolio.
4. Is there a separate advertising restriction? A restricted ad account is a different enforcement type from a disabled personal profile and has its own review path.

If check 2 finds nobody, the documented options are the portfolio full-control request and, for a Page, the Page admin dispute, both described below.

Access, existence, eligibility and delivery are four separate questions

A lockout can make you assume the worst, or the best, about everything at once. Record these separately and mark anything you cannot see from a signed-in session as unknown:

• Asset existence. Does the portfolio, Page or ad account still exist? In the documented community case the Business Manager stayed verified and the assets continued to exist; the owner simply could not sign in. Meta's documentation reviewed here does not describe automatic deletion of a portfolio or its ad accounts because one admin's profile was disabled.
• Access. Who can sign in and act on each asset today?
• Advertising eligibility. Is there a restriction on the portfolio, Page or ad account itself? If so, Meta documents a review path: on a computer, open Meta Business Support Home, go to Account status overview, select the restricted account and choose Request review under What you can do.
• Live delivery and spend. Whether campaigns keep delivering while nobody can sign in is not something Meta documents for this scenario. Check billing and delivery wherever your team can still see them, and do not assume either that ads paused or that they continue.

A disabled personal profile does not by itself establish that an ad account is restricted. Keep the two diagnoses apart.

The personal-account appeal runs separately

Appeals of a disabled personal account happen on the personal side, by the person whose account was disabled, using the prompts Meta shows them. They are separate from business-asset administration. In the community thread, the user reports that the appeal response was final and that they could not appeal again. Search Engine Land reports that appeal results vary, with some resolving very quickly.

Meta does not publish a timeline or success rate for these appeals in the documentation reviewed here, so do not promise an outcome. Hacked accounts are a different situation and go through Meta's dedicated recovery flows rather than standard support.

Do not make business recovery wait on the personal appeal. The portfolio-level and Page-level request flows below are documented independently of it.

Official flows for granting or recovering admin access

Meta documents three relevant flows, each scoped to a different asset.

1. Normal grants. A person with full control adds people to the portfolio in Meta Business Suite and assigns assets such as an ad account, Page or Instagram account. Only full-control holders of the portfolio can change or remove permissions.

2. Portfolio full-control request. Meta has a request for full control of a business portfolio you claim ownership of. Its eligibility list includes a former employee or contractor with no ownership rights, a business that changed ownership and lost access, and portfolios where no one has full control. Meta instructs you to first try contacting whoever currently has full control and ask them to grant it.

Unresolved: does a disabled sole admin qualify? The list does not say whether a portfolio whose only full-control holder has a disabled personal account counts as one where "no one has full control". Meta does not state whether that person's permissions are suspended, preserved or removed. Treat eligibility as an open question, not a yes or a no, and rely on what Meta's request form presents to you when you are signed in.

3. Page admin dispute. For a Facebook Page, a separate dispute flow exists for gaining access from someone who has full control. Meta requires three documents (an identification document, a signed attestation letter and an ownership document), unaltered and in a non-editable format such as PDF, JPEG or PNG. You start it from Business Support Home by chatting and selecting "Page admin dispute".

Assigning a Business Manager as a Page owner requires being an admin of that Business Manager and having full control of the Page, so portfolio and Page recovery may need to happen in sequence.

A new Business Manager is not a shortcut

Teams often ask whether they can create a fresh Business Manager and pull the stranded ad account into it. Meta's developer documentation describes claiming as a one-time procedure for eligible ad accounts, says an ad account with a confirmed owner relationship cannot be removed from its business, and says agencies should use the business-to-business access model rather than claiming clients' accounts. Nothing in the documentation reviewed here describes a way to take an owned ad account out of its existing portfolio by opening a new one.

Shared access to an ad account still depends on someone with the right permission on the owning side. Treat a from-scratch rebuild as a last resort with unknown verification outcomes. In the community case, the user asked whether re-verifying would fail because the company name and domain were already linked to the disabled account, and no answer was published.

What Meta does not document about this situation

• Full-control eligibility for a disabled sole admin, as above.
• Timelines and evidence standards. Meta lists document requirements for Page admin disputes but, in the pages reviewed, no processing time for those disputes or for portfolio full-control requests, and no equivalent document checklist for the portfolio request.
• Billing and delivery during a dispute. Meta does not publish what happens to active campaigns, balances or payment settings while control of a portfolio is contested.
• Escalation after a final appeal. The community case ended at "you cannot appeal again" with no documented next step.

Where Meta does not publish a procedure, this guide says so rather than inferring one.

Keep a private incident record

Before contacting Meta, write down in one internal place:

• Business portfolio ID, ad account ID(s) and Page ID(s). IDs only, never passwords or session data.
• The last confirmed access: date and time, role if known, and which asset.
• Everyone who can still sign in and what each person can see or change.
• The exact wording of any notice shown at personal login, and separately any notice on the portfolio or ad account.
• Your status for the four questions above: existence, access, eligibility, delivery, each marked verified or unknown.
• Any support case references, with the account that opened each, so you do not open duplicates.

Submit identity, ownership or attestation documents only inside an official Meta support workflow when Meta asks for them, never through third-party forms or unsolicited messages.

Actions that make recovery harder

• Submitting weak paperwork. Meta will not proceed with a Page admin dispute unless all three documents are ready, unaltered and in a non-editable format. Incomplete submissions stall the one documented Page-level path.
• Paying "recovery" services. Search Engine Land reports an underground market of fraudulent services exploiting locked-out users. AdsInfra cannot restore a disabled personal account, and Meta's documented flows do not involve third-party intermediaries.
• Engaging with unsolicited messages. Hijackers have used fake business inquiries and suspension threats over Facebook Messenger to deliver password-stealing malware. A team mid-recovery is a likely target.
• Trying to evade enforcement. Buying or farming profiles, or opening disposable assets to work around a disabled account, breaches platform terms and adds risk.
• Rebuilding on one personal profile again. Meta's managed Meta accounts exist to let people access business tools with work credentials, separate from a personal Facebook account. Whether you adopt them or simply keep more than one full-control holder, avoid recreating the single-admin dependency.