# Worked Meta ad account handoffs

All businesses, people, IDs, and receipts below are fictional. `EXAMPLE` is a teaching marker, not a Meta ID or native receipt. The records show what a handoff can say at different stages; none reports a real account change.

## 1. New business needs its first account

| Field | Value |
| --- | --- |
| Record owner | Morgan, marketing lead (fictional) |
| Business name | Harbor Research (fictional) |
| Business portfolio ID | EXAMPLE-PORT-HARBOR |
| Ad account name | Not created |
| Ad account ID | Not applicable until creation |
| Account owner business | Harbor Research, intended |
| Owner portfolio ID | EXAMPLE-PORT-HARBOR, intended |
| Relationship evidence | Business owner confirmed Harbor Research will own a new account; EXAMPLE note, October 31, 2026 |
| Intended outcome | Create a business-owned ad account in Harbor Research's portfolio. |
| Selected route | create |
| Route reason | No existing account was identified after the owner checked the chosen portfolio. |
| Accountable actor | Morgan, portfolio controller, pending native permission check |
| Permission scope, with asset and tasks | Create in Harbor Research portfolio; no partner grant requested. |
| Route fit | Fits |
| Readiness | Hold |
| Submitted state and time | Not submitted |
| Approved state, approver, time, scope, evidence | Owner's business decision recorded in EXAMPLE note; Meta terms acceptance Unknown. |
| Observed state, surface, identity, date, evidence | Portfolio selected in Business Suite, EXAMPLE note; no ad account observed. |
| Verified state | Hold |
| Native receipt | Unknown |
| Evidence references | EXAMPLE owner note and portfolio screen description, October 31, 2026 |
| Evidence date | October 31, 2026 |
| Unresolved item | Morgan's native creation permission, chosen currency and time zone, and business decision on Meta terms. |
| Exact owner request | Morgan: confirm portfolio control, account currency and time zone, and whether you will review and accept Meta's terms for this business. |
| Next action | Resolve those choices; then Morgan may create once and save the native result and new account ID. |
| Billing readiness | Unknown; payment decision belongs to the business. |
| Page asset | Unknown; Page access is a separate asset check. |

**Why this is held:** The route fits, but a sensible route is not permission to click Create. If the confirmation disappears after a creation attempt, inspect this portfolio for the new account and recover the receipt before another attempt.

## 2. Existing account belongs to the same business

| Field | Value |
| --- | --- |
| Record owner | Alex, operations lead (fictional) |
| Business name | Cedar Analytics (fictional) |
| Business portfolio ID | EXAMPLE-PORT-CEDAR |
| Ad account name | Cedar Ads (fictional) |
| Ad account ID | EXAMPLE-ACT-CEDAR-42 |
| Account owner business | Cedar Analytics, per owner statement; native ownership not yet observed |
| Owner portfolio ID | Unknown; owner says the account is outside the destination portfolio. |
| Relationship evidence | EXAMPLE owner statement and Ads Manager account ID description, October 31, 2026 |
| Intended outcome | Put the existing business-owned account into Cedar Analytics's portfolio. |
| Selected route | claim |
| Route reason | Existing account reportedly owned by the same business and not in another portfolio. |
| Accountable actor | Alex, proposed portfolio controller |
| Permission scope, with asset and tasks | Claim EXAMPLE-ACT-CEDAR-42 into EXAMPLE-PORT-CEDAR; no partner grant. |
| Route fit | Fits, conditional on ownership check |
| Readiness | Hold |
| Submitted state and time | Not submitted |
| Approved state, approver, time, scope, evidence | Unknown; owner authorization to claim is required. |
| Observed state, surface, identity, date, evidence | Account ID visible in Ads Manager in EXAMPLE description; owner portfolio Unknown. |
| Verified state | Hold |
| Native receipt | Unknown |
| Evidence references | EXAMPLE owner statement and Ads Manager account selector description |
| Evidence date | October 31, 2026 |
| Unresolved item | Current owning portfolio, Alex's full control, destination account capacity, prepaid balance if applicable, and authorization for a potentially permanent move. |
| Exact owner request | Cedar's business owner: confirm who owns EXAMPLE-ACT-CEDAR-42 now, whether it is already in another portfolio, and whether Alex may claim it into EXAMPLE-PORT-CEDAR. Alex: confirm destination capacity and, if prepaid, zero prepaid balance. |
| Next action | Check native ownership, claim eligibility, and written owner decision; use claim only if eligible, then preserve the native result. |
| Billing readiness | Unknown |
| Page asset | Unknown |

**Why this is held:** The account ID is known, but a display name and an owner statement do not establish native ownership. Claiming may permanently move the account. If Meta shows that another portfolio owns it, switch to an access request instead.

## 3. Client owns the account; agency needs ad tasks

| Field | Value |
| --- | --- |
| Record owner | Jamie, client marketing owner (fictional) |
| Business name | Northline Health (fictional client) |
| Business portfolio ID | EXAMPLE-PORT-NORTHLINE |
| Ad account name | Northline Ads (fictional) |
| Ad account ID | EXAMPLE-ACT-NORTHLINE-77 |
| Account owner business | Northline Health |
| Owner portfolio ID | EXAMPLE-PORT-NORTHLINE |
| Relationship evidence | EXAMPLE client owner and portfolio Settings descriptions, October 31, 2026 |
| Intended outcome | Let Elm Agency manage ads in the client's account while Northline keeps ownership. |
| Selected route | owner_grants_partner |
| Route reason | Client owner can share the existing asset directly with the agency's portfolio. |
| Accountable actor | Jamie or another person with full control of Northline's portfolio |
| Permission scope, with asset and tasks | Grant Elm Agency portfolio EXAMPLE-PORT-ELM partial access to manage ads on EXAMPLE-ACT-NORTHLINE-77. No full portfolio access. |
| Route fit | Fits |
| Readiness | Hold |
| Submitted state and time | Not submitted |
| Approved state, approver, time, scope, evidence | Jamie approved the proposed task scope in EXAMPLE note at 2026-10-31 14:00 UTC; native partner grant pending. |
| Observed state, surface, identity, date, evidence | Unknown; neither side has observed the shared asset. |
| Verified state | Hold |
| Native receipt | Unknown |
| Evidence references | EXAMPLE client approval note naming actor, account, partner, scope, and time |
| Evidence date | October 31, 2026 |
| Unresolved item | Jamie's full portfolio control and native partner grant, any second approval, and agency observation. |
| Exact owner request | Jamie: confirm full control of EXAMPLE-PORT-NORTHLINE, enable two-factor authentication if needed, then grant EXAMPLE-PORT-ELM manage-ads access to EXAMPLE-ACT-NORTHLINE-77 and send the native result. |
| Next action | Owner grants the scoped partner permission; agency later checks the matching account and tasks in its portfolio and Ads Manager. |
| Billing readiness | Client-owned; readiness Unknown and separate from agency access. |
| Page asset | Unknown; Page permission requires a separate decision. |

**Why this is held:** The client approved a scope, but the share has not been submitted or observed. The agency's employee invitation, if needed, is a later internal assignment within the granted tasks.

## 4. Conflicting account ID and unknown owner

| Field | Value |
| --- | --- |
| Record owner | Sam, project coordinator (fictional) |
| Business name | Lakeview Studio (fictional) |
| Business portfolio ID | EXAMPLE-PORT-LAKEVIEW |
| Ad account name | Lakeview Ads, reported name only |
| Ad account ID | Conflicting: EXAMPLE-ACT-91 in email; EXAMPLE-ACT-19 in screenshot |
| Account owner business | Unknown |
| Owner portfolio ID | Unknown |
| Relationship evidence | Contradictory EXAMPLE email and screenshot descriptions |
| Intended outcome | Give an outside team ad-management access. |
| Selected route | undetermined |
| Route reason | Ownership and exact account identity are unresolved. |
| Accountable actor | Sam to obtain owner reconciliation; owner-side actor Unknown |
| Permission scope, with asset and tasks | Proposed manage-ads task only; asset ID unresolved. |
| Route fit | Unknown |
| Readiness | Hold |
| Submitted state and time | Not submitted |
| Approved state, approver, time, scope, evidence | Unknown |
| Observed state, surface, identity, date, evidence | Unknown |
| Verified state | Hold |
| Native receipt | Unknown |
| Evidence references | EXAMPLE contradictory email and screenshot descriptions |
| Evidence date | October 31, 2026 |
| Unresolved item | Owner portfolio and exact ad account ID. |
| Exact owner request | Please open the intended account in Ads Manager and send its name and ID, then identify the business portfolio that owns it. Which of the two IDs is correct? |
| Next action | Reconcile account and owner identity. Do not create, claim, request access, or grant a partner yet. |
| Billing readiness | Unknown |
| Page asset | Unknown |

**Why this is held:** Neither a familiar account name nor a confident email resolves two different IDs. A blanket full-access grant would also exceed the stated manage-ads task.

## 5. Completed fictional partner access handoff

This is a **simulated successful record**, with invented evidence references. It shows what matching approval, grant, and observation would look like. It does not assert that any Meta account was changed.

| Field | Value |
| --- | --- |
| Record owner | Priya, client marketing owner (fictional) |
| Business name | Alder Systems (fictional client) |
| Business portfolio ID | EXAMPLE-PORT-ALDER |
| Ad account name | Alder Campaigns (fictional) |
| Ad account ID | EXAMPLE-ACT-ALDER-31 |
| Account owner business | Alder Systems |
| Owner portfolio ID | EXAMPLE-PORT-ALDER |
| Relationship evidence | EXAMPLE-OWN-31: simulated owner portfolio Settings observation ties EXAMPLE-ACT-ALDER-31 to EXAMPLE-PORT-ALDER. |
| Intended outcome | Let Pine Agency manage ads in Alder's ad account while Alder keeps ownership. |
| Selected route | owner_grants_partner |
| Route reason | Alder is the account owner and chose a scoped owner-side partner grant. |
| Accountable actor | Priya, simulated full controller of EXAMPLE-PORT-ALDER |
| Permission scope, with asset and tasks | Pine Agency portfolio EXAMPLE-PORT-PINE receives partial access to manage ads on EXAMPLE-ACT-ALDER-31 only; no full portfolio or Page access. |
| Route fit | Fits |
| Readiness | Ready; the requested partner handoff has matching simulated evidence. |
| Submitted state and time | Submitted at 2026-10-31 15:10 UTC; EXAMPLE-GRANT-31 is a simulated native result. |
| Approved state, approver, time, scope, evidence | Approved by Priya at 2026-10-31 15:00 UTC for Pine Agency EXAMPLE-PORT-PINE, manage-ads task on EXAMPLE-ACT-ALDER-31; EXAMPLE-APPROVAL-31. A second controller was not requested in this simulated result. |
| Observed state, surface, identity, date, evidence | Observed by Priya in simulated Alder Settings and by Theo, Pine Agency's portfolio controller, in simulated Pine Settings and Ads Manager at 2026-10-31 15:20 UTC: EXAMPLE-ACT-ALDER-31 with manage-ads task for Pine; EXAMPLE-OBS-31. Alder retained owner designation. Theo's observation does not establish a later Pine employee assignment. |
| Verified state | Verified for the specified partner access only; simulated EXAMPLE-OWN-31, EXAMPLE-APPROVAL-31, EXAMPLE-GRANT-31, and EXAMPLE-OBS-31 agree on account, owner, partner, and scope. |
| Native receipt | EXAMPLE-GRANT-31; invented demonstration reference, not a real Meta receipt. |
| Evidence references | EXAMPLE-OWN-31; EXAMPLE-2FA-31; EXAMPLE-APPROVAL-31; EXAMPLE-GRANT-31; EXAMPLE-OBS-31. All simulated. |
| Evidence date | October 31, 2026 |
| Unresolved item | None for the partner access task; billing, Page access, and ad serving are separate. |
| Exact owner request | No further owner request for this scoped partner grant. |
| Next action | Pine assigns its permitted ad task to the intended employee if needed, then checks that person's access separately. |
| Billing readiness | Unknown; not needed to verify the partner grant. |
| Page asset | Unknown; no Page grant was requested. |

**What changed in the simulated record:** Alder's owner approved one account and one task scope. The grant result and later observations match those identities. The simulated `EXAMPLE-2FA-31` reference records that two-factor authentication was enabled for the owner portfolio before the partner grant. The handoff is verified for partner access only; it does not claim billing readiness or ad delivery.