Partner access to the client's portfolio

Two ways into a client’s Meta Business Portfolio — and exactly which permissions to ask for

Your client has a Meta Business Portfolio — good, that’s the easy case. Now you need to get inside it the professional way: partner access, business-to-business, no shared passwords, revocable by the client at any time. There are two routes: the client grants it, or you request it from your side and the client only clicks Approve. Learn both — the second one is what separates agencies that launch in a day from agencies that spend a week emailing screenshots.

Two businesses connected by a bridge — partner access, business to business

People access vs. partner access

Meta has two mechanisms for letting someone into a portfolio, and clients mix them up constantly. Know the difference cold, because you’ll be the one explaining it:

People accessPartner access
Who it’s forIndividuals — the client’s own employeesBusinesses — agencies, freelancers with a portfolio
How it’s grantedEmail invite to one personYour agency’s Business Portfolio ID
Your teamClient invites each of your teammates one by oneYou assign your own people to the client’s assets yourself
When someone leaves your agencyClient has to remember to remove themYou remove them on your side — client does nothing
OwnershipClient keeps itClient keeps it — partner access never transfers ownership

For day-to-day agency work — running ads, managing the Page, reading the pixel — partner access is the answer. It scales: one grant from the client, and you manage your team’s permissions internally. There’s one exception where people access matters, covered at the end of this page.

Before you start: find your Business Portfolio ID

Both routes need your agency’s own portfolio. If you don’t have one yet, create it at business.facebook.com — it takes five minutes and you only do it once, for your agency, ever.

Your ID lives in Business Settings → Business Info — a 16-digit number under your business name. Keep it in your onboarding template; you’ll paste it into every new client conversation.

Route A: the client grants you access

The classic flow. Send the client these steps (there’s a ready-made script you can forward as-is):

1

Open Partners in Business Settings

The client goes to business.facebook.com/settingsPartnersAddGive a partner access to your assets. Only someone with full control of the portfolio can do this — usually the owner.

2

Enter your Business Portfolio ID

They paste your 16-digit ID. Meta finds your agency’s portfolio by that number — no emails, no invites to individual people.

3

Select the assets to share

Ad account, Facebook Page, Instagram account, pixel/dataset — everything from the checklist. This is the step clients rush: they share the Page and forget the pixel, or share one ad account when there are two. Send them the exact asset names.

4

Set the permission level and assign

For each asset the client picks what your agency can do — then clicks Assign assets. The assets appear in your portfolio within a minute, and you can start assigning your own teammates to them.

Meta Business Settings Partners menu with the two Add options
Partners → Add — the fork between Route A and Route B

Route B: you request access — the client just approves

Fewer steps on the client’s side means fewer things go wrong. From your Business Settings:

1

Send the request

Business Settings → Partners → Add → Ask a partner to assign you their assets. Enter the client’s email (the one tied to their portfolio) and, if you have it, their Business Portfolio ID.

2

Specify assets and permission levels

You choose what you’re asking for — ad account with ads management, Page, Instagram, pixel. Precision here is a professionalism signal: asking for exactly what the job needs, no more.

3

The client approves

They get a notification, review what you asked for (they can trim it), and click Approve. Done — no navigating menus, no screenshots back and forth.

4

Track it in your Partners tab

Pending requests sit in Partners on your side, so you always know which client is holding up which launch.

What permissions to ask for

Ask for task-level (partial) access matched to the job — it’s what security-conscious clients expect, and it protects you too: you can’t be blamed for what you couldn’t touch.

AssetAsk forEnough to
Ad accountManage campaignsLaunch, edit, and optimize ads
Facebook PageAds + content (or messaging if you run the inbox)Publish click-to-WhatsApp ads, manage responses
Instagram accountMessages + adsDM automation and ad placements
Pixel / datasetManageFire CAPI events, build audiences
Portfolio-wideDon’t askFull control of the whole portfolio is almost never needed — and asking for it triggers the “is this safe?” conversation
Meta asset sharing step with task-level permission toggles
Task-level permissions per asset — everything the job needs, nothing more

The exception: connecting WhatsApp to Chatfuel

Partner access runs your ads. But when it’s time to connect the client’s WhatsApp, Meta’s authorization flow requires the person clicking Connect to be logged in with a Facebook account that has Full control of the client’s business portfolio — the client can verify who has it at business.facebook.com/settings/people. Two clean ways to handle it:

  • Screen-share. The client logs in and clicks; you navigate. Fifteen minutes, no extra access. This is also the only way for Instagram — that authorization must come from the client’s own Instagram account.
  • People invite with Full control. For clients you’ll manage long-term, have them add one senior person from your team in Business Settings → People with Full control. Reconnections, number changes, and troubleshooting stop requiring the client’s calendar.
Never remove the old admin first

If you’re helping a client clean up their portfolio, make sure the new account has full access and can see the WhatsApp Business Account under Accounts → WhatsApp accounts before removing anyone. Removing the old admin first can lock everyone out of the WABA — and getting it back means a support case with Meta.

When something’s still red

Request never arrived, assets shared but invisible, permissions that don’t let you do anything, an admin who left the company — every access dead-end has a known exit, and they’re all collected in Troubleshooting access issues.

Where to next