Meta Ad Account Access Troubleshooting

Overview

Meta's Business Manager permission system frequently fails to propagate access correctly when a new ad account is added to a client's partner portfolio. This is a recurring issue across clients and is not specific to any one account configuration. The fix is reliable once identified, but requires knowing the exact sequence of steps.

The Problem Pattern

When Asymmetric creates a new Meta ad account and adds a client's Business Portfolio as a partner, the client may be unable to see or access the new account — even though the partnership appears correctly configured on the agency side. Symptoms include:

• Client can only see old ad accounts under "Other Assets"
• New ad account (visible in the agency's Business Portfolio) does not appear in the client's Ads Manager
• No invitation email is received by the client
• The client's Facebook Page appears linked to the ad account in the agency view, but the client cannot navigate to it

This occurs because Meta's permission system does not always automatically link a new partner ad account to the individual users within the client's Business Portfolio. The connection between the ad account, the Business Page, and the individual user must be explicitly triggered.

The Fix: Remove and Re-Add Partner with Page Included

The reliable resolution is to remove the client as a partner and re-add them, ensuring the Facebook Page is explicitly included in the new invitation.

Steps

1. In the Asymmetric Business Portfolio, navigate to the ad account's partner settings
2. Remove the client's Business Portfolio as a partner
3. Re-add the client's Business Portfolio as a partner — explicitly include the Facebook Page in the invitation (this is the step most likely to be missed on the first attempt)
4. The client will receive a new email notification granting access
5. The client clicks the link in the email, which allows them to assign themselves to the correct ad account
6. Access is confirmed when the new ad account appears in the client's Ads Manager dropdown

Why This Works

Removing and re-adding the partner relationship forces Meta to regenerate the invitation and permission chain. Including the Facebook Page in the re-invitation appears to be the key trigger that correctly links the ad account to the client's user profile.

Key Notes

• The client's Facebook login is personal — Meta requires a personal account to access a business account, which adds confusion when troubleshooting
• The old ad account (previously used by the client independently) will still appear under "Other Assets" and is separate from the new agency-managed account; make clear to the client which account is the source of truth
• Warn the client not to modify settings in the Ads Manager backend once access is granted — they should use it for review only unless guided otherwise
• This issue is not unique to any one client; it is a known Meta platform friction point and should be expected during onboarding

Evidence

Encountered during the ^[1]. Sebastian Gant resolved the issue live on the call by removing and re-adding Avant Gardening as a partner with the Facebook Page included. Tim Stenzel (client) received the new invitation email, clicked through, assigned himself to the account ending in 657, and confirmed access within the same call session.

"This is always a headache with every client until we manage to get it." — Sebastian Gant

Related

• ^[2]
• ^[3]
• ^[4]