How to Add a Partner to Facebook Business Manager

what is the difference between a partner, a user and an agency account?

A partner is another Business Manager, a user is an individual login, and an agency account is usually operator slang for either a partner business or an ad account controlled by that agency. That distinction matters because each route leaves a different control trail. Partner access lets a separate business request or receive access to assets. User access adds a person inside your own business. An agency ad account means the agency owns the ad account and may only share reporting, invoices or campaign work back to you.

If you are searching how to add a partner to facebook business manager, the real decision is whether you want to share assets or transfer control. Partner access is for shared operation; ownership transfer is a different move, and the cleanup path is covered separately in how to transfer Facebook Business Manager ownership.

We separate these three mechanisms because support threads and scam reports routinely collapse them into one word. In our read, that collapse creates most bad permission decisions: a founder adds a person when a vendor needed partner access, or accepts a partner request when the sender should have been verified first. Meta’s CAPI documentation uses similarly strict identity boundaries in another part of the stack: the server event needs a dataset ID, an access token and customer-information parameters, per Meta’s customer-information parameter docs. The principle carries over: know which identity is being granted power before you approve anything.

what is the click path for each one?

The click path depends on whether you are adding a business, adding a person or accepting a request. In Business Settings, partner access normally starts under Users or Partners, then Add or Assign assets; person access starts under People; agency-owned ad accounts start from the agency’s side if the agency controls the account.

For partner access, the clean version is: Business Settings, Partners, Add, enter the partner’s Business ID, choose the asset, choose the task permissions, then send. If the vendor sends the request first, you review the requesting business, the requested assets and the exact permissions before accepting. That review step is where the Facebook Business Manager partner request scam usually succeeds or fails.

For user access, Business Settings, People, Invite people, enter the email address, choose employee or admin, then assign assets and task permissions. If two-factor authentication, a login check or account recovery blocks the invite, fix identity first; our related note on Facebook Business Manager 2FA not working covers the order because permission work gets messy when login state is unstable.

• Partner route: add a Business ID, then assign assets and tasks.
• User route: invite an email login, then assign assets and tasks.
• Agency-account route: confirm who owns the ad account before you spend into it.
• Request route: inspect sender, asset list and permission set before accepting.

which permission levels exist and what does each grant?

Permission levels split into business roles and asset tasks, so the practical question is not “admin or not” but “admin over what?” A business admin can change high-level settings inside the business. Asset permissions decide what someone can do with a page, ad account, pixel, dataset, catalog or Instagram account.

Most operators overuse admin access because it resolves the next blocker quickly. That is usually the wrong trade. A media buyer who only needs to launch ads on 1 ad account does not need business-admin rights, page control, finance control and pixel control. Give the task permission that matches the job, then widen it only when a real error message proves the missing permission.

The claim people argue with is simple: partner access is often safer than adding an outside buyer as a person in your business. It sounds broader, but it keeps the vendor’s staff management on the vendor’s Business Manager instead of turning your business into their user directory. We counted the failure mode this way: removing one partner relationship is cleaner than finding every contractor the agency invited through individual seats.

what does the partner see about your spend and your assets?

A partner sees what the assigned asset and permission level allow them to see, not your entire business by default. If you assign one ad account with campaign permissions, the partner can work inside that ad account; if you assign a pixel or dataset, they can use that measurement asset according to the task you granted.

Spend visibility is the part buyers underestimate. A partner with ad-account access will normally see campaign structure, delivery status and performance data inside that account. Finance permissions are separate from campaign permissions, but campaign-level spend is operational data, not a secret once you ask someone to manage the account. Your safer move is scoping the ad account itself, not pretending a buyer can optimize without seeing spend.

We could not verify Meta’s current Business Manager UI labels for every asset permission from the supplied fact pack; a live Business Settings permission screen or Meta’s current business-help page would settle the exact label names. The safe range is stable: expect separate controls for business administration, ad account work, page or profile work, catalog access and measurement assets.

how do you scope access to a single ad account?

Scope access to a single ad account by assigning only that ad account, then granting only the tasks needed for the work. Do not add the partner at the business level and then rely on memory to withhold assets later.

The practical path is to select the partner, choose Assign assets, pick only the target ad account, and leave every other page, pixel, dataset, catalog and Instagram account unselected unless the buyer needs it. If the buyer needs pixel events for optimization, assign the dataset separately rather than handing over a bundle of assets. Meta’s deduplication rule in another measurement context shows why IDs and event boundaries matter: browser and server events deduplicate only when the event name and matching identifiers line up within 48 hours, per Meta’s deduplication docs.

Single-account scoping also reduces cleanup after a restriction. If one account is disabled, you can remove or quarantine that account without breaking the rest of the business. We use this split when reading business manager restrictions: the question is not only why Meta restricted something, but which connected asset can now contaminate operational work.

how do you remove a partner cleanly, and what stays behind?

Remove a partner by revoking the partner relationship or removing the partner’s assigned assets, then checking users, pixels, datasets, pages, catalogs and ad accounts for leftover access. The first click removes the obvious relationship; the audit removes the operational residue.

A clean removal pass has 4 checks. First, remove the partner from the asset or from the Partners area. Second, inspect the ad account for users the agency may have added through its own business or through prior invites. Third, review pixels, datasets, catalogs and pages because tracking access often survives longer than campaign access. Fourth, check payment methods and billing contacts before you assume spend authority is gone.

What stays behind depends on ownership. Campaign history, invoices, page posts, pixel events and dataset history do not disappear because a partner lost access. If the ad account belongs to you, the campaigns stay in your account. If the ad account belongs to the agency, your access can vanish when the relationship ends. Disabled-account cleanup is a separate process, and the mechanics are covered in how to remove a disabled ad account from Business Manager.

which of your assets are visible publicly regardless of partner settings?

Partner settings do not control public visibility for ads, pages, profiles or public brand surfaces. They control internal access. If a page is public, an ad is running, or a profile is visible through Meta’s public surfaces, changing a partner role does not make that public material private.

This distinction matters during vendor changes. Removing an agency from Business Manager can stop the agency from editing campaigns, but it does not erase ads already delivered, public page content, comments, page transparency signals or external landing pages. If your concern is reputation, partner removal is only one step; you also need to inspect the public assets people can still see.

We checked the supplied source pack for legal or platform figures that belong here and did not add any unlisted numbers. That restraint is deliberate: this page is about Business Manager mechanics, and the verified numeric material supplied for the page mostly concerns tracking tools, hosting, video platforms and server-side event infrastructure rather than Meta’s current business-access UI.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Meta Ad Library, Meta advertising standards, and Google helpful content guidance. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through Ad spy comparison hub, Top Ad Spy Tools: A Reference for Operators, Spy Tool List: What It Is and What It Is Not, Ad Library Research: What Matters and What Does Not, Meta Ad Intelligence: What Matters and What Does Not, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.